Forum Replies Created
-
Posts
-
Found a workaround: my first suspicion yesterday was that the Steam overlay might be the culprit. To avoid potential overlay conflicts vorpX tries to block it, but in this case it’s already loaded when vorpX attaches, too late for blocking. Disabling it didn’t help either unfortunately. What I didn’t try yesterday is simply renaming the overlay DLL so the game can’t load it anymore. Surprise, surprise, that actually works.
Caveat: Steam replaces missing files on start, so the DLL has to be renamed after each Steam launch. I’ll see whether I can come up with something better, but for now this will do:
- Launch Steam.
- Navigate to your Steam folder in Windows Explorer.
- Rename GameOverlayRenderer64.dll to _GameOverlayRenderer64.dll. You can also just delete it, Steam replaces it anyway on next launch.
- Launch the game.
If you only see a file named GameOverlayRenderer64 in your Steam folder without the .dll extension, use that. In that case your Windows Explorer is probably configured to not show file extensions.
No problem, but please NEVER upload profiles changed this way to the cloud. I will remove it from the database. No problem if you do that on your PC, but please don’t upload such a profile to the cloud.
This is really important. THANKS!
I still have overrides for official profiles on the nice-to-have-list, but that’s a more complex matter than one might think. A lot of stuff has to be considered in regard to updates, restoring etc. Hopefully there will be some time for this in the not too distant future.
For now the official way to handle something like this would be to rename the game’s .exe (or better create a copy with a different name) and then create a custom profile for this renamed .exe. Not ideal, but unless a game ceases to work with a renamed .exe, it’s a viable solution.
Step-by-step:
1. Make a copy of the game’s .exe (e.g. game.exe > my_game.exe)
2. Create a copy of the original profile in the config app
3. Assign my_game.exe to your newly created custom profile
4. Make the changes with your custom profile
5. Upload the profile (don’t forget to mention the renaming in the description).This is a hotfix for the showstopper issue mentioned above. No other changes. The next regular update is being worked on in parallel and will be released before Christmas. Probably without an RDR2 FOV hack, but what I can say already is that shader tracking (and with it HUD scaling) for D3D12 (RDR2) will be included.
I bought the Steam version today to check this and don’t have good news unfortunately. vorpX hooks into the game, but initializing D3D12 fails with the Steam version. There is no easy solution for this issue, the error occurs in a call to the D3D12 API, so there isn’t really anything to fix in vorpX itself.
I have some vague ideas regarding a potential cause, and maybe there is a way to work around the issue, but that’s all just theory for now. In the worst case fixing this may require pretty huge changes. I’ll invest an extra day today tomorrow, but don’t expect a fix in the next vorpX release, probably won’t happen until next year.
For now all I can recommend is using the Rockstar Launcher version. Not much reason to use Steam for RDR2 anyway since it requires the Rockstar launcher on top.
You can try switching to “SteamVR” in the vorpX config app. Works also with Oculus headsets. With some luck that may help, but I wouldn’t count on it. If no program that is supposed to show the desktop in VR works at all, it sounds more like there is some issue with desktop capture in general on your machine.
vorpX works perfectly fine with Oculus headsets. There is no need to disable Oculus Home, you should be bale to launch games with vorpX normally from your Windows desktop.
One thing you will have to do to is allowing ‘Unknown Sources’ in Oculus Home if you haven’t done that already. You can do that under Settings > General in the Oculus app.
Apart from that please make sure that your have selected Oculus as your headset type in the vorpX config app. Just in case.
And last but not least: Your AV program is probably the worst known offender in regard to vorpX and on top of that rather difficult to disable. You will at least have to disable its so called “advanced threat protection” (which is the opposite of “advanced” and flatout blocks hooking into other programs) in addition to disabling the scanner.
19/12/09
vorpX 19.3.1.3 has been released.This is another hotfix with a better solution for the Windows Defender/Steam ‘Application load error 3:0000065464’ issue after a recent Defender update. Instead of switching to the less reliable alternative hooking per default the original hooking method has been modified to work again without this issue.
Ironically disabling a fix for a rather similar Defender/Steam issue from about two years ago made it work again in the end. Big thanks to the certified genius(es) at Microsoft who ruined my entire weekend.
The Dragon Age/Dragon Age 2 issue will be resolved in the next regular vorpX update. I don’t have an exact date yet, but definitely before Christmas.
Just to avoid potential confusion: before that there will probably one more hotfix for the current release branch tomorrow. this hotfix will not contain the required changes yet. The next regular update will come after that.
Glad that worked. Not much of a weekend for me anyway due to the Defender/Steam issue. There is a 50:50 chance that I will be able to resolve it without having to switch to the less reliable hooking method per default. No promises yet, I’ll know for sure in a few hours after some more testing. Fingers crossed.
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.