I just tested this out. Download Deus Ex GOTY and then Revision, ran Normal deus ex first then linked the prefix folder to the number revision would run under (probably not needed but saves space).
Revision appears to run fine for me. Maybe just try running it all via steam instead of doing some manual install method yourself!!!

@jarrard
How are you downloading Revision? When I attempt to install the mod with Deus Ex GotY installed, I get this error.

The only way I can think of someone installing this mod on Linux is if they use Proton/Wine to install Steam and use a Proton/Wine Steam install to trick Steam into thinking its running on Windows to allow the patch to download.

@jarrard
When you say, "linked the prefix folder to the number revision", do you mean used WINEPREFIX to point wine to install in the ~/.steam/root/steamapps/common/Deus Ex/Revision directory, or point to the ~/.steam/root/steamapps/compatdata/397550/pfx directory? What exactly did you do?

EDIT:
Nevermind, I got it. You have to search for Revision in your games library, then right click on it, and go to compatibility, and force enable Proton there. This will fix the error message. I will post back with results.

Game runs and installs fine for me after running Deus Ex unmodded first, mouse cursor is grabbed and stuck to the bottom left unfortunately makes the game in its modded form completely unplayable. Its so close, seems like the game works for some and not others.

Compatibility Report

• Name of the game with compatibility issues: Deus Ex: Revision
• Steam AppID of the game: https://steamdb.info/app/397550/

System Information

• GPU: Radeon RX 5500 XT

• Driver/LLVM version: Mesa 21.2.0-devel (git-d677120cae) / LLVM 13 git master

• Kernel version: 5.13.0-pf2+

• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfoamd

• Proton version: 6.12-GE-1 / Experimental

• Logs:
  GE D3D: steam-397550ged3d.log
  GE OGLa: steam-397550geogl1.log
  GE OGLb: steam-397550geogl2.log
  Experimental D3D: steam-397550exd3d.log
  Experimental OGLa: steam-397550exogl1.log
  Experimental OGLb: steam-397550exogl2.log

Got it running, and here are the results. The game seems to ship with two different OpenGL renderers, according to the render select menu. I encountered three different bugs here, and i'll show them as the test procedure moves along.

GE D3D:
The brightness works, and there is no washed out textures as mentioned in https://github.com/ValveSoftware/Proton/issues/798. There is also no wireframe bug, unique to OGL, which I will get to now.

GE OGLa:
brightness slider is broken, and there is also a visible wireframe bug in the rendering for OpenGL, when a 3D object passes over the translucent main menu.

GE OGLb:
same results as GE OGLa

Ex D3D:
brightness slider works, textures are NOT washed out, and there is no wireframe glitch. It works perfectly.

Ex OGLa:
brightness slider works, textures are washed out, wireframe bug

Ex OGLb:
same results as Ex OGLa

The game also freezes and stutters when you are moving the brightness slider. Performance is noticeably lower using D3D.

Here are some screenshots of the default brightness levels of each render using Experimental.

Ex D3D:

Ex OGL:

How are you downloading Revision?

Did you press play now? never got that issue. Yep enable compatibility.

I just used DX9 option, there is also a DX10 mod floating abouts if you want to try that.

The OGL options may not have all the fancy updates by community.

Proton version: 6.12-GE-1 / Experimental : I used proton 6.3-5 for testing. Didn't notice any performance issues but if your trying to get 200fps then perhaps.. playing at 4k here got well over 100fps.

@jarrard
With the way you explained how you got it working, sounds more than just “pressing play” but ok. No need to adjust prefixes like i tried originally which you evolved off of.

Since it’s a mod, it also will always say “install now” highlighted in green, unlike it being greyed out, like a traditional windows game on linux, which brought further confusion.

Considering how much you lacked testing compared to me, you don’t know how much better OpenGL runs compared to D3D.

Already tested D3D10 on GotY that i linked earlier if you didn’t notice.

https://github.com/ValveSoftware/Proton/issues/798#issuecomment-570986587

Since you know about D3D10 kentie, and considering how about you blindly assumed i didn’t know about it, how about you test on Revision since you know it’s a thing?

No need to adjust prefixes like i tried originally which you evolved off of.

I said I did it to reserve space otherwise you have 2 prefixes for 1 game basically. :)
I was only doing a quick test to see if I had your issues. I DID NOT, no need to get nasty!

@jarrard
ok dude, save that less than 1gig of space. revision is completely different too, it’s hard to call it the same game.

you saying things like “did you press play now?” came off completely disrespectful, since like i mentioned, it’s a mod that will have a green install button even when compatibility isn’t set, which is what threw me off, and can throw someone else off too.

windows games on linux that don’t have compatibility set will have a greyed out install button. this isn’t the case for revision since it’s a mod.

did you even try opengl? there’s a big fps drop during intro cutscene, when the camera pans out to the big firefight in the road on D3D, and my machine is decent.

EDIT:
Since the INSTALL NOW button shouldnt be green unless proton compatibility is enabled on it, i made an issue about the UI bug

ok dude, save that less than 1gig of space. revision is completely different too, it’s hard to call it the same game.

I just assumed the mod MAY want registry and config files from the base game pre-existing in the prefix, so linking DeusEx to the mods prefix number works pretty well. I've done it before.

There is a option to install and also play now. I used play now button and it worked, but I think maybe your problem is steamplay has not been enabled for non-whitelist games which is a steam settings option you can tick on. I had that ticked on, hence I never get bad platform errors.

I just tried the recommended d3d9 option. Of cause there could be performance issues throughout the game which I have not tested yet. Only the intro/tutorial.

So i cant "enable steam play for all titles" because of another bug when having a third party Proton in the ~/.steam/root/compatibilitytools.d directory. Doing so will always have that option unticked after the required restart of Steam, hence me manually needing to enable it for each game.

When removing Proton-GE and enabling steam play for all titles, the INSTALL button is now blue instead of green like in the picture i posted earlier. Thats one way of fixing it, but not everyone, like me unfortunately, has that option enabled. Its still a Steam UI bug, as the button should be greyed out since proton compatibility wasnt enabled on it.

https://github.com/ValveSoftware/Proton/issues/4958#issuecomment-878457955

The "play now" button doesnt appear until after its installed, which is why i thought you were being a smart alec lol. I'm going to make an issue about the other Steam UI bug now.

https://github.com/ValveSoftware/steam-for-linux/issues/7921

Yes, when you set Proton-GE as default, the box will remain unticked and steamplay isn’t enabled for all titles.

Ok, well technically you shouldn't be using proton-GE by default unless there is a reason too, such as a game doesn't work. Otherwise it makes it hard to post bug reports because GE has allot of extra work arounds going on. I generally try with default proton to start with anyway.

It doesn’t matter what your default Proton is as long as you provide a log of Experimental for them to see as well. I provide GE logs along with Experimental to provide as much information as possible.

Not sure if this is a regression or if I misconfigured something since I switched from an Arch based distro (Endeavour) to Ubuntu 22.10 recently. Deus Ex Revision launcher and then load graphic and window show briefly before crashing and returning to Steam.

Tried vanilla GOTY and the same thing happened. All other proton experimental titles I have installed at the moment working as expected.

3700X, 5700XT, Ubuntu 22.10, Proton experimental, Wayland.
steam-397550.log

edit... aaaaaand, it's already fixed. I don't know what I did, if anything, but it's working as normal again now. Please ignore the above comment.