Forum Replies Created
-
Posts
-
1) Skyrim does not need any custom resolutions. You can set the resolution as high as you want on the DirectVR page of the vorpX menu by choosing a preferred quality. Go for something like 1440p or above for good image quality. Keep an eye on performance though. Higher resolutions cost performance. It’s all about finding the right balance here.
2) If you encounter graphical glitches, try another 3D mode. If currentlly you have sleceted Geometry 3D , try Z3D or vice versa. Make sure to restart the game afterwards, just in case. Z3D doesn’t look as natural, but is a lot faster.
3) Memory scanner: See my reply in your other thread.
4) Do not use supersampling in SteamVR with vorpX! That has (almost) no effect on image quality, but may cost performance. The right way to enhance image quality in vorpX is raising a game’s resolution like you would do when you play a game on your monitor. If vorpX can handle it, you can do that on the DirectVR page of the vorpX menu. Whenever that is case, you see an according message in the top left corner of the game window. If vorpX cannot handle it, games usually allow to set the resolution in their options.
I sent you another installer which uses a newer DotNet version. It should not be affected by your broken DotNet 3.5 install.
Would be great if you could provide a bit more detailed information about your issue. Difficult to say anything useful otherwise.
If you carefully follow each step in the custom resolution instructions, there sholdn’t much that can go wrong. For nVidia: double check especially the steps 2. and 4. Without doing these you won’t be able to add resolutions. For AMD: keep in mind that the AMD driver does allow to add resolutions higher than your monitor allows.
The scan may sometimes fail although it “thinks” it succeeded. That would typically yield the result you saw. If the scan does not work for you in this game, stick to mouse based tracking. Scanning the whole memory of a game for one particular value is a rather delicate matter and may not always be 100% reliable. Hence the message in that regard that is shown during each scan.
No problem here with both the regular and alternative hooking method. The only reason why vorpX would need admin rights for hooking a game is the game running as admin itself. That would be the case if for example you are Steam running as admin.
I would gladly take a look at the issue if someone could provide a savegame from a location where the issue occurs, unfortunately noone did so far. Please send it to support |at| vorpx com.
Before you do that try to reset the profile to default and check whether the issue still occurs with default vorpX settings.
Once the DirectVR scan succeeds you should be able to use the gamepad natively. If you made any changes to the input settings in the vorpX menu, please reset the profile to default or redownload it from the coud. With default settings it should work fine, just checked it for you. Also make sure the gamepad is enabled in the game options.
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.