Forum Replies Created
-
Posts
-
vorpX runs with any headset that supports SteamVR (true for pretty much all consumer headsets) or the Oculus runtime, so as far as vorpX is concerned directly there isn’t really much to say when comparing the various available options.
Windows Mixed Reality and Pimax headsets both introduce an extra software layer between their hardware and SteamVR, making them a bit less convenient to use, but that’s a general thing, not something vorpX specific.
Sounds as if you run vorpX in some sort of compatibility mode. Please check that and disable any potential compatibility mode setting. If for example you set vorpX to run in Windows XP compatibility mode, the updater (correctly) assumes you have Windows XP.
No compatibility mode should ever be required for vorpX.
If you want to use an external gamepad remapper, you have to disable vorpX’s controller handling. Otherwise there will be a conflict between vorpX’s internal remapper and your external remapper.
Be aware though that disabling vorpX’s controller handling can cause issues with head tracking in games that don’t allow mouse and gamepad to be used together. The gamepad override exists to deal with this.
If the gemepad override is activated in a profile, it’s best to leave it activated and use vorpX’s internal remapper.
I forgot to update the profile for the last release, sorry. There is indeed some weird z-ordering issue that must have been introduced by a game update. A change in vorpX’s code can be ruled out as a cause, even the ages old vorpX build that was used to create the profile looks the same.
Unfortunately I couldn’t solve the issue despite spending two full days on it, so G3D will have to be disabled for the time being. Until that happens please don’t play the game.
Switching to Z3D in the vorpX menu is not enough in this case, making the matter even more strange. G3D has to be completetely disabled in the the system portion of the profile.
vorpX changes MPC-HC’s video output method when you launch it for the first time with vorpX. Maybe the method it selects is incompatible with Discord.
You can restore the prior state in the vorpX config app (‘Restore Game Settings’).
If you still encounter your issue after doing that, it can’t be related to vorpX. vorpX does nothing while it’s not runing.
Well, then you’re out of luck. Just kidding.
If you didn’t keep the original key e-mail or need a new key because your hardware changed, simply resend your request code and you’ll get a new key.
Since it may depend on a PCs configuration whether one or the other method works better, baking the hooking method into a profile is usually not a good idea, except for rare cases where that already can be done (just not by users).
No profile that doesn’t already have alternative hooking baked in does generally not work with normal hooking. If some don’t for you, that’s related to your individual setup.
Still sounds like a good idea to make it a per game setting outside of profiles. A few other things that can differ from user to user are already stored that way. I’ll think about it.
Since in contrast to native apps the SteamVR supersampling isn’t the most relevant aspect in regard to image quality (instead, like you correctly say, the game resolution does what supersamling does for native apps), vorpX does some sanity checks when creating the final render textures, so overly large headset render textures that affect performance negatively are unlikely to occur.
TLDR: If the Win 10 1903 issue is related to wrong handling of supersampling, vorpX probably won’t be affected.
If you forced antialiasing in your graphics driver, disable that. For some reason driver forced antialiasing makes Bioshock run extremely slow with vorpX. Can’t remember currently if that also applies to the ingame AA. If in doubt, disable that too.
Following the tutorial to the letter should get you going.
To me it looks like the guy in the video uses SteamVR in direct mode not in desktop mode, but I might be mistaken. If that’s the case there should be no need to switch the display. Can’t really say much more though, I don’t have a PSVR to try.
I never tried a PSVR, but I’m pretty sure there is a better way to do this than the “Generic Headset” mode. The tutorial below uses vorpX in SteamVR mode and Trinus for streaming to the headset. Despite being easier to handle such a setup probably also can provide head tracking.
Dishonored 2 is Z3D only at this point. Technically Geometry 3D is not out of the question in this case, but would require additional programming just for this one game, which is always a bit hard to justify unless a game is really popular.
If you want to try games that show vorpX’s full potential, I can recommend the Good FullVR games for Beginners list as a perfect start point.
I tried when DirectVR was introduced, but no method the scanner supports to find the right values yielded a result unfortunately. There have been a few updates to the scanner since then, so maybe I should give it another shot.
As always no promises though, the memory scanning process doesn’t work for every game.
You don’t need to run vorpX as admin unless you also run the game as admin. It’s generally better to only run vorpX as admin if necessary.
In case of injecton issues please first and foremost check for programs on your PC that may interfere by also hooking into games. In almost all cases that’s the cause of injection issues.
You can find more detailed information about potential candidates in the trouble shooting guide.
19/06/12
vorpX 19.2.1 has been released.This is a maintenance release, mostly focusing on fixing a few issues that have been identified since 19.2.0. Also some minor improvements have been added, most notably automatic audio switching for Rift S.
New/Changed:
- Rift S audio switching support.
- D3D9 improvements, may help in unsupported DX9 games that use state blocks.
- D3D11 compatibility improvements
- The actual value is shown for settings that are set to ‘Device Default’
- vorpX shortcuts launch programs without hooking if the watcher is disabled.
- To deal with Pimax’s new ‘Compatible With Vive Only Games’ setting a warning is shown if the headset is detected as Vive while Pimax software is running.
- No more ~5 seconds hooking delay after a clean game exit. Now only delayed if a game hangs.
Bugfixes:
- D3D9 Z3D pipeline init was incomplete (vorpX 18.1.5 regression).
- D3D9 Z3D HUD scaling was not working anymore in some games despite the feature being available.
- Z3D did not work anymore in various games when loading pre 19.1.0 profiles.
- Fixed a rare crash condition that could occur occasionally with multithreaded games during init.
- Game settings changed by DirectVR weren’t always saved for Metro: Exodus
Game Profile Changes/Fixes:
- The Long Dark: Geometry 3D was broken after game update, 3D HUD added
- Tomb Raider Anniversary: fixed sea water glitch
- Mass Effect 1-3: default to immersive screen mode now instead of cinema
- Z3D base paramaters adjusted for various profiles