New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Bureau: XCOM Declassified (65930) #797
Comments
It seems, that this game is affected by the CEG DRM issue #753 |
Same here, how can I check logs for more info? |
Find "user_settings.sample.py" and rename to "user_settings.py".If use Proton beta file is located in -steamapps/common/Proton 3.7 Beta/ |
Proton 4.2-3, one day maybe. |
Still a problem in Proton 6.3-5 |
Tried latest Proton Experimental with the latest Steam Beta CEG Build, and it still doesn't launch: |
It's not working for me either with Steam Beta + Experimental. But I don't even get a proper log file (not runtime container related). |
TheBureauXcomDeclassified.tar.gz Per Pierre currently when you fail to launch a CEG game or update prefix you need to use Steam to verify game files. This will give you a new fresh original exe. Then when you start proton experimental it will try again to patch the exe against your account. (that is what CEG does) |
I have gotten the game to work now. The intro video also played and I could load up a game save near the end of the game ok. So appears to work 100% although I didn't test controller. Currently you need to switch Proton Experimental to the "bleeding-edge" beta. Then set the following launch options for the game. |
I confirm, I was also able to run the game by changing to the proton of the game to Experimental, then on the proton experimental library entry settings choosing the beta branch for bleeding edge, then going to The Bureau library entry properties local files tab and clicking on the verify button once, then launching the game. However, if I don't use the variables |
After I deleted the prefix, I was able to get a proper log. However, even when I disable esync and fsync, the game doesn't start. The icon appears for a fraction of a second in the panel and then crashes. Doesn't matter if I chose DX11 or not. |
steam-65930.log |
@Patola No I didn't. I wasn't aware that there is a bleeding egde beta, I thought you were talking about experimental. I retried with bleeding egde and can confirm that it works with that and esync/fsync disabled. |
With the latest stable steam client and Proton 6.3-8 the game now load, but it start minimized and when I try to maximize it, the game crash. I have to kill it with alt+F4. |
Runs fine for me with Proton 7.0-1, Mesa 21.3.5, kernel 5.16.10. |
Begins to launch via steam, but then promptly stops running without any screen popping up at all.
steam-65930.log
There's the proton log.
https://gist.github.com/Dazarlin/1fe5b3d929f71f1f3f598c5b99d0c262
And there's my system info.
The text was updated successfully, but these errors were encountered: