Since today it happened two times, first i got screen flickering with CRT like lines and then the screen becomes completly black, except the cursor, wich is still rendered and movable.
The game continues running in the background, i can select units and buildings, acording to sound effects and the cursor changes to patrol and reclaim.
Windows: Version 10.0.19044 Build 19044
Prozessor Intel(R) Core(TM) i5-4670K CPU
NVIDIA GeForce RTX 3060
Treiberversion 31.0.15.2647
yes can i have similar problem, i tried playing with my friend multiple times... everytime either me or my buddy gets flashing screen and is unable to continue playing, we tried on multiple maps and with and without nomads every time ends with flickering screen
it started after the update
We need logs!
You can find them here:
and then 'Show log folder', find the one that matches your game.
A work of art is never finished, merely abandoned
@jip game_18455362.log game_18455312.log game_18455204.log game_18455143.log game_18455117.log game_18455087.log game_18454999.log game_18454878.log
these are the logs of today, i hope im being helpful ^^
Could you try and host on the regular game type (FAF or FAF Develop?), see if it still happens?
A work of art is never finished, merely abandoned
@jip I'm having similar problems. This log is from a game I hosted: game_18456774.log . This log is from a game someone else hosted: game_18456848.log
The game froze with the UI flickering but my inputs were still accepted as I could pause the game and it would pause the game for my two buddies aswell. Alt+Tabbing out and back in lead to just a blackscreen. The game continued uninterrupted for them until I alt+f4'd the game.
Same here. Multile times, every game crashes this way and before the last patch I had no problems at all.game_18457009.log
Video: https://priv.de/crash.mp4
It started just after the last update today.
Got the same...
with mods
game_18458247.log
and without them
game_18458316.log
And no problems detected in FAF Dev.
Related to the FakeRings errors in the logs - It is getting fixed asap, in the meantime deactivate the Depth scanning feature via options.
