The logs hint at ddraw.dll being taken from C:\windows\system32\ddraw.dll rather than the patched version in ~/.local/share/Steam/steamapps/common/Fallout 2. I tried playing around with Wine DLL overrides in the Proton settings but I have too little knowledge about this.
Symptoms
The Steam release of Fallout 2 includes two mods (sfall and f2_res). They don't seem to be applied when running under Proton.
Changing settings in ddraw.ini and f2_res.ini (both found in ~/.local/share/Steam/steamapps/common/Fallout 2) don't seem to have any effect. I tried the following options in ddraw.ini and they did not have any effect:
SkipOpeningMovies=1 (this one is easy to test with)
ProcessorIdle=30 (but CPU usage was still over 150%)
Other than these mods not being applied the game seems to run normally and is playable, however constantly using over 150% CPU according to htop.
Reproduction
When starting the game from Steam it asks whether you want to play Fallout 2 or the classic version. Both versions exhibit the issue described above.
Compatibility Report
System Information
I confirm:
steam-38410.log
The logs hint at ddraw.dll being taken from C:\windows\system32\ddraw.dll rather than the patched version in ~/.local/share/Steam/steamapps/common/Fallout 2. I tried playing around with Wine DLL overrides in the Proton settings but I have too little knowledge about this.
Symptoms
The Steam release of Fallout 2 includes two mods (sfall and f2_res). They don't seem to be applied when running under Proton.
Changing settings in ddraw.ini and f2_res.ini (both found in ~/.local/share/Steam/steamapps/common/Fallout 2) don't seem to have any effect. I tried the following options in ddraw.ini and they did not have any effect:
Other than these mods not being applied the game seems to run normally and is playable, however constantly using over 150% CPU according to htop.
Reproduction
When starting the game from Steam it asks whether you want to play Fallout 2 or the classic version. Both versions exhibit the issue described above.