- This topic has 10 replies, 4 voices, and was last updated Mar 2, 2026 8:48pm by
.
-
Posts
-
Hello Ralf, I wanted to play Thief 4 with the new update, but I couldn’t.
The Thief 4 profile does not work, there are several problems:
– The mouse cursor does not appear on the screen (but the buttons work)
– The game doesn’t play any sound in my headset (the sound from my Rift S is on the headset audio channel)
– The game camera moves in all directions if I move my head, and I have the impression that the FOV is not good (it’s hard to determine) which makes the game completely unplayable in FullVR (Putting the option in VorpX “Input Settings > Try Pitch Lock > On” alleviated the problem)
– There is no DirectVR Scan button?Other than that the VorpX hooking up is good and the G3D seems to work well.
I’m also using this post to give some settings I found (and that work) that could improve the VorpX profile of the game:
Disable motion blur (Thief\Engine\Config\BaseEngine.ini):
motionBlur=False
motionBlurPause=FalseDisable the black/white vignette effect around the screen (ThiefGame\Config\ThiefGame.ini):
mbForceHideCloakEffect=1Mouse setting (to be tested):
Disable mouse smoothing (ThiefGame\Config\ThiefInput.ini):
bEnableMouseSmoothing=falseReduce mouse input lag (Engine\Config\BaseEngine.ini):
OneFrameThreadLag=FalseReduce mouse lag (ThiefGame\Config\ThiefEngine.ini):
bSmoothFrameRate=FALSE
MinSmoothedFrameRate=0
MaxSmoothedFrameRate=0Settings and optimisation guide:
https://www.pcgamingwiki.com/wiki/Thief
https://steamcommunity.com/sharedfiles/filedetails/?id=233295023(I use the new update, The game is running on Oculus Rift S, I have a RTX 2060 on Windows 10, I don’t have Antivirus, only Defender and no software running in the background. Excuse my bad english)
If you can’t see the cursor while it is supposed to be visible, try ALT+C. This shouldn’t really happen though, I’ll take a closer look at it. In the meantime ALT+C should do the trick.
If you experience anything unwanted sound wise, untick the ‘Use built-in audio device’ checkbox in the vorpX config app. vorpX auto switches to the headset audio device. If that’s not what you want, unticking that checkbox disables the function.
There is no DirectVR memory scanner for the game, that’s correct. Another part of DirectVR however adjusts various settings automatically to configure the game for FullVR mode. Most importantly the camera field of view. Note that initially two restarts may be required until the FOV is right. Works for me. vorpX displays a prompt requesting a restart whenever it considers that necessary.
If you happen to have disabled automatic settings, please re-enable that, otherwise DirectVR can’t configure the game correctly. Also please reset the profile to default in the config app if you tweaked any vorpX settings.
I have completely reinstalled the game without making any changes and I have the same problems.
I’ve done some more testing:
– The VorpX cursor (Alt+C) makes navigation in the game menus much better.
– The only parameters modified by VorpX are in the registry (no modified ini file).
– My game is installed in “D:\Program Files (x86)\Steam\steamapps\common\Thief\Binaries2\Win32\…” (default Steam path)
– My screen and game resolution is set to 4:3But I have a new problem, I can’t reset the profile of Thief 4, when I reset it in the vorpx configuration software (Restore Game Settings) it disappears as it should, but when I restart the game my old modifications are still there (lumasharpen, contrast…) it’s been 4 times that I reset it without success.
EDIT: I managed to reset the profile correctly, I was in the wrong configuration menu (ignore the last paragraph of my previous post).
After this reset the problems are still there.Can’t really say much more than above, sorry. Checked the game for you right away after I read your post to be sure nothing has been broken. If you let vorpX do its thing, it adjusts everything so that the game’s FOV matches your headset FOV. That has been working for years and it is still working today. The registry edit is precisely what you need for the FOV to be right. Just a guess, but maybe some of your manual .ini tweaks affect how the registry value works. Worth a shot to delete your manually tweaked ini files. The game should create new ones on launch, if not verifying the game files in Steam will.
Note that if all worked, the game will run windowed. If you run it fullscreen on a 16:9 monitor with a 4:3 res, it may looked stretched. vorpX takes care of that under normal circumstances.
The only other thing I could possibly imagine is that maybe there is some game of the year edition or something similar with different config paths than the original game, that happens occasionally. If you suspect, it could be that, let me know. Judging from your Steam path that doesn’t seem to be the case here though.
Not sure if there are mods for the game, but if so and you have installed some, please also try without.
Apart from that the only other suggestion I have is maybe trying a full vorpX factory reset in the config app (trouble shooting page).
I have a similar problem with the FOV not being right. There’s a good amount of distortion as I move my head around. Nothing super crazy but way more than in other vorpx games I tried.
I can confirm vorpx is setting the 4:3 resolution and it is changing the registry variable ‘FOVCorrection’. Seems like maybe it’s setting it wrong. It sets it to 29892 in decimal which means it adds around 30 degrees to the 90 baseline.
Or is it just the best it can get and it’s impossible to get no distortions in this game?
I can confirm vorpx is setting the 4:3 resolution and it is changing the registry variable ‘FOVCorrection’. Seems like maybe it’s setting it wrong. It sets it to 29892 in decimal which means it adds around 30 degrees to the 90 baseline.
I didn’t try this game with VorpX yet, but if you have 120° horizontal FOV, it’s usually a bit much (depending on the game). I sometimes played with that FOV value because it can be immersive but yes it can cause distortions in full VR mode when you turn your head (at least in my G2 with some games), unless you zoom more.
You probably can change the FOV manually to a lower value.
I don’t think 120 is too much in this game, game settings let you go up to 110 and it wasn’t enough, going down from 110 only made things worse, more distorted and more zoomed in.
I’d prefer not to have to mess with it manually in the registry as it requires a game restart every time and it takes a while so It’d be extremely tedious but if there’s no other choice I’ll try going higher and see if it improves things.
You just make it harder for yourself that way. I mean, I perfectly get the love for tinkering with stuff, one could say that very same mindeset brought me here. But if I had to choose one single thing where I’d say ‘just leave it alone’, it’s this. vorpX can automatically adjust the FOV to 100% perfectly match the headset FOV considering each and every setting you may have adjusted that affects FOV. You can’t guess better. Maybe with the rare exception of three or four cases where the computation itself contains a guess factor due to some game oddity. This is not one of them though.
So whenever vorpX can compute the FOV, let it do its thing. There’s still a lot to tinker with even if you don’t touch the things you REALLY don’t have to touch. :)
But like I said I see distortions in this game and I don’t see them in some other vorpx games I tried. So you’re saying it’s as good as it gets and there’s just something wrong with this game where it’s not possible to get rid of distortions?
There is only one correct FOV in FUll VR mode, and I can guarantee you 100% that the one computed by vorpX is the right one in this case. Really.
vorpX takes the headset FOV reported by the VR runtime and uses that to calculate the correct game FOV, considering the resolution, settings like ImageZoom etc. Except for a few unfortunate cases where this computation involves a bit of a guesswork in itself – this isn’t one of those cases – there is no margin for error here.
Just make sure to follow the instructions shown by vorpX if there are any. In this case that would be selecting a 4:3 resolution, which typically is the best choice for FullVR anyway since it provides a bit of wiggle room on both sides for vorpX’s frame interpolation when you turn your head without annoying black sliding in.
And if you afterwards still think something is off, just use the FOV offset setting on the DirectVR page of the menu. At least that way you won’t have to guess again yourself if/when you change related settings like ImageZoom.
- You must be logged in to reply to this topic.