Y|yukichigai
Published
Modified doxboxCARMA.conf and dosboxSPLAT.conf to use output=ddraw instead of output=surface. Significant performance improvement since this avoids using GDI.
Awful framerate through the Glide renderer, even factoring in that it's translating Glide -> D3D which is then being translated again by Proton. Software renderer is decent performance but still looks awful.
Since this runs through DosBox anyway you're better off installing DosBox natively and then running it using the dosbox*.conf files found in the Max Pack install folder.
Slightly better performance than Windows, but lots of framerate stutter
Framerate stutter and large shifts in framerate, but mostly playable.
Intro movie does not show. Screen unresponsive during initial startup until you click the mouse and then hit ESC. Game works fine after that.
In menus, mouse input seemed to click 5-10 pixels to the right of where the cursor was pointing. No effect on gameplay.
This was tested on a non-gaming laptop that has difficulty running the game under Windows. Despite the inconsistent framerate, this is more playable than running through Windows normally.
Game may benefit from some ini tweaks (actually, video.scr) to adjust graphics options not found in the menu, e.g. turning texture filtering down to Bilinear, so on.
Very poor performance on older hardware
Startup logo plays no sound
Significantly reduced framerate (~50%) compared to the same hardware on Windows
This isn't my main gaming rig, but I was still surprised at how much of a performance hit this took just going back a few generations of graphics cards to a 680 GTX, especially when the game is 40fps+ with the same hardware on Windows (on low, but still).
Game works perfectly, separate Options program does not
The separate Options program you can select on launch does not work. Fortunately all of the important settings (resolution, keybinds, whatnot) can be accessed in game.
Works without any extra configuration
No impact on performance compared to Windows. Game runs perfectly.
The lack of mouse input is part of the game, not something caused by Proton. Took me a minute to remember that.
Audio issues and periodic freezes, but performs well outside that
Entering a menu during gameplay stops music. Music does not start again, even if you change levels. Some enemy sound effects may not play as well.
Fullscreen does not remove the taskbar. Setting game to native resolution winds up with either the top or bottom of the screen cut off if you are in fullscreen or windowed mode, respectively. Windowed mode does not stop the mouse cursor from triggering the dock overlay if it passes by it.
Freezing/stutter during combat, particularly when enemies changed animations
Some of the issues with adjusting the game's resolution and fullscreen/windowed more are present even in Windows. However, Proton seems to amplify the problems.
Forced Proton 4.11-12 instead of native
Flickering shadows for items near the edge of FOV
Framerate on Low Graphics is superior even to the native Linux version, while on High Graphics it tanks hard (unplayable). Native Linux version is very playable at all graphics levels, but will not do V-sync.
For reference, the Windows version has unplayably bad framerates on this hardware at any graphics level, far worse than either proton or native.
Works great without any additional configuration
Mouse becomes unresponsive during pre-level loading screens, but there's nothing you can do during loading screens anyway so it doesn't matter.
