mrtnptrs
Published
Tried Proton GE 7-24, Proton 7-03 and Proton experimental (30-06-2022), all result in the same blackscreen after the initial loading-screen of the game (right when you hear the EA logo sound). Cursor still works then when using touch and is visible, 60 fps, but whole screen is just black. Applying the "-skipvideos" through Origin might help, idk, haven't tried it as every Steam-Origin game requires to specifically re-install Origin again... So, beware, game has always to be launched through Origin, goes automatically when starting from SteamOS, but still noteworthy...
Can run stable 60 fps with max settings (max AA, SSAO on etc.) Has no black-screen issue, like the remastered version has on Steam Deck, and doesn't use any DRM (apart from standard Steam DRM, Remastered version uses that, but also Denuvo AND Origin DRM) or Origin-launcher (like the remastered version does)
Works great (full supported fps), but have to change control layout and takes up to few minutes to load (can be easily fixed)
Some heavy stuttering sometimes, could be due to shader compilation or just due to weird old SAGE engine that is being used. FMV-cutscenes run at maximum of 50 fps by default and game itself runs at 30-31 fps by default (engine-limitation, can't be raised without speeding up the game.)
As the game tries to reach a now defunct server to retrieve the in-game news ("Comrade News"), it waits till that request times out before the game can start. Can take several minutes for the game to load, till that it is just black screen or the loading Steam-logo animation. Can be fixed by either replacing the RA3.exe executable with a different one (see https://www.pcgamingwiki.com/wiki/Command_%26_Conquer:_Red_Alert_3#Speed_up_loading) or by simply adding "127.0.0.1 files.ea.com" to "rootfs/etc/hosts"-file (which thus leads the request directly to nothing).
Can run smoothly, but has startup-issues at first, thus first start it a few times with Proton GE and then it should be fine.
Didn't want to start on latest Proton Stable (7-03) and Proton Experimental, even didn't start the first time with Proton GE, but after trying to start it with Proton GE for a second time, it suddenly worked. After that, starting it with normal Proton also worked. Very weird startup issues. Maybe during the "updating executable"-part when trying to run it through GE fixed the executable and made it able to run under normal Proton?
After you got it to start, it can run at 60 fps very stable (only in rare circumstances not) at max settings (runs standardly at much lower settings) except for setting anti-aliasing (MSAA) to 4X instead of 8X (otherwise you will hover between 50-60 fps as MSAA is very demanding.)
The Steam overlay and performance metrics wouldn't show, even if I pressed the respective buttons. The game itself runs fine thought, it just seems that the game doesn't like overlays when running through proton/DKVK.
Runs well, just weird that the overlays don't work.
You start off with the game playing at lower resolution, you can set it to full 800p in the in-game settings. Be wary, can't play the game without a self- or community-made Steam Input layout.
You start off with lower resolution and settings when starting for the first time, but max settings at 800p won't hold a stable 60 fps (floats between 50-60 a bit when much happens on-screen), either lower the fps-limit (like 40 or 50) or lower the settings. Didn't crash once for me.
Especially the music sounds weird/corrupted always, game sounds seem to be mostly ok
Some stuttering when moving around in a level, could also be shader-compilation related stuttering or stuttering from geometry loading in
Audio issues happens also when using Proton Experimental. Game runs fine for the rest apart from some heavy stutters sometimes when moving around the map.
Doesn't support 800p natively, only 768p at max. Lower resolutions don't scale to the screen of the Steam Deck, unless you are in windowed mode.
Game runs natively at 38 fps. This game is fully playable on Steam Deck, but would recommend OpenRCT2.
Can run great, but requires editing some files, otherwise it won't start, can run at 60 fps after tinkering
- Open the file "/home/deck/.local/share/Steam/steamapps/compatdata/17390/pfx/system.reg"
- Paste the following strings anywhere between other pre-existing strings in that file:
[Software\Wow6432Node\electronic arts\spore] 1627191375
#time=1d78116fc363040
"appdir"="Spore"
"datadir"="/home/deck/.local/share/Steam/steamapps/common/Spore/Data"
"installcompleted"=dword:00000001
"installloc"="/home/deck/.local/share/Steam/steamapps/common/Spore"
"locale"="en-us"
"playerdir"="My Spore Creations"
"reindexyesorno"=dword:00000000
- Now run the game, works with latest Proton Experimental (30-06-2022) and also with Proton 7-03.
Credits: https://github.com/ValveSoftware/Proton/issues/514#issuecomment-966274572 (adapted solution to Steam Deck)
Some text can be hard to read, but doesn't bother me that much. UI is also bit on the smaller side. Also not very bothersome.
Game wouldn't start up initially, see configuration files changes how this was fixed.
To get 60 fps:
- Open "/home/deck/.local/share/Steam/steamapps/common/Spore/Data\Properties.txt"
- Add the following line to the end of the file: "property frameLimitMS 44 int"
- Open "/home/deck/.local/share/Steam/steamapps/common/Spore/Data\ConfigManager.txt"
- Add the following line to the end of that file: "intProp frameLimitMS 16"
- Save both files
- Set Steam's frame limiter for this game specifically to 60 fps (otherwise it will run at 62)
- Play the game.
Game supports 800p resolution at max settings (When panning around the camera fast, the fps can drop into the 50's), but those max settings are not the default, you'll have to set those in-game.
Runs from the start at max settings 60 fps without any adjustments needed. Only minor stuttering on camera transitions in in-game cutscenes, but that happens with many many games, nothing unusual.
