Grovesy
Published
The constant hard crash freezes are making it very to tough to enjoy. I'm only able to complete one in every two multiplayer games.
Multiplayer Stuttering when initially starting any gameplay.
Multiplayer - Freeze requiring the game to be force killed after 10 or so minutes of gameplay.
While multiplayer can be enjoyed reasonably well when it works, I'm finding often the game will lock up entirely after around 10 minutes of gameplay.
I can only speak for the multiplayer here, I bought this on special to investigate the H2M mod being released shortly. However the base game multiplayer is causing me significant issues thus far. I plan to investigate further, potentially adjust my comments here in the near future. However in the mean timethe multiplayer verges on "unplayable" due to the inability to play more than 2 entire multiplayer games in a row.
Played for a solid 6 hours straight with no crashing. Am yet to experience a CTD so far, without any tweaks.
Only audio bug I experienced was with the gatling laser, however that's been an issue that has been around for quite a while, very common regardless of OS
Runs better than on Windows Operating System, hands down, no word of a doubt
I see a lot of memes going around regarding the "constant crashing" of Fallout New Vegas and jokes regarding the game being an unstable mess. Since playing this game through Proton, I can count on one hand the amount of times this game has crashed on me. Managed to spend one session playing for 7 hours straight without a single crash, before eventually having to close the game due to the fact I had been playing for 7 hours straight and guilt had begun to set in. Undoubetly a much more stable experience using Proton that running on Windows. Load times are lightning fast, the on record bugs may still be present, but otherwise the game is a masterpiece, best enjoyed when loaded under Proton. No tinkering was necessary for me.
Issues with full screen display support on Proton 9+, reverting to Proton 8 has provided no issues.
Proton 9 and up was causing the game to crash when attempting to launch in fullscreen mode.
Lot of fun, Surprisingly stable for such an old game. Occasional crashes but those are clearly caused by bugs in the game itself, rather than any sort of support/compat issues.
Managed to downgrade to version 1.0 without issue, however had some trouble installing the widescreen patch. Might've been a me issue. Planning to attempt to get SA:MP running and update on compat in the future. Without downgrading though, switching down to Proton 8.0 was the only requirement to get the game playing without issues.
despite some initial headache getting past the product activation key issue, the game has been running flawlessly since.
Create a .reg file with the content:
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\iDeal-Games\JA2 Wildfire] "Registration"=hex:3c,2f,6f,22,a3,a0,50,22,58,8f,60,22,1e,2d,ad,20
Edit the RunGame.bat file, at the bottom add a new line before start /WAIT "" WF6.exe:
start /WAIT "" regedit start /WAIT "" WF6.exe
Launch through steam, when regedit opens goto Registry and Import Registry File. Select the .reg file created earlier, ensure it successfully imports, then close regedit. Wildfire should launch successfully. You can now go back into the RunGame.bat file and remove the start /WAIT "" regedit line.
Credit to steam user: aeris for finding this fix. https://steamcommunity.com/profiles/76561199018697114
Weird game freeze/messed up display when taking steam screenshots.
You can play JA2 Classic without any tinkering, however to access wildfire you WILL need to get past the product activation key issue. If you're reading this looking for a solution, I have included a brief of how I managed to fix the issue following aeris' advice in a steam discussion page regarding the issue. For some reason I was unable to launch WINE's regedit inside of Widlfire's prefix from the terminal, however adding the regedit launch option to the RunGame.bat file allowed me to successfully import the registry file. Everything's been working solid since, although I have to avoid taking steam screenshots as it causes a weird graphical issue where the screen appears to be overlayed on itself upside down and I can no longer interact with UI.
Scroll down to find Aeris' comment for the product key fix: https://steamcommunity.com/app/215930/discussions/0/1814296273132304445/
For a while there I forgot I was on my linux boot. Played for 8 hours straight with only 2 incidents where I was returned to the main menu.
-skipintro
Occasionally would unload my save game and return to main menu. Autosave ensured no significant progress was lost.
Main menu still says "Exit to Windows." I found that humorous.
