Forum Replies Created
-
Posts
-
My reply above still applies. Didn’t have a chance to check the Game Pass version yet, but if it can’t be hooked, it might have been recompiled as UWP (Windows Store) app. UWP apps run in a sandbox that “protects” them against hooking.
There is a sort of expected crash when on first launch vorpX changes the DirectX setting from DX12 to DX11. Worked for me afterwards, but maybe for you guys it crashed before the setting had been saved. Just a guess, but that would indeed send you in a loop where the game crashes on every launch until it is set to DX11 manually. I’ll check whether I can handle this first time situation more gracefully, shouldn’t be too hard.
@ Kaaliba : I‘ll check that. Unsupported or not, switching to the Oculus settings and back should always work. Not sure currently what might have changed, but I‘ll take a closer look before the next update.
@ all : Thanks! And have a fun weekend.
Nothing specifially, but this is a good opportunity to repeat the mantra that startup issues of any kind with a fairly high probability are hooking conflicts with other programs that also hook into a game. The hottest candidate, especially if the issue starts to occur directly after an update, would be some invasive third party antivirus program, but that‘s not the only one.
More detailed info on the matter in the trouble shooting guide on top of this sub-forum (or alternatively in the vorpX help).
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).
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.
Just briefly checked the game again, should work now. So nothing I can recommend besides resetting both the game’s graphics settings and the vorpX profile to default (you can to the latter in the config app). Also make sure to check the messages vorpX displays on start in the headset and the top left corner of the game window.
Just checked the Epic Store version of the game with a Quest 1. Worked here except for the first launch where vorpX adjusted some game settings. Definitely has to be DX11, vorpX should take care of that automatically though. If you happen to have disabled automatic settings, please re-enable that. vorpX often adjusts settings that are required for games to run as they are supposed to.
One thing I noticed is that the Epic Store apparently has some new EpicWebHelper.exe that vorpX tries to hook. Makes sense to exclude that. I’ll add it to the exclusion list for the next vorpX release, for the time being you can do that manually in the config app under ‘Excluded Programs’. Just click ‘Add Process’ while the Epic Store is open and then select ‘EpicWebHelper.exe’. If it worked, you’ll see an according entry in the exclude list. Afterwards close the Epic Store and restart vorpX. Make sure the Epic Store really exits and not just minimizes as it does per default. If in doubt, restart Windows.
If afterwards you still encounter this issue, it’s time to consider some other hooking conflict. If you happen to use any other antivirus than Windows Defender, do yourself a favor and get rid of it. That can’t be said often enough. There is no need for invasive third party AV on Windows 10.
If that also isn’t the issue, there might be some conflict with some other tool you might have running. The trouble shooting guide on top of this sub-forum has more details on that.
@ sergeant82nd:
Provided your issue is the same Windows Mixed Reality related one that I experience here, you should be able to work around it by launching the game without the Mixed Reality Portal open. It will launch when vorpX initializes the headset.
Since the issue also occurs without vorpX running, I’m not sure whether another solution will be possible at all, but either way launching the game without the WMR Portal being open should do the trick.
@ sergeant82nd : What headset do you have? The issue I can replicate here only occurs with WMR headsets. As soon as the WMR portal is running, the game has difficulties to get into foreground for some reason. This happens even without vorpX running. No quick fix for that unfortunately, requires further investigation. With other headsets AC:Odyssey and AC:Valhalla hook normally here.
@ steph12 : There still is the issue with vorpX losing access to the depth information occasionally. There was so much other stuff in this release that I didn’t have enough time to dive further into this very game specific issue. It’s still on the list though. There is a user profile in the cloud, judging from its description it has the very same issue though.
Origins seems still to work as far as I can tell.
I’ll take a closer look tomorrow and if I can find a fast solution, will upload a hotfix. Mind the ‘if’ though, can’t say anything definitive yet.
@ dborosov: Did you get my mail earlier today? Following the procedure in the mail will allow you to check whether your issue is related to the update or not. Considering that forlaunchcast also wasn’t able to reproduce it, I suspect it isn’t. The only way to know for sure however is you checking it.
Just checked the game, there seems to be some issue with getting it into foreground, which would also explain why you can’t open the vorpX menu. Same thing for AC:Odyssey (which definitely is supposed to work).
I have a hunch, but am not 100% sure, have to take a closer look at that. Not today though. It’s almost midnight over here, time to call it a day.
Assuming ACV means Assassin’s Creed Valhalle, there is no official profile for game currently since 3D doesn’t work 100% reliable., so I can’t really say much.
Try to remove the user profile that you used and re-import it from the cloud. That way its settings would change back to the defaults the profile author had dialed in.
There is an “emergency” hotkey that let’s you deal with such glitches by temporarily disabling DirectVR. ALT+B per default, can be changed in the config app.
BTW: I’ll definitely check Dishonored in regard to the weapon hide feature soon. If you plan a full playthrough, it might be worth waiting a few weeks.