LINUX SUPPORT IS HERE

[callcifer]

No idea, but let's debug it. What's your GPU/GPU driver/DE/Proton version?

[foodlfg]

- AMD RX560
- Ubuntu 18.10 - it was ok with 16.04 LTS
- OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.8
- from:Proton 3.7-8 to:Proton 3.16-9 Beta
- vsync on/off, windowed, not windowed, wine virtual desktop on/off

the flickering appears in the main menu too. no need to play games to test this.

[callcifer]

Ubuntu switched from Unity desktop to Gnome between those versions, but I'm also on Gnome without any flickers, so that can't be it. Same with Proton, I'm on 3.16-9 as well.

It sounds like it might be the GPU driver. I'm on Nvidia so can't help much, but you could try upgrading to Mesa 19.0.3 and see if that makes a difference.

[tatsu]

@foodlfg I donnot have this issue, are you on AMD?

[tatsu]

the 30-min desync/crash bug is apparently caused when using certain AMD processors and seemingly would have nothing to do with linux. could anyone help me verify this?

I Had a buddy who's had this happen on a windows 10 64bit FX 8320 processor

Code: Select all

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x0042323b
    attempted to write memory at 0x00000105

Program : C:\ProgramData\FAForever\bin\ForgedAlliance.exe
Cmd line arguments : /init init.lua /nobugreport /log C:\ProgramData\FAForever\logs\game.log /gpgnet 127.0.0.1:8150 /mean 1500.0 /deviation 500.0 /savereplay gpgnet://127.0.0.1:54096/9684728/Hazdarr.SCFAreplay /country FR /numgames 0

Callstack:
   Unknown symbol (address 0x0042323b)
   Unknown symbol (address 0x00801e43)

[foodlfg]

it's a crash bug for me, no desync is involved.
also, i have a Ryzen CPU which is completely different from an FX 8320 CPU so i wouldn't think it is the CPU that is casing the problems. it's a new design and for example the FX 8320 has no virtual threads. the same thing is that both have many threads or cores.

it's true tho, that i got this crash with an nvidia GPU too. i have an AMD one. so it's definitely not GPU related.

when i enabled gallium nine for my AMD GPU, the crashes seemingly disappeared. tho i still get crashes when i watch long replays, but not in actual gameplay.

i would suggest your friend to switch to linux (: and install gallium nine (: to see if it really solves the problem.



----------

btw the d3d_WindowsCursor console command solves the mouse cursor flickering for me.
issue it in the games console, during gameplay.

[Little Miss Murder]

Dunno about any thirty minute crash bug, but I am unable to complete watching most replays over an hour long without ir crashing to the debug window for various reasons that dont seem to have a clear cause. These are usually Setons replays and so the memory and CPU load are fairly high.

I have an i5-6600k and a GTX970.

[tatsu]

damn that's weird. I personally don't have crashes at all.

GTX 760, i7 3930K

[foodlfg]

i have crashes during watching long replays and i even have a completely different system. : D
we cannot narrowing it down to only CPU/GPU/drivers, it looks like. >.<

do you guys use minimap or split view in the game?
these might cause crashes, i suspect.

- Ryzen 5 1600X, 16GB mem
- AMD RX560, 4GB
- Ubuntu 18.10, Gnome 3
- OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.8
- from:Proton 3.7-8 to:Proton 3.16-9 Beta

[callcifer]

Yes to minimap, no to split screen. Replays over 30 minutes crash 50% of the time for me.

i7-5820K, GTX1080Ti, latest Gnome, Proton 3.16 beta