Did not notice any issues in the game.
Did not use any mods or anything and the game works out of the box.
Ignoring the first launch launcher issue, the game is fully playable without a single issue.
-q
Can only change the resolution on the main launcher. Obligatory on first time launching the game.
Steam does not support Cloud Saving for this game
-q as a command should ignore the launcher
prime-run gamemoderun %command%
used protontricks to install .NET 7 and the SADX mod loader
mods arent as necessary for this game as they are with SADX but still this port has many issues inherently (what i'm trying to say is that the port runs well on linux, its just that the port itself isn't good)
Works very well
When playing with nouveau Drivers the game was running very slow, changing to proprietary Nvidia drivers fixed this to me.
Audio is mixed weirdly, meaning some music and voice lines start too early. Unsure if this is just a Linux thing or an issue with the remaster itself.
The default fullscreen wasn't actually ran as fullscreen, I was able to fix this through KDE Plasma's System Settings: Window Management -> Window Rules -> Add New then adjust the position, size, maximized horizontally, maximized vertically, fullscreen options to apply initially with your desired configuration. set window type to normal window and set match whole window class to yes, with the window class application exact match to "steam_app_213610 steam_app_213610". Probably other ways to do this with other desktop environments but this is how i dealt with it with what I had.
You'll want a fix for the fullscreen (or play in a windowed resolution that isn't fullscreen). Other than that works perfect on default proton.
PROTON_USE_WINED3D %command%
This is the vanilla game.
The game would crash to desktop after the end of City Escape, after the score count up, at the moment it would show the first achievement / say "saving game". This is regardless of being full screen or windowed.
I had to set the launch command to PROTON_USE_WINED3D=1 %command% and then it ran fine with proton 9.0-3 (successfully completed the first level, then the next one, then chao garden shenanigans; save seems to work).
Installed dotnetdesktop7 for SA Mod Manager
Vanilla game works fine, but the game is best played with mods if you're willing to tinker. Install the SA Mod Manager to the game's install directory or the mod loader will not load correctly on startup. Make sure you install dotnetdesktop7 as SA Mod Manager relies on it.
If you're modding the game, also make sure that you change from Borderless Windowed to Fullscreen in SA Mod Manager or you will encounter strange performance issues. There seems to be some kind of problem with GPU utilization if the game isn't running with exclusive Fullscreen. If you want anti-aliasing, make a DXVK config forcing MSAA.
Runs great, minus slight flickering
Flickering during the stage end score tally
When a stage ended and the score tally was brought up, the ending screen slightly flickered. Ran fine otherwise.
WINEDLLOVERRIDES="d3d8=n,b" gamemoderun %command%
dotnet7, dotnetdesktop7
Zero issues with ge proton 9.6. If you want to play with mods (HIGHLY reccomended for this game), install the required proton components, use my launch options and replache Launcher.exe with the mod loader. I reccomend starting the game without any mods for the first time or it may crash at launch.
Modding the game using SA2 Mod Loader is also very easy on linux. Was able to install and run mods such as HD GUI for SA2, SA2 Render Fix, Cutscene Revamp, etc.
Was able to play the entire game in Linux with 0 issues on both a desktop and Steam Deck; with 0 mods.
Perfect. Playable all three stories from start to finish without issues.
If the Configuration Tool doesn't detect your external gamepad, then go to the game's properties>Controls, and enable Steam Input for this game. This will force SA2 to detect your gamepad as a Xbox controller. Set the Configuration Tool to use your gamepad in the Controls tab.
This game runs better on Linux than on Windows. Just use vanilla proton and you're good.
DXVK_FRAME_RATE=60 %command%
Wouldn't even launch with proton experimental, worked flawlessly when dropped down. Of course there is the initial menu and it not switching to controller by default, but that happens in windows anyway.
Works perfectly.
Just install and play.
Game runs perfectly fine, but you need to set the player 1 input device to gamepad in the launcher
Have to change input in launcher on first start up
you have to use the touchpad to configure the launcher when starting the game for the first time
runs well and couldnt find any issues or bugs, use touchpad to configure launcher.
Sometimes the background music gets crackly. Lower volume seems to help a bit.
-q
CPU 6 watts GPU halved
No Steam Cloud which can be annoying
Runs excellent (minus one small issue)
Graphics freeze for 5 seconds every 30 mins or so. (Might just be my window manager but it's specific to this game.)
I am always nervous about older titles and compatibility but was pleasantly surprised when this game booted right up and just worked. I continued playing my save I started back when I used Windows for a bit and had a blast. No bugs to report on my end.
$(echo %command% | sed -r "s/proton waitforexitandrun .*/proton waitforexitandrun/") "$STEAM_COMPAT_INSTALL_PATH/SA2ModManager.exe"
Installed vcrun2010 and vcrun2019
System notifications cause a second of lag when they appear and disappear.
I experienced some crashes when trying to play the story mode with mods, usually after cutscenes. The stage select, boss rush and kart race modes ran with no issues.
The launch option above will redirect steam to the mod manager upon pressing play. Make sure to force the mod manager to run with Proton.
Will need to use Steam button + Touchpad to configure in the launcher when the game initially starts.
Runs perfectly OOTB.
Played through all 3 story modes twice (because I forgot this game doesn't have cloud saves) & 2P Battle Mode, everything worked with zero issues.
Game runs fine out of the box however the audio seems to be bass boosted in a sort of way
Had to change to gamepad layout in the launcher. Had to restart the first time as it wasn't detected originally for some reason.
Annoying launcher requires changing to gamepad mode and using the touch screen but once launched the game is fine.
Game works well out-of-the-box. Installing mod loader breaks stock Launcher, but this issue can be solved.
Installed mod loader, renamed original Launcher.exe, symlinked sonic2app.exe to Launcher.exe
Out-of-the-box, the game has a launcher for configuration which must be operated with the touch screen. This can be mitigated by renaming or deleting Launcher.exe and symlinking sonic2app.exe to Launcher.exe.
The game works perfectly out-of-the-box, I didn't notice any issues. I installed the mod loader and am using it through Bottles, and the stock Launcher ended up breaking in Steam, with an error that showed up anytime I clicked the play button. To fix this, I renamed the stock Launcher and symlinked sonic2app.exe to Launcher.exe. The mod loader can perform all the actions of the stock Launcher and more, so no functionality is lost. This probably isn't the cleanest solution and may break in the unlikely event this game is updated in the future, but it works and is easy to redo.
Emblem shimmers, certain explosions, flames, and portals aren't rendering properly. This is something I experienced in Windows as well, afaik it's an issue with certain switchable graphics cards. Your mileage may vary, but the flames and portals are cruicial to newbies. Experienced players can get around by muscle memory/knowing what/where to expect them.
Missing textures aside (on my end, ymmv) it's a pleasant experience that feels almost native. Graphical issues required fixes too kludgy to recommend on Windows and seeing them replicated here makes me think it'll require even more messy work. Users with dedicated graphics cards (ie non-switchable graphics/non-Intel) shouldn't have these issues. Overall recommended.
The single player experience works out of the box.
Runs well and plays well, multiplayer untested however given the fact that multiplayer is local only i doubt that it wouldn't work
DXVK_FRAME_RATE=60 %command%
I was able to 100% the game without experiencing any Linux-related bugs.
If your monitor's refresh rate is greater than 60 fps, the game will run too quickly. This can be fixed with the "DXVK_FRAME_RATE" launch option.
The SA2 Mod Manager works perfectly under Wine. To install mods with the "one-click" feature, I used the one-click URL as a command-line argument for the Mod Loader; in my Linux terminal, I typed: "wine SA2ModManager.exe (One-Click Link)" in the game's directory where the mod loader was.
DXVK_FRAME_RATE=60 %command%
It has the typical model load-in as you'd expect from a 1999 game, microstutters if you're doing something HEAVY in the background but you have to be looking REALLY hard. Basically flawless under Proton. It would work without tinkering, but it will play way faster than expected (because the time-scale and physics are capped to the FPS, 30 is how it would appear on the Dreamcast, 60 is how it is on everything else.) I also used the most up to date Proton (excluding Experimental, which would be Proton 7.0)
Game and launcher work fine out of the box with Proton 7.0-2
Played the game entirely vanilla and didn't have any problems with this game whatsoever. The launcher worked perfectly and I was able to select my controller. In the past I had trouble with this, and if the game won't let you select a Gamepad option for controls, right click the game > Manage > Browse local files and delete the two files in the game's "Config" folder, then relaunch the game.
- Played with a Steam Controller and an Official Nintendo Switch Pro Controller
- Played without mods, though likely SteamTinkerLaunch could be used to make using mods easier by setting the Mod Manager to launch as the game's executable (meaning you may not need Bottles for it separately)
- Game has a bug (not Linux specific) where on high refresh rate monitors it may run too fast. Using your preferred framerate limiter can fix this, for example:
- MangoHUD:
mangohud MANGOHUD_CONFIG="fps_limit=60;no_display" %command% - DXVK:
DXVK_FRAME_RATE=60 %command% - Gamescope:
gamescope -r 60 -o 60 -- %command%
- MangoHUD:
