DoomBot[Q]
Published
Loads up DosBox, starts loading the Build3d engine, then swaps resolution, appears to attempt to load initial intro video, but then crashes instantly.
Bummer :(
ERROR: P (HRESULT = 0x80004003) window pops up over the game window, clicking ok closes the game instantly.
Excellent experience, despite the small performance degradation. This game runs on potato hardware, on higher end hardward it will be fine.
About a 20% degradation to performance in comparison to Windows, still perfectly playable.
Runs flawlessly on the current Proton Experimental on some seriously old hardware. There is a performance difference between running it on Windows 10 and on Alma Linux (60 vs 40 fps at identical settings), but I suspect with a much beefier gpu the gap would narrow a lot. Keep in mind the HD4600 I am currently using is doing this with experiemental Vulkan 1.0 support.
Linux Native version requires SDL_VIDEODRIVER=wayland %command% to get running on most modern Linux OS, and texture alpha's are not working correctly via OpenGL, showing white instead of colored transparencies. And on enterprise linux OS (Red Hat, Rocky, Alma, etc...), this option is completely broken, as is Vulkan rendering.
Running it through Proton Experimental lets you enjoy the game without issues on Wayland equipped systems, no fussing required. Using the DirectX 11 renderer works identically to the Vulkan one, as it's all going through Vulkan anyways. Very smooth performance.
On more powerful gpu's, there shouldn't be as much performance degradation, but as I've played it, it's a stuttery mess.
Performance degrades nearly to 1/4th of windows performance.
An absolute stuttery mess on my hardware, but it DOES RUN. A gpu upgrade will sort it out, and once I do get a new GPU, will update this accordingly.
Works perfectly with either D3D or Glide
Thanks to the compatibility patch that was done in 2021, it run flawlessly in Glide mode, and nearly perfectly in the default launch mode (which is Direct3d). The only tiny caveat with Direct 3d mode is that there's a tiny row of pixels around the edge of the screen that moves with the scene, but that's it.
I will be trying a controller profile for it at some point, but for now, I'm quite satisfied with the results.
When launching, a WINE dialog box pops up stating "Invalid command line argument: -changedir"
If you don't let the game window focus automatically while it starts(for example, if you are mucking around with steam itself while the game launches), the game will not be displayed at all, forcing you to force-quit the game and restart it.
By default the game turns on 3D acceleration, which limits performance to about 20 FPS. Immediately go to the options menu and turn off 3D acceleration, which will allow the game to run at a flat 60 FPS
Using Proton 5.13-6, the game runs perfectly as expected, with no issues. On Experimental and 7.0.1, the screen becomes tiny and upside down, making it completely unplayable. On other versions, it simply refuses to launch.
Works exactly as it should, unlike on Windows 10, where it's basically unplayable.
Max settings, works super smoothly.
Played the first 2 levels for a quick test, and no issues.
Borked, direct3D error
After running setup and selecting direct3d from launcher, when you hit play game, it loads a black screen stating that it cannot find a suitable direct3d graphics adapter.
Runs flawlessly.
Needs to be ran two times from Steam, once for installation, and second time for initial patches, but once that's done, click play, and enjoy (Windows installation requires this sometimes too). No modifications required.
