Forum Replies Created
-
Posts
-
the only change is the one mentioned in the changelog post, which unfortunately was necessary since after a recent Windows Defender update various Steam games didn’t launch anymore with vorpX.
As mentioned in the above post you can check the ‘Use legacy hooking’ checkbox in the config app to use the original hooking method if the new default method doesn’t work for your game.
Checked the game this today. There seems indeed to be an issue with shadows that was introduced some time ago. I will have a closer look next week, shouldn’t be too hard to fix since it worked in the past.
19/12/07
vorpX 19.3.1.2 has been released.This is a hotfix that addresses an issue with some Steam games frequently failing to start with vorpX after a recent Windows Defender update.
No other changes. In case you wonder: the next regular update will be released before Christmas.
The hotfix makes vorpX’s prior alternative hooking method the new default, which is more compliant with what Microsoft considers the ‘official’ way to hook into programs. If vorpX now fails to hook into a game that worked fine for you before this hotfix, try the ‘Use legacy hooking method’ checkbox in the config app to revert to the original method.
Did you run the DirectVR scanner after entering the game world? After a successful scan the FOV should be correct.
If that does not work and you happen to have any mods for the game installed, please try without mods.
If I nderstand you correctly a similar issue occurs also with the Oculus desktop, which seems to indicate that there is some general issue with getting the Windows desktop capture API working. Not really sure what to recommend here, sorry.
You could try to use the desktop viewer with the -output 0 cpmand line argument, just to be sure. Although that shouldn’t make a difference if you just have one monitor connected.
Please read through the guide linked above thoroughly. You can’t possibly have done that within two minutes. :)
Please make sure that your Windows 10 is updated to version 1903 (1809 might also work, but I’m not sure). If you are unsure about that run click the start button and then type: winver [ENTER]. The window that now opens should contain the line ‘Version 1903’.
If you experience this with several games, the most likely issue is a conflict with some other program that also hooks into games. Typical cases would be invasive AV software, GPU/CPU utilities or chat programs that can show notofications in games.
You can find more detailed information about the matter here.
@ james: if vorpX does not update automatically on your PC, you can reinstall it using your web installer. If you don’t have it anymore, you can get a new one here.
If you have multiple monitors attached to your GPU, try to remove all except the main monitor. If that helps, you can later try to launch the desktop viewer with the -output paramter (e.g. -output 0) added to the target field of its shorcut. That you can define which monitor to use for the desktop viewer.
Please make sure to use the Steam version of the game and if you changed any vorpX settings, reset the profile to default in the config app.
Also make sure to remove any mods if you have mods installed for the game.
DirectVR tracking/FOV should work out of the box for HL2 without even running the memory scanner.
Alternatively you can add arbitrary resolutions yourself instead of using DSR, which in many games is better since that way you can choose resolutions with uncommon aspect ratios. You can find detailed instructions including a list of resolutions that make sense for vorpX in the “Custom Resolutions” section of the vorpX help (or here).
Yes.
BTW: You can easily check whether a game is supported in the config app. All officially supported games are listed on the local profiles page. If you do not see a game there, chances are that a user profile exists, which you can check on the cloud profiles page.
This message might get shown if the server session gets invalidated while being logged in, although normally vorpX should notice that and change the state to logged out. If you haven’t done that already, try directly after logging in, sessions time out after 10 minutes or so of inactivity IIRC.
Apart from that: can you download profiles from the cloud? In that case there might be an issue with your firewall preventing the upload.