
🐭
Published
Runs great at the highest settings with no tweaking required! That is to say it runs nearly identical to the Windows version, bar the expected occasional framerate dip. The game is still a buggy, laughable piece of crap, but Steam Play can't fix that. The only problem I had was when I got a black screen when changing the resolution. I could still see the Steam framerate overlay, shift-tab still worked, alt-tab still worked, and alt-f4 still worked, so that was probably just a bug with the game itself. The right resolution was being used when I restarted. So platinum results overall.
Runs great. I played it all the way through to the end. 100% and all achievements. The only issue I noticed was some input delay, but this problem could be present on the Windows version too. I really don't know.
The native Linux version is broken. It only shows a white screen. If you're using a Steam Deck and are in "desktop mode", you can't alt-tab, alt-F4, or close the program in any other way because the controller layout is automatically switched. With all inputs rendered useless, you have to hold down the power button and hard reset. There are two different solutions for this: - Set the launch options to: -screen-fullscreen 0 - Or use the Windows version by putting a check in the box at properties > compatibility > force the use of a specific steam play compatibility tool. The latest version of Proton will probably be fine. NOTE: This method will cause Steam to redownload the game. Aside from that, it seems cloud saves are broken. They won't be shared across computers/devices. Finally, frame caps are a problem. You can enable vsync in the settings, but you'll have to do it every time you start the game. There's still a checkmark in the vsync box but it won't be enabled. If you're using the windows version, you can force a frame cap by adding this to the launch options: DXVK_FRAME_RATE=60 %command%
Works great! I played for an hour and there were no problems I can think of, other than the occasional framerate drop. But IIRC, this uses Adobe AIR, so that's to be expected.
It finally works! It's taken years but the game finally works! You just have to use Glorious Eggroll's Proton, version 7-13 in my case. I haven't had the chance to put some real time into it yet, but the only problem so far is resource overlays aren't working. I'm not happy about that, but the game is working now and that is a huge step forward! Other notes: You can force multithreading, and vastly increase performance, by setting this as the launch option: taskset -c 1-$(($(nproc --all)-1)) %command% You can also put a frame cap on the game with: DXVK_FRAME_RATE=60 So the full launch option would be: DXVK_FRAME_RATE=60 taskset -c 1-$(($(nproc --all)-1)) %command%
Main menu loads just fine. Mods/DLC are the issue. C:S loads it all into RAM when loading saves. If you have too many, it will max the RAM and crash the system. Steam Deck has ~14gbs to play with, which is more than any other city builder ever needs, but we're talking about Unity3D now, so you must be VERY picky about mods/DLC. Go to properties, DLC, and uncheck anything useless. Soundtrack or radio DLCs are out. If you don't like sports and aren't making a campus city, then disable those too. CCPs are nice and you can have a few enabled without issue, but old saves can be dependant on them. So it's up to you. But C:S isn't just a memory hog! It's a CPU & GPU hog too! You're going to have a hard time getting it to run at a smooth FPS, free of microstutters. Disable all DoF crap and turn shadows way down if you want a two digit FPS. I've seen people suggest using the following launch option, but it could be a placebo: SDL_VIDEODRIVER=x11 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command% Oh and don't even bother running the windows version in Proton. AWFUL performance. Force native only. I've heard -force-opengl and -window-mode exclusive make a difference, but what render mode would the native Linux build use besides OpenGL? But wait, there's more! Why stop at awful system usage when it can have trash graphics too? I've seen people claim to get visuals that look like the promo art. But you'll need >10 mods for that and even if you had enough RAM, you'll still have compat issues with mods since the devs love to break them and often do. So all mods are living in a quantum super state of being both alive and dead, and it's really just a matter of time anyways so you might as well never bother. You'll never iron out those jaggies. Learn to love them. And we're still not done yet! Why not put a terrible launcher in between the user and C:S too? To skip the stupid launcher, use launch option: "./Cities.x64" %command% So: 1. Force native Linux 2. Disable all DLCs 3. UNSUB all mods (disabling isn't enough (they still load)) 4. Set launch options: SDL_VIDEODRIVER=x11 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia "./Cities.x64" %command% -force-opengl -window-mode exclusive 5. Disable graphics Then it will work. OR! Hear me out! You could play an actually fun and stable city builder, like Tropico, Surviving Mars, or Cities XL. Just saying.
The only problem was the out of control frame rate. I was getting ~2,000fps. That's nuts. There seems to be no options to limit the frame rate or enable vsync anywhere. So my suggestion is to skip the native version and install the windows version. Then set the launch options to: DXVK_FRAME_RATE=60 %command% Then the game will run just fine without melting your GPU. Other than that, it's great. A cool and stylistic game. Also: Angler fish that have a light on their head are female. The males are tiny and don't have a light. Billy should have been female.
Installs and runs great. Though I did have a couple issues with trying to switch to windowed mode. First I had to restart the game to apply the changes, which caused it to crash on the first restart. On the second restart, the video wouldn't update and it started without a frame. I tried to move it, via alt+mouse1, and it wouldn't move. I restarted it a 3rd time and it appeared on the wrong monitor and minimized, and wouldn't unminimize. On the 4th and every restart since, it has worked perfectly without any issue. I don't know what caused this bizarre behavior but I didn't do anything to resolve it so I guess it sorted itself out. It might be easier and faster for you to manually set a virtual desktop than to try to set it to windowed mode. To do that, just open a terminal and run WINEPREFIX="$HOME/.steam/SteamApps/compatdata/26900/pfx" winecfg and put a checkmark in the box in the graphics tab. The highest resolution is 1024x768 so set that as the virtual desktop resolution. Easy-peasy. But that's only if you want it in windowed mode. :)
It loads a black screen at lightening fast speeds! It gives you at least five minutes of load time so you can listen to your favorite song, make a sandwich, or decide if you want to play a different game, before it even shows you the main menu! And once you finally play a level, you'll be happy to know it runs at a blistering 17 frames per second! It has an "advanced" settings menu, which is there purely for amusement because it doesn't matter if it's on the lowest graphical settings or the highest, the framerate will always dip into single digits at least once a second! If you do literally nothing for the first 30 minutes after a level loads, Steam's overlay will report as much as 200fps! But apparently Steam's overlay is a F*CKING LIAR because Doom still looks like a slideshow!
There was a promising post on github that said VC++ 2015 had to be installed to make Doom not run like hot garbage. I tried installing both it and Doom ON THREE DIFFERENT DISTROS, all with the same exact hardware, and all three gave the exact same results.
I'm giving this a platinum rating because apparently this kind of performance is identical to the Windows version. That's right, trying to play Doom at a comfortable framerate on Windows will make you want to kill yourself there, too. So technically, it's not Proton's fault because Doom is running exactly as Bethesda intended.
It's amazing, isn't it? No indie developer could ever possibly hope to get away with this kind of thing. But because it's Bethesda, Doom is actually on Proton's list of recommendations. What a joke. I would request a refund, but I've spent too much time trying to get this broken mess to work right.
Valve, if you needed the money, you could have just asked. You didn't need to go through all of this work to trick me like this.
Hi, me again! I'm the same guy that made the extremely long-winded, sarcastic, and angry report, but still gave it a platinum rating. I've got a huge update. As it turns out, CChromaEditorLibrary.dll is the source of the problem. Apparently it will make the game run like crap, even if you turn off chroma support in the settings. Luckily, some very powerful wizard cast a spell and reversed the hex, releasing the cursed souls from that dll, and all you have to do is download it and overwrite the one steam gives you: https://github.com/Riesi/CChromaEditor/releases All is not well though, as it still takes me at least 5 minutes to load the main menu when starting the game, but hey, it's at least playable now! Again, none of this is Proton's fault. The blame still lays at Bethesda's feet. Proton can't fix lazy and shoddy programming.
Proton-6.4-GE-1 GloriousEggroll
Proton-6.4-GE-1
It doesn't run quite as well as I expected but it's more than playable.
Video cutscenes are played in German, but in game cutscenes are in English. If the video cutscenes play for too long, the game will crash.
The video cutscenes are actual mp4 video files with 2 audio tracks; English and German. So the simplest way to stop DAH from selecting the German audio track is to remove the German audio track from the video files. I have written a BASH script that does exactly that. Hopefully somebody will find a more proper solution in the future, but for now this works.
Simply create an empty text file and copy-paste the script from here:
https://pastebin.com/SdkFUib8
Then make the text file executable and run it from a terminal with the path to your Destroy All Humans! install directory as the only argument passed. It will automatically find and remove the German audio track for all mp4 video files in the directory you gave it. The whole process should take less than a minute. The files are backed up before hand and can freely be deleted.
Additionally, I also found a way to permanently skip the introductory credits:
First, go to <your install directory>/DH/Content/Movies/
Then, delete or rename the following 3 files:
BFGLogo1080p.mp4
Bumper_LegalSplash.mp4
THQNORDIC_LOGO_Color_white.mp4
Finally, create 3 empty files and give them the same names as the 3 files above. You will now get to the main menu faster when launching the game.
One last tweak; you can also remove the splash screen by deleting <your install directory>/DH/Content/Splash/Splash.bmp
The audio is totally boned. The solution is to manually download and save a copy of X3DAudio1_7.dll to the game's base install directory (the same folder as Fallout4.exe and Fallout4Launcher.exe) I used the one found here: https://www.dll-files.com/download/b4ff2a39685c1a6d43f0e56eb350af3a/x3daudio1_7.dll.html?c=YVVsaTVWOHFDZ25EUXdZZUErcjd1Zz09
Changing the resolution to something slightly unconventional will cause the GUI, 3D models, and world itself to go out of sync, disappear, or go extremely low poligon. The MC's left hand had a normal poligon count, but the right hand dropped down to Deep Rock Galactic levels. I can't explain it. It's a Bethesda game.
It will run at 1 frame every 20 seconds if you run it in fullscreen.
Very easy to mouse out of the window, even with bBackgroundMouse disabled.
It's a Bethesda game.
It's a Bethesda game.
It's a Bethesda game.
I doubt somebody would enjoy this experience. It technically works, but the stuttering is too great. There's a massive lag spike like every 15 seconds. You can't have a custom resolution because the GUI and all of the 3D objects are tied to the resolution. You have to download like 50 mods to fix just some of the performance, quest, and other misc bugs. One necessary mod simply uncaps the framerate when it loads saves because how fast FO4 loads data is tied directly to the frame rate. The higher the frame rate is, the faster the game loads. Yes, seriously. Over the years, I have effectively rewritten Fallout4.ini, Fallout4Prefs.ini, and Fallout4Custom.ini probably a dozen times, and it's just impossible to get good performance out of this crap without simply buying the latest graphics card and hoping it can make up for Bethesda's laziness and petty hatred of their own fanbase. Part of the problem is you have to keep making the files write protected so the game won't randomly go through your settings and completely undo everything you're trying to do. They specifically designed FO4 to subtlely revert player settings back to "unplayable mess", because, again, Bethesda has a burning, unquinchable hatred for their fans. FO4 is a mess and I don't recommend it. I've spent years trying to make this thing run competently, and I don't recommend living that life. Do something fun with your time instead. BUT, if that's what you really want, you can get it to work.
Like all Bethesda games, you have to edit the ini configuration files to make the game run smoothly. This isn't specific to Proton, Linux, or even Windows. This is just Bethesda being Bethesda.
To create a character without crashing the game, use this launch option:
WINEDLLOVERRIDES=winedbg.exe=d %command%
To get the Atom Shop to work properly (thank you TrunkleBob!), edit and run this command:
WINEPREFIX="/path/to/your/steamapps/compatdata/1151340/pfx" winetricks d3dx9 vcrun2015
And now for my contribution... :D
Just before FO76 came to Steam, I spent a couple weeks optimizing the ini config files for FO:NV, then a couple more weeks optimizing the ini files for FO4. And I had just finished optimizing FO4 literally one day prior, when Bethesda activated FO76 in my Steam library. So I spent another week optimizing FO76's ini's. And I'm proud to say I fine tuned it so FO76 will run great without sacrificing much visually. So if you would like smoother frames while still looking great, then you can try my ini.
~
To try my ini:
Go to:
/path/to/your/steamapps/compatdata/1151340/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout 76/
Backup Fallout76Prefs.ini so you can revert changes later if you don't like my settings.
Copy-paste the settings here:
to Fallout76Prefs.ini
Run the game!
You should immediately notice a significant improvement to the framerate without losing much visually.
~
If you're still not getting good performance, try lowering the values for fShadowDistance and fDirShadowDistance to 12000. If you're still struggling after that, set iShadowMapResolution to 512. Setting bSAOEnable to 0 will also give a framerate boost.
~
If you want borderless fullscreen, change bFull Screen to 0 and bBorderless to 1. But from what I tested, it looks like standard fullscreen (not borderless) gives slightly better performance anyways, but it's up to you.
~
NOTE: Any time you go to the in-game options menu, FO76 will rewrite Fallout76Prefs.ini, destroying any changes. So avoid the options menu and always keep a backup of it so you don't lose your settings.
It works great OOB, but Steam supplies the crappy UK censored version. So here's how you can install Fallout Fixt, which is a configurable mod bundle that reintroduces cut content, fixes bugs, and adds extra features, all in one go. First, download Fallout through Steam and Fallout Fixt from here: http://www.nma-fallout.com/threads/fallout-fixt-v0-90beta-is-being-worked-on-jan-2019.194562/ Next, go to steamapps/common/Fallout/ and delete FalloutLauncher.exe. Then make a symbolic link named FalloutLauncher.exe, linking to the Fallout Fixt installer you downloaded earlier. Then go back to your Steam library and run Fallout. From here on out, it won't matter anymore if you pick "Play Fallout" or "Play Classic Version". This will run the launcher, which is the link, which is actually the installer. When it asks where to install, select your steamapps/common/Fallout/ directory. When it's done, go back to your steamapps/common/ directory and rename /Fallout/ to /Fallout-backup/. Then go to steamapps/common/Fallout-backup/Fallout Fixt/ and link that directory to steamapps/common/, naming it Fallout. Then link /Fallout-backup/f1_res.ini to /Fallout-backup/Fallout Fixt/f1_res.ini, overwriting the file there. Finally, make one last symlink, linking /Fallout-backup/Fallout Fixt/FalloutW.exe to /Fallout-backup/Fallout Fixt/FalloutLauncher.exe. When all of this is done, you simply run Fallout through Steam and it will run the significantly better version. Easy! Again, it won't matter anymore if you pick "Play Fallout" or "Play Classic Version". I'm pretty sure that just passes easily ignored arguments.
It crashes OOB. But will run perfectly when using "PROTON_NO_D3D11=1 %command%" as the launch option.
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
The reason it's so hard to get this game to run with Proton is, ONCE AGAIN, the useless launcher. Here's how you can defeat it: 1. Delete/rename UbisoftConnectInstaller.exe and ubiorbitapi_r2_loader.dll. 2. Create a symlink pointing to From_Dust.exe in the game's directory, and name it UbisoftConnectInstaller.exe. Example: ln -s From_Dust.exe "$HOME/.steam/steamapps/common/From Dust/UbisoftConnectInstaller.exe" 3. Download this tarball and extract the two files to the ../steamapps/common/From Dust/ directory, overwriting any files: https://www.dropbox.com/scl/fi/zo112j11b3do98vnwzmqw/from_dust_ubisoft_connect_circumvent.tar.gz?rlkey=rq4w0fjtfjt68q1slq6f7lewv&dl=1 4. Set the launch options to: PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% (Yes, you will need the launch options. I could run the game but couldn't get past Ubisoft login without them.) 5. Done! If you start the game and see the blue clouds on a black background screen, with that little spinning circle loading icon thing in the lower right corner, then something went wrong. Alt-F4 and try again. You'll know you did it right when it shows the main menu screen right after the Ubisoft screen. Other problems: The mouse cursor doesn't lock to the window, so windowed mode won't work. You have to keep it fullscreen. The frame rate is hard locked to 30fps. There seems to be no way to increase this (yet). Other than that, it will run great. But there are times where the FPS will drop down to like 20. But then again, From Dust is a 32-bit program so it's likely this is simply a hard limitation in the engine itself. Enjoy!
I can confirm the game will indeed crash at startup unless you delete all(3) .reg files at "(your steamapps path)/steamapps/compatdata/530890/pfx/". After that, it runs like native.
Note: The game is 32 bit and can only allocate 4gbs of memory. It also loads literally everything at launch so if you install mods and it won't start, then you installed too many mods. The only solution is to remove some (likely the larger) mods. This is not a Proton problem, this is a Haydee problem. IE, it happens in windows, too.
You can get this running easily but you need to manually change a WINE setting so it will emulate a virtual desktop at 640x480. To do this, open a terminal and type "WINEPREFIX="/your/path/to/your/SteamApps/compatdata/15710/pfx/" winecfg" all one command, without the outside quotes, but keep the inside if you have any spaces in your path. So for example WINEPREFIX="$HOME/.steam/SteamApps/compatdata/15710/pfx" winecfg or WINEPREFIX="/media/hd3/programs/SteamApps/compatdata/15710/pfx" winecfg. In the new window, switch over to the graphics tab, put a checkmark in the box next to "emulate a virtual desktop" and change 800x600 to 640x480. Then click apply and ok, and run the game. From there, it will run perfectly. Some notes: First, depending on your native resolution, this will run the game in a very small window. It's ugly but if you use a DE with a zoom feature, you can make this work. Second, if you increase the size of the virtual desktop, Exoddus.exe will automatically resize it back down to 640x480, so a larger virtual desktop won't help you. In addition to that, if you click the mouse while using a larger resolution, Exoddus.exe will crash and you will have to kill it manually. So you still need to set the virtual desktop resolution to 640x480. Outside of that, it runs perfectly. :)
You can get this running easily using two different methods. You can use "-interline" as a launch option, or you can manually change a WINE setting so it will emulate a virtual desktop at 640x480. Using "-interline" as a launch option will put ugly horizontal black bars all over the screen, making the game darker and UNdebatably decreasing the picture quality. (Injecting black bars into pretty much any picture will make it look worse. There is no debate here.) The upside is you get to run the game fullscreen, and that's the only advantage to using "-interline". The second option, the virtual desktop method, gives better picture quality but you'll be running it in a 640x480 window. I think the virtual desktop method works better because there's a 30fps cap on Oddessy and Exoddus anyways, so that combined with the blackbars makes fullscreen look like crap. To emulate a virtual desktop, open a terminal and type "WINEPREFIX="/your/path/to/your/SteamApps/compatdata/15700/pfx/" winecfg" all one command, without the outside quotes, but keep the inside if you have any spaces in your path. For example: WINEPREFIX="$HOME/.steam/SteamApps/compatdata/15700/pfx" winecfg. In the new window, switch over to the graphics tab, put a checkmark in the box next to "emulate a virtual desktop" and change 800x600 to 640x480. Then click apply and ok, and run the game. From there, it will run perfectly. Note: If you increase the size of the virtual desktop, AbeWin.exe will automatically resize it back down to 640x480, so a larger virtual desktop won't help you. In addition to that, if you click the mouse while using a larger resolution, AbeWin.exe will crash and you will have to kill it manually. So you still need to set the virtual desktop resolution to 640x480. Outside of that, it runs perfectly. :)
Videos don't play and there simply doesn't seem to be a way to make them play. From what I can tell, this could be a codec issue where Proton doesn't ship with the right codec, while all versions of windows come with it preinstalled. I've tried many solutions, including installing quartz.dll, devenum, and CCCP, and nothing works. The only solution I couldn't test, because it didn't install, was installing WMP9 via protontricks/winetricks. Presumably, installing WMP9 would have also installed the proper codecs. But this couldn't be done, as Proton seems to only use win64 prefixes and WMP9 can only be installed on a win32 prefix, as there isn't a 64 bit version of WMP9. So I'm throwing in the towel on this one. I hope someone in the future can get something useful from this information. As an interesting side note, there is an "original" beta branch where the problems are reversed. The videos play but the in game audio doesn't work. I haven't had any luck making it work there either. I even tried re-encoding and swapping the videos and in game "oddio" between the two branches and still no luck. It just refuses to work. Good luck to those of you in the future!
The game runs perfectly, bar exactly three problems. The first is that the game will crash upon loading an actual level if you use the anti-aliasing setting: SSAA 16x. You can resolve this by setting "PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%" as the launch option. The second is that SSAA 16x causes huge dips in the framerate. Both of these problems can also be solved with the exact same solution: just don't use SSAA 16x. TBH, anti-aliasing in this game is quite unnoticeable. It really doesn't add much at all to it, so I just turn it off all together. The third problem is that all of the text in the Steam Overlay will be replaced with rectangles, including the fps counter in the upper left. It randomly fixes and breaks itself over and over. I have never seen a game do this and haven't found a permanent solution yet. A temporary solution is to save then load that save. Aside from that, it runs great. Nearly platinum.
Installed and played great. No fullscreen, alt-tab, or controller problems to speak of. The only issues I experienced were:
- Some early access bugs
- Most of the fun comes from multiplayer and nobody is online. Ever. I played literally 1 online session in 4 hours. And it lasted 15 minutes. I spent a lot of time waiting for players to join, but nobody ever showed up. You can still solo levels, but without other players, it feels dead.
But performance wise, this was a platinum experience. Not a single Proton issue to speak of.
This was with v0.9.0b5
Works great OOB. Like native.
I'm glad this works so well with Proton because I was a backer for the game back when they promised a native Linux port. They broke their promise. The port never came. So now I can finally play the game I helped fund the development of. Thank you, Proton!
Installs and runs great! No problems I can think of. What a great game, too.
Multiplayer is non-existent. It's not necessary to enjoy SMR but it is more fun if you play with other people. The problem is that SMR was removed from Steam so online multiplayer is basically dead now. Presumably couch CO-OP still works perfectly fine OOB though.
I don't know how everybody else is getting great performance with this. I have to put all of the graphics settings at their absolute lowest to keep a steady 60fps. Proton version 4.2 gave a big performance boost, but there is still a lot of ground to gain here. But all of that said, it doesn't crash and all of the issues I've encountered have all been graphical or related to the framerate. It's still playable but it looks like blurry crap. It's a shame too, cause it's a great game.
My GPU was running at 100% the whole time. I kept turning the graphics settings down, but even on the lowest settings (to the point where it looked like a 2002 game (Seriously! Army Men RTS looks better than this!)), it was still using up about ~70% of the GPU. I don't want to accuse Paradox of running a bitcoin miner in the background. I'm just saying a nearly flat surface and a handful of low poly models shouldn't be taxing my GPU like this. But YMMV.
The game actually does run. The problem is Paradox's launcher. That's what causes it to silently crash on start. The solution is to circumvent the launcher. This is probably the easiest way to do this: 1. Go to the install folder and move/link Aftermath64.exe, Aftermath_Data, and MonoBleedingEdge to the launcher folder. 2. Go into the launcher folder and rename/delete Paradox Launcher.exe. 3. Rename Aftermath64.exe and Aftermath_Data to Paradox Launcher.exe and Paradox Launcher_Data, respectively. This will make Steam skip the launcher and run the game directly. Which I would suggest doing even if the game runs just fine for you anyways.
There was crackling at first, but it seemed to get resolved when I switched to DX11.
If you have a controller plugged in, the game will force you to use it. You have to disable the controller in the settings menu.
I was having some real performance problems, given my hardware. The game was stuttered quite often and I couldn't seem to get the FPS to go above 55. By default, it uses DX9 and I switched it to OpenGL. I didn't notice much of a difference. I played with the settings a lot but only got about a 10 frame difference from the highest settings and lowest settings.
Then I switched it to DX11 and the frame rate instantly went to 170. With all eye candy enabled, I'm getting a comfortable 120 fps.
I highly recommend enabling DX11 right off the bat, and disabling "Sync CPU to GPU". Those two settings gave way more of a performance boost than just about anything else. If you're still having problems, turn the shadow quality down to 0, and disable HDR and other shadow effects.
Broken ***BUT...***
I have found that if you spam either the enter key or spacebar as soon as the game goes fullscreen, all the way until you see the loading screen, the main menu will load right after. If you see the loading screen, and the star is spinning quickly or the loading screen is up for any longer than about 5 seconds, that means it didn't work that time. Close the game and try again. It may take several attempts but the main menu does load.
However, when you try to start a new game, you get the difficulty selection screen, then another loading screen, and presumably the game is supposed to start right after that. But it's only a black screen. I haven't figured out how to get it to do anything from there.
But hey! This is progress! Hopefully somebody else can pick up where I left off here.