Demo: ground meshes flicker

[Krampe]

Really loving the new look of the game, but in the demo I'm getting terrible flickering on what seems to be squares of terrain mesh, making the ground see-through and it's pretty unplayable like this. Is anyone else experiencing this..?
When buildings are being constructed on one of these flickering squares, the underneath pathing mechanism shows through (quite interesting how they made the pathing work actually lol), and then when the building is completed the flickering sometimes stops on that particular square...
The normal EA game has always played fine for me for over 300 hours, and hopefully this won't affect the 1.0 release for me, I really love the game!
However I do worry if it's due to me playing on an iMac27 (from the Intel days) using Bootcamp - I've seen other graphics issues being told to update gpu drivers, which I've done already and no luck. I tried official AMD drivers and different versions of those Bootcamp Adrenaline drivers, which give me better FPS but the flickering is unchanged. Never had issues in any other games, only this demo.

Older but hi-spec'd out iMac27:
i7-6700K
24gb RAM
Radeon M395X

Really hope this is just temporary and will not persist in the full release. Any suggestions are appreciated tho, would love to just play the demo too! Thanks!

[iki_balam]

Same here. Hoping there's a fix.

[Krampe]

Originally posted by iki_balam:

Same here. Hoping there's a fix.

Are you playing on a Bootcamped Mac as well, or real PC?

[iki_balam]

Real PC

[Krampe]

Devs, any suggestions on this issue?

[Mr Ash]

Originally posted by Krampe:

However I do worry if it's due to me playing on an iMac27 (from the Intel days) using Bootcamp

This could well be the link to your issue. Make sure to completely remove old drivers (clean install) if you are updating to new drivers. If an older driver was corrupt just installing new drivers won't fix this without a full clean install.

Unfortunately as this is unsupported there is very little we can do to test, however we are seeing other issues on Linux that we are looking into. It may be an AMD related thing but we are investigating and hopefully will be able to resolve these issues.

[Hieronymus]

I can confirm the same/similar issue for windows, so it might be AMD related.

[Krampe]

Originally posted by Mr Ash:

Originally posted by Krampe:

However I do worry if it's due to me playing on an iMac27 (from the Intel days) using Bootcamp

This could well be the link to your issue. Make sure to completely remove old drivers (clean install) if you are updating to new drivers. If an older driver was corrupt just installing new drivers won't fix this without a full clean install.

Unfortunately as this is unsupported there is very little we can do to test, however we are seeing other issues on Linux that we are looking into. It may be an AMD related thing but we are investigating and hopefully will be able to resolve these issues.

Hey thanks for the response!
Yeah I agree that iMac/Bootcamp isn‘t really a focus platform and way down the line in terms of testing for compatibility. For what it‘s worth, I‘ll just reiterate that I have never really had any issues in any other games. I‘ve tried official drivers and also community drivers, and yes I‘ve also made sure to wipe any old lingering drivers and done clean installs.
It does seem like others are ticking in with similar issues on normal Windows machines, and I‘m noticing a bunch more saying it‘s AMD related.

Anyway I‘m sure y‘all are in crunch mode, and we‘re all rooting for you! This game is really special and I just want it to be a banger when it releases, you guys deserve it!
Let me know if I can be helpful with a dxdiag dump or anything! Thanks for an amazing game.

[Burpane]

I first got an error in win10 and the error read I needed an OpenGl version I didnt have. AMD handles OpenGL in different ways compared to NVidia or whatever is used. I then adjusted my newly installed AMD driver to allow OpenGL to pass through some firewalls.

Originally posted by Mr Ash:

Originally posted by Krampe:

However I do worry if it's due to me playing on an iMac27 (from the Intel days) using Bootcamp ..an AMD related thing but we are investigating and hopefully will be able to resolve these issues.

"Its not ur boots or the straps of camping with a BigMac."

I downloaded the other landscape game and the initial setup wanted me to update my AMD driver. The driver needed was an AMD 21 version. The game started after full AMD drivrer cleaning and reinstall.

AMD 21 Recommended: download the Non-Legacy driver ( Radeon Software Adrenalin 21.5.2 Driver for Windows® 10 64-bit for Non-Legacy AMD Radeon Graphics )

Here is the resource documented link:
https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-21-5-2.html

[Burpane]

Somwhow the OpenGL folders are not compatible with AMD. AMD has an option to allow OpenGL. If the OpenGL option is off with AMD the games files and folders have no access to read the Foundation log file. The AMD drivers are more than optimized to allow and reconfigure OpenGL as an empty folder, which AMD takes control to allow the files of the game to get reconnected under AMD driver permissions. A bit troubling to understand as OpenGL is like a third party tool and needs more security before an initial game boot.

If the screen freezes, guess what it is with OpenGL, a bad files and folder paths with a blank database that issues a no such address with no user and no way to let the game user profile have access.

Im not a developer I enjoy reading about instructions. I would try repairing with different OpenGL versions to see which has the cleanest play time, and then wait for OpenGL to offer a better compatibility. It like buying RAM today dram, sram, trex, and sddHDram. They each connect to a single addressed slot.