[Ralf]

Extremely weird then. Does importing cloud profiles work despite the error? I would assume it to fail entirely if the error is caused by the temp file access that I’m supecting.

[Ralf]

That is the case, but the profile was updated after the last vorpX update – as you could have noticed by reading the very first reply to the original post before posting yourself. Sorry, I clearly shouldn’t have said that, but couldn’t resist. :)

[Ralf]

Guess I didn’t really consider that someone might use vorpX lying on their belly. There’s something to learn every day, even after seven years… :).

The code is shared between cinema and immersive mode and since for cinema mode a negative tilt would make the screen disappear into the floor that is not allowed. I’ll put negative tilt for immersive screen mode on the nice-to-have list, but don’t expect that to be treated with super high priority.

[Ralf]

That is definitely not the error I had in mind. The only directory I’m aware of that is accessed during the profile download is a temp folder that the config app creates upon start, should be virtually impossible that this folder isn’t present.

Considering that I never heard of this issue before: did you maybe set up your user temp folder in some *really* unusual fashion? E.g. moved it to a network drive, write protected it or something similar?

[Ralf]

That’s really odd since in case of nVidia GPUs vorpX is supposed to set the driver setting to off. I’ll check whether something might be wrong with that.

For the most part you can dismiss this message though, vorpX actually ignores VSync normally. The warning (and auto turning off) was introduced since for unknown reasons in some DX9 games the recently added new headset snyc method causes an FPS drop when the GPU is maxed out unless VSync is turned off. Fairly strange since it shouldn’t really matter at all with vorpX whether VSync is on or off.

Long story short: unless you play DX9 games at very high resolutions you normally don’t have to care about VSync at all.

[Ralf]

Just checked the Epic version, works fine here.

Make sure that you download the updated ‘Rocket League [vorpX]’ profile from the cloud I mentioned above. The profile that comes with vorpX currently does not have DX11 support, you need the updated cloud profile.

If you already did that: as always with hooking problems, please first and formemost check the pinned trouble shooting post on top of this sub forum. 99% of hooking problems are caused by some interfering background application, most likely some annyoing and unnecessary third party AV program.

[Ralf]

When hooking into a game (that has a vorpX profile) fails, you should normally see a dialog that offers to install a hook helper to the game folder.

If things fail so severly that you don’t even see this dialog, please check the pinned trouble shooting post on top of this sub forum. Issues like that are usually caused by some annoying third party AV program. If you use anything else than Windows Defender, consider getting rid of it.

[Ralf]

You can re-assign shortcuts in the vorpX config app, but only to keyboard keys and mouse buttons. A wireless mouse with recentering bound to one of the mouse buttons might be a viable idea in your scenario.

[Ralf]

The regular FO4 with vorpX for the most part still makes sense if you prefer playing seated or want to use mods that aren’t available for the VR version. Otherwise the VR version is probably what you want.

[Ralf]

(As usual) the profile was created using the Steam version, also no other reports like this until now. Denuvo doesn’t prevent vorpX from hooking into games normally. The only Denuvo related issue so far I noticed occasionally were longer loading times in a handful of games when starting them with vorpX (e.g. Dishonored 2 was quite extreme when it still had Denuvo). That wasn’t an issue here though.

I’ll re-check the latest game version and let you know if anything changed.

If you happen to use an Oculus headset, make sure to switch vorpX to SteamVR as suggested by the message that pops up when you launch the game with vorpX in native Oculus mode. DX12 games currently crash with native Oculus.

Apart from that: if you haven’t done so already, please check the pinned trouble shooting guide in the ‘Technical Support’ sub forum (or in the vorpX help). Your issue might be related to some overzealous AV program or another hooking conflict.

Edit: Still working here with the latest game version.

[Ralf]

Never heard of that before, but there is a similar issue when trying to open the cloud profile page with a DotNet version slightly below the one vorpX expects. Maybe yours is related. Shouldn’t be an issue on Win 10, but if you happen to still be on Windows 7, make sure that DotNet 4.6.2 is installed. The .2 being crucial here, with 4.6.0 you would encounter the issue.

https://www.microsoft.com/en-us/download/details.aspx?id=53344

[Ralf]

More recent vorpX versions have a new update mechanism that doesn’t use a download helper written to the temp folder, so you won’t encounter an issue like this anymore.

[Ralf]

I’d strongly recommend to leave that as it is, it ensures that your view always is centered vertically. If you still want to change it, you can do that on the DirectVR page of the vorpX menu. In addition to that you might have to adjust the right stick y-sensitivity on the Input page to your liking.

Keep in mind though that the feature hugely improves comfort, which is why all native VR games work that way. Think twice (or better thrice :)) before you disable it.

[Ralf]

Your AV program is one of those that make it quite hard for their users to actually disable them. Disabling the scanner is not enough, you also need to disable the ironically named ‘Advanced Threat Protection’, which rather unadvanced blocks Windows functions used to hook into games.

Alternatively you might want to consider switching to Windows Defender instead, which also provides excellent protection and causes a lot less trouble than some third party AV programs. Windows Defender kicks in automatically when you remove your third party AV.

[Ralf]

Might be best to forward the message to him just in case MyCommerce didn’t notify him too, not really sure how they handle that. His data should have been added to our license database though, so getting his key should just work. Let mey know if not.

[Author]

Posts