This is the original version of the game, not the BFG edition (discussed in #569 ). Videos are working fine. Gameplay too.
Specs: Proton 3.7-3, Ubuntu 18.04, NVIDIA Corporation G94GL [Quadro FX 1800] (rev a1)
Full specs: https://gist.github.com/adrianlshaw/13b21eae4d9ad3c6c79474396110feed
I wish we could use the Linux binary instead of running it through proton.
Well, technically, you could also use the newer BFG edition that combines both of the campaigns into a single package, and that definitely requires Proton, because it was never ported from Windows.
Whilst it's nice to see this working through Wine/Proton; I'd imagine most people will be better off compiling:
There seems to be packages available in the repos for Ubuntu, Arch, etc.
Perhaps Valve could find a seamless way to integrate projects like these into Steam somehow.
Something better than the "add a non-steam game" route - a workshop mod?
@andrew-mcmahon RBDoom-3-BFG is unstable and misses some important features like achievements and online multiplayer. dhewm3 is also unstable, contains bugs not presented in vanilla and incompatible with most existing mods. Unless these two projects find workaround and can deal with publishers (in which I doubt), I wouldn't want them to appear on Steam.
Found glitches:
Glass windows are fully opaque:
Glass + messed up UI image:
@xDShot Post your system info in a gist, please.
I'm attaching (resized, I forgot that this game is hardcoded to 4:3 aspect) screen shots to show things work on my system.
System:
https://gist.github.com/kode54/3ff952f39b407d6f806a6779838f5335
Using the RX480 listed there.
dhewm3 is also unstable, contains bugs not presented in vanilla
Is it? Could you file bugreports for those bugs and instabilities at https://github.com/dhewm/dhewm3/issues ?
I don't suffer those graphical glitches either so it must be specific to Intel integrated gfx.
Steam system info
I would've thought that online multiplayer is completely dead anyway? (at least according to steamDB)
What I will say is that enabling HDR in RBDoom3-BFG seems to be the cause of some rendering issues.
Drop down a console (¬) and turn that off with r_useHDR 0
Soft shadows are also _very demanding_; the basic stencil shadows are OK.
No real issues with dhewm3 either.
I've noticed the older engine stutters a bit in places and the GUI + videos are 4:3 as they were originally.
Even if the GUI can't be fixed easily; non-stretched/letterboxed videos would be a nice addition.
RBDoom3-BFG screenshots with GALLIUM HUD @ 1080p
dhewm3 screenshots with GALLIUM HUD @ 1080p
A few more comparison pics here and here.
Personally I love having the choice of which edition of Doom 3 to use.
@kisak-valve Requesting an XAudio2 label for this game...
Doom3 from 2004 uses XAudio2? (Very unlikely, unless they updated the soundcode for the Steam release)
Or did you mean Doom3 BFG, which is discussed at https://github.com/ValveSoftware/Proton/issues/569 ?
Oh, shoot, i clicked the wrong one. Dan is right, I meant the other one, original Doom3 uses OpenAL!
@andrew-mcmahon even if there exist some modern port, this games should simply work with Proton, like the others WIndows games on Linux, that the subject here. Advanced users could always try others ports. I just tested Doom3 with Proton 3.16-3 and it works very well. You click, you play! @kisak-valve It could be whitelisted.
https://gist.github.com/legluondunet/0f0a56fb4e9cb743f111385e554fce69
It doesn't launch at all on Intel 7700K with just Intel HD graphics.
Game is working fine now (Proton 3.16-6 Beta).
Doom 3: BFG Edition does not start with Proton 4.2-2. Works correctly with 3.16-8 Beta. Can you verify if it also affects you?
Hello @kmaterka, please add PROTON_LOG=1 %command%
to the game's launch options, try the game with Proton 4.2-2, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
@kisak-valve Sure, log attached:
steam-208200.zip
@kmaterka Here’s a shot in the dark: Try removing OpenVR?
@kode54 Good shot! After removing these two:
./steamapps/compatdata/208200/pfx/drive_c/windows/syswow64/openvr_api_dxvk.dll
./steamapps/compatdata/208200/pfx/drive_c/windows/system32/openvr_api_dxvk.dll
game started.
Although, specifically, it appears it was the input code crashing somewhere related to libfreespace, but that only appears to get loaded if the OpenVR framework is present. It would be beneficial to those attempting to run the VR integration on Linux to fix this, but until then, it would also be nice if the game’s current VR libraries didn’t crash in Wine even without OpenVR installed in Steam, unless those libraries came extra because of something you did.
Most helpful comment
Whilst it's nice to see this working through Wine/Proton; I'd imagine most people will be better off compiling:
There seems to be packages available in the repos for Ubuntu, Arch, etc.
Perhaps Valve could find a seamless way to integrate projects like these into Steam somehow.
Something better than the "add a non-steam game" route - a workshop mod?