Wildgate - Open Beta
Somehow, uploading Logs is failing on github, I will try and get it uploaded as fast as possible
Oh lord, the game is spamming alot of Nonsense in the Log files
Yea, I am afraid I wont be able to send the log file. The game was spamming that nonsense every single second, causing the log file size to be enormous and impossible to compress.
The game starts fine here (only tried with AMD). Could you please try with Proton Experimental specifically (deleting the Proton prefix /compatdata/3727950 before that)? And if the issue persists, attach a compressed default log as full? The log may be big but those are compressed very well.
Yea, I have no idea, first, the game started with those errors, now it all of a sudden fixed itself???
My brain does not understand......
Not to mention, it fails to close properly, causing it to loop on "Stop game" and "Stopping"
I have to end the "GameThread" in System Monitor to get it to close properly.
And it still does that Log Spamming nonsense
And it still does that Log Spamming nonsense
It is not nonsense, it is useful info :) Which, if the full compressed log recorded with PROTON_LOG=1 %command% in the Launch options is attached, has a chance of giving some clue what's going wrong. Short exempts from log are useless unless you know exactly what problem is already.
6.15.2-arch1-1
Mesa 25.1.3
7900 XTX
Proton Experimental [Bleeding-Edge]
We have been assuming it was the anticheat, but after the latest patches I am able to play as long as I
- Don't fire certain weapons like the MK2
- Don't use any ship turrets
- ???
If I do any of the secret forbidden actions the game will just silently crash to desktop and disappear ~30 seconds later.
The attached log is for me
- Starting up the game
- Selecting the MK2 weapon into my loadout
- Loading into a matchmade game
- Loading into the pre-match lobby
- Waiting for a bit, then firing the MK2 weapon
- After a short while the game silently crashing to desktop
I've had an experience with Wildgate and Killing Floor 3 where the game seems to go through a few seconds to minutes of terrible frame rates before fixing itself. Sometimes changing graphics settings temporarily is enough to fix the problem.
Both games will go from a stable 60+ FPS to sub 20 and sometimes single digit FPS when this is happening but won't experience it again once it settles down (until closed and reopened).
It almost feels like some kind of weird shader cashing issue ... but a very strange one that's never permanently resolved.
Has anyone else noticed something like this or found a solution?
Compatibility Report
System Information
I confirm:
Symptoms
The latest Wildgate update has caused the game to break by spawning 7 Wine crashing windows containing a Yes or No to launch Wine Debugger, once all windows are cleared, the game immediately crashes and pops up a Unreal Engine Crash Dialog.
Reproduction
Install the public Wildgate Beta version from its Steam storefront, once installed, launch the game with your preferred Proton version and it should crash badly.