The game itself have a minimum requirement of 6GB RAM. I'm guessing DXVK and Wine have some overhead so it's kind of surprising that it's at all playable.

View this comment - View article - View full comments

Quoting: GuestUnfortunately it’s impossible to get an idea about what the game is from the comments on GOG, and I can’t find a gameplay video of it on youtube.

https://www.youtube.com/watch?v=Noa6d-Rro_8 [External Link]

View this comment - View article - View full comments

Quoting: TheSHEEEP"Coming to PC Mac Linux"
*sigh*

A port to the original IBM PC 5150? That's quite impressive. Wonder if it is clone compatible?

View this comment - View article - View full comments

Quoting: lejimsterOk, so I have been testing the patch for a few hours, haven't experience one hang on either Rage or Wolfenstein N.O. with it.

That leaves just one major problem left with 32-bit Rage now, the megatexture corruption.

https://youtu.be/EUwq4dbnFkA [External Link]

Great! I will file a new bug for the menu hang. The patch is most likely not the right way to solve it though.

The textures was reported in bug 107694 [External Link] but sadly nixed by Mesa devs.

View this comment - View article - View full comments

Quoting: lejimster

Quoting: ziabiceFinally I can put my hands on RAGE and Wolfenstein!

Been playing Rage. Although only 64bit works properly for me and I had to add xact to get the sound working.

I need to do some driver testing to see if its just a buggy version of mesa-git, but 32bit Rage and Wolfenstein N.O. tend to crash in the menus.

I think this is the problem:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=bc65dcab3bc48673ff6180afb036561a4b8b1119 [External Link]

Though I'm seeing hangs, not crashes, in the menu in Rage, haven't tried Wolfenstein yet.

Could you try if this fixes the problem for you?
https://pastebin.com/iwGynY9E [External Link]

View this comment - View article - View full comments

Quoting: g000hFallout 3 GOTY - I tried this, but it failed for me - I'm aware that there are tweaking steps involving xlive.dll and using "/tmp/proton_run msiexec /i /path/to/xliveredist.msi" but I don't have and couldn't find "proton_run" (The command "find / -name proton_run" does not find it on my PC. Could not find it to download.) Running Debian Buster and trying latest Proton beta (after the more stable one didn't fix the problem.)

Replacing FalloutLauncher.exe with Fallout3.exe seems to work:
https://github.com/ValveSoftware/Proton/issues/370 [External Link]

View this comment - View article - View full comments

Quoting: x_wingKDE Neon (Ubuntu 18.04) here with Mesa drivers (18.1.6). It's running fine for me, just took a while to start the first time (you get a blurry window for about 30 secs.). The only problem are some artifacts while you move the camera, out of that, the frame rate and mechanics works fine for me at full graphics.

I'll try with Mesa 18.2RC and check if the artifacts go away...

EDIT: Ok, tested with 18.2RC2 at the artifacts are still there. Fortunately I figured out that they're generated by "Ambient Occlusion" option in the graphics setting. Disabling that feature all the artifacts goes away (I can play at max setting, only need to disable that effect). Definitely it takes some time to start the first time, probably because it compiles and creates a cache of shaders.

EDIT2: Video [External Link] showing artifacts and how they disappear when disabling Ambient Oclussion

An apitrace and bug report should be helpful if you have the time!
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa [External Link]

View this comment - View article - View full comments

Turning off esync with PROTON_NO_ESYNC=1 got rid of the crashes I had in Carmageddon MD, increasing the file open limit wasn't enough.

View this comment - View article - View full comments

Quoting: GuestRunning Doom in Steam Play does not work for me.[...]

I think it still starts up in OpenGL mode, try setting the launch option "+r_renderAPI 1" to force Vulkan.

View this comment - View article - View full comments

I've had some problems with (unsupported) titles* opening file descriptors like crazy and eventually crashing. Not sure if it's a bug unique to Proton or a Wine issue.

* Carmageddon Max Damage, Quake Champions and possibly others.

Apparently this is because of Proton using the esync patch:
https://github.com/zfigura/wine/blob/esync/README.esync [External Link]

The comments in that file doesn't seem correct. Debian still have a 4096 limit by default. Anyhow, raising that limit does get rid of the errors. Carma still crashes but that's another bug.

...and esync can be turned off with PROTON_NO_ESYNC:
https://github.com/ValveSoftware/Proton [External Link]

View this comment - View article - View full comments