Piquan
Published
Proton Experimental helps, but not much
I initially had the initial "Fatal Error" black screen, but I switched to Proton experimental-5.13-20210217 and that stopped.
It shows producer logos, and a screen to select your play position (standing or sitting).
It crashes a second into that screen.
ffmpeg -f pulse -i default -t 1:00 -f wav -y /dev/null & PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command% --launcher-skip -skipStartScreen
After alt-tabbing out, the game crashes when I try to return.
After 1.5, it will crash unless I record audio when it launches. Most people here have the same requirement with playback, but playing something in the background didn't help me. My command given above includes a bit to record (and discard) audio for one minute when launching the game.
I've had great fun playing CP2077 since it came out. I don't have the stability issues that many people talk about.
PROTON_ENABLE_NVAPI=0 %command% --launcher-skip
Without the launcher, cross-platform saves don't work.
Freezes are no more frequent with 2.0 than before.
The game sometimes freezes, maybe once per 10 hours of gameplay. Currently-playing audio elements continue, but graphics and the world stop. Alt-tab takes several seconds to respond, but after that I can stop it from Steam.
With NvAPI disabled, DLSS is not available.
I had to disable NvAPI with PROTON_ENABLE_NVAPI=0, but I don’t know why. I tried many launcher commands, and carefully checked all my Nvidia and NvAPI drivers, libraries, etc, but couldn’t get it working without disabling NvAPI. It seems that most Nvidia users don’t have this problem. PROTON_ENABLE_NVAPI=0 is only going to have an effect on Proton 8 and later, since prior to that, NvAPI was always disabled by default.
I verified that the command in the report I gave (PROTON_ENABLE_NVAPI=0 %command% --launcher-skip) works, but I use a more elaborate command in practice.
The command I use is ffmpeg -f pulse -i default -t 1:00 -f wav -y /dev/null & PROTON_ENABLE_NVAPI=0 MANGOHUD=1 VKD3D_CONFIG=dxr gamemoderun %command% -skipStartScreen --launcher-skip.
- The part
ffmpeg ... &starts a background process to open the microphone for one minute. This works around a problem with early versions of CP2077 on Linux in which music in bars wasn’t audible; I don’t know if it’s still necessary. - The
VKD3D_CONFIG=dxris to enable ray tracing. Note thatdxr11is, as of quite recently, obsolete; it’s automatically implied bydxrsince vkd3d-proton 3.9 / Proton 8.0-3. You can leave it out if you don’t use ray tracing. - The
MANGOHUD=1enables the MangoHUD Vulkan layer, if you have it installed. You can leave it out if you don’t use MangoHUD, but it doesn’t matter otherwise. gamemoderunenables GameMode clock governor. If you don’t have GameMode installed, you have to remove that.-skipStartScreenskips one of the loading screens, but isn’t a big deal.- Linux users have needed
--launcher-skipfor a long time, since REDlauncher uses Windows libraries that don’t work right under Proton.
Currently unplayable
After the intro videos finish, and gameplay starts, the environment doesn't render. You just have your character, a few objects around, and the sky box: no ground, walls, or anything else.
Unplayable using Nvidia drivers 550.54.15 (missing textures). Updating my drivers to 575.51.03 fixed it.
-d3d11
It recently stopped working on my system, I think because of either a Proton or a driver update. Works fine again with -d3d11, though.
Delete or rename libEGL.dll and libGLESv2.dll, and optionally d3dcompiler_47.dll
Many maps run at at low framerates, about 10 fps or so. (Given the nature of the game, this does not affect gameplay.) The top-level affection cutscenes can take about 15 seconds to run one of the effects, making it appear as if the game has locked up; be patient.
Some users talked about using the built-in web version. That won’t work with modern browsers, unless you run an HTTP server. I wrote a utility at https://github.com/piquan/katakana-warriors-save-migrator to migrate your saves between the web and app versions. That also has some instructions on running the web version, but it’s not for the inexperienced.
Latest EA launcher update fixed it for me
This hasn't been launching for the past month or two. Today, the EA launcher loaded an update that seems to have fixed my problems. The first launch loaded the update but didn't launch the game, the second went through the launcher screen and then ran the game, and the third launch worked fine, going straight to the game. After the update, I've played ME1 for a few hours, and had no problems.
No text-to-speech (used by the ATC)
To recognize the HOTAS, I had to set the "Controllers" pane in Steam's game settings, but it worked well after that. Thrustmaster rudder pedals were not detected.
Set launch flags to -FastLaunch
sed -i -e 's/^resolution=.*/resolution=1280x800/' "${STEAM_COMPAT_DATA_PATH}"/pfx/drive_c/users/steamuser/AppData/Roaming/LucasArts/*/Settings.ini && %command%
L4, R4: Set to U (use) and P (pick up) for convenient access; Triggers: Set to L=A and R=B (hard pull only, disable the analog output!) to correspond to the relevant on-screen displays; R trackpad as mouse, click=B
Steam cloud sync will sync your preferences too. If the preferences have a resolution that's too high, then the game will crash on startup. I changed the startup command to automatically switch the resolution to 1280x800; I used a similar command on my desktop to switch the resolution to 4k.
