Metro Exodus dx11 G3D

[fubar]

I have other problem with this game. I’m using the GOG dx11 version and Vorpx can’t change the resolution and the fov, or maybe they get overwritten by the game. I’m using the official profile and all the settings in vorpx menu are correct.

If it’s not possible to fix please tell me what aspect ratio and FOV I need for Rift S and what other tweaks are needed and I’ll set it all manually in the user.cfg

[Ralf]

The FOV for Metro Exodus is a vertical FOV. With default ImageZoom (1.0) that’s 96 deg. vorpX keeps this constant over all headsets to make potential instructions in user profiles stay valid across all headsets.

If you want to max out the ImageZoom (and thus your Quest 3’s vertical FOV), try 105. I’m not 100% whether I recall that correctly though, is probably slightly off.

You can check the precise vertical FOV required for maxed out ImageZoom in the vorpX logfile. Easiest way to access it is createing a trouble shoot archive in the config app. In the logfife (after launching a game), you find a line that looks like this:

INF: OculusRiftDevice: FOV: XX.XXXXX°

That’s your *vertical* FOV for maxed out ImageZoom. In case of Metro Exodus it luckily happens to be exactly what the .ini file wants.

Caveat 1: might also be OpenVRDevice or OpenXRDevice depending on what you have selected in the vorpX config app.

Caveat 2: don’t get distracted by the term ‘OculusRiftDevice’ in the log, that has historical reasons. It’s the right one for all Meta headsets when using Horizon Link.

[Boblekobold]

In order to go above 90 FOV :
– Open the game’s executable file with an Hexadecimal Editor (like HxD)
– look for the second-to-last “00007042” hex value
– replace it by the desired value (for example : 0000D242 Hex = 105 float)

You can convert float to hex (00007042 default hex value corresponds to 60 FOV).

It seems to work with most versions.

When you set a FOV greater than 90 in the .cfg file, it automatically reverts to 60. This modification will allow you to set the desired value instead.

[Ralf]

Thanks for the heads-up. Guess I should stick to my own recommendation to not do anything vorpX doesn’t do automatically. ;) Unlike me – who forgot it – vorpX is aware of of this limitaion…

Good to know that there is a hack to remove it completely. Probably not a big deal to apply it in in-memory without hacking the .exe. I’ll look into that.

[fubar]

Thanks, it calculated 98 and I applied it with the hex editor and it’s perfect now. Do you guys know if it’s possible to get rid of the dirty screen effect? I tried with shader authoring tool and went through every shader but it’s not affected by this.

[Boblekobold]

Do you guys know if it’s possible to get rid of the dirty screen effect

The gasmask is part of the metro experience ;)

[Author]

Posts