Forum Replies Created
-
Posts
-
Sounds as if the DirectVR rotation might not get applied properly. For Source 2 games the scanner has to find multiple memory locations. Sometimes it might not find all of them, which would lead to a success message while in fact not everything is right.
For Half-Life 2 vorpX comes with pre-cached DirectVR values though, so if you are using the current Steam version of the game, there should be no need to run the scanner yourself. A factory reset in the config app restores the pre-cached values, so that’s worth a shot.
I don’t really have any other suggestions for Gone Home than the ones I gave you twice already, sorry. If for some reason DirectVR auto settings don’t work for you for a game, you can always:
- Either disable auto resolution in the vorpX menu (DirectVR page) and use vorpX the old fashioned way by following the three steps from the ‘1-2-3 Game Setup Guide’ in the help, essentially using the ‘ImageZoom’ option to compensate for missing FOV.
- Or alternatively switch the ‘Play Style’ option to ‘Immersive Screen Mode’, which doesn’t require a specific FOV.
Regarding my assessment of dellrifter’s Black Mesa fix please see my reply directly above yours. Whether there can be a solution on vorpX’s end, I can’t tell yet. If a game loads SteamVR (OpenVR) by itself, it causes a conflict with vorpX which does the same when operating in SteamVR mode. If by any chance you happen to own both a Vive and a Rift, switching vorpX to Oculus mode would also help.
Just in case you didn’t try that already: might make more sense to use antialiasing and a lower resolution instead. 4x MSAA with a more reasonable resolution will probably be faster and result in an image that looks just as good or even better.
You are the first one reporting such an issue since the Vive Pro has been released almost a year ago. Definitely not related to the Vive Pro, which is just another SteamVR headset for vorpX, but something unique to your individual setup/configuration.
Please try a full factory reset for vorpX (in the config app) as well as for your headset.
In regard to hooking issues please check for programs on your PC that may cause a conflict with vorpX by also hooking into games. First and foremost antivirus software, but also: any kind of GPU/CPU utility, game recording/streaming software, messengers and generally everything that can show notifications in games.
@ brown66: That sounds unusually low. Before thinking about a new graphics card please first try a fresh, unmodded install with default “medium” or “high” graphics settings. That should run quite well. Afterwards add back your mods one by one to identify those that reduce performance. Also make sure not to use any .ini tweaks that are known to cause a severe performance hit (e.g. a higher “ugridstoload” value).
Please make sure that the “Don’t optimize game settings” checkbox in the config app is UNCHECKED. Afterwards you can simply choose a better resolution quality on the DirectVR page of the vorpX ingame menu.
Although at this point that is pure speculation since I don’t have a Pimax here, I would assume that it’s mostly the larger FOV that is responsible for the performance hit. The larger the FOV, the more geometry has to be drawn, which obviously affects performance. Even more so in heavy games like the tested Kingdom Come Deliverance.
Pimax apparently is very much aware of that and thus (judging from the video) seems to provide three FOV settings with even the smallest one still being substantially better than the other current headsets. A pretty neat idea actually that should make things a lot easier for vorpX.
You don’t need a new key for reinstalling vorpX, your original key will work just fine. A new key is only required if you change hardware or reinstall Windows.
If even 1680p (which is already better than your headset’s native res) is not enough for you for some reason, you can disable the auto resolution feature on the DirectVR page of the vorpX menu and set an even higher resolution in the game’s ini file yourself, provided your PC can display it. Make sure to set a 4:3 res in that case, not widescreen, to avoid unnecessary rendering overhead.
You can select a resolution ranging from 1080p (slight undersampling) to 1680p (slight supersampling) on the DirectVR page of the vorpX menu.
Sounds like a corrupt installation, there should be an Oculus option in the headset selection box. Pleae try to reinstall vorpX.
That shouldn’t be an issue for years. Might still make sense to create a second user for testing purposes in case it’s some other profile related issue.
Apart from that: if you can run the config app, please create a trouble shoot data archive in the config app and send that to support |at| vorpx com.
Please uninstall MalwareBytes for testing purposes. Some more invasive AV programs make it very hard to fully disable them until they are completely removed.
Please first and foremost try without MalwareBytes. Sounds very much like a virus scanner problem.
You can reinstall without needing a new key. The one you got stays valid unless you reinstall Windows or change hardware in your PC.
You need to make a copy of a profile that has SBS input unlocked. The Rise of the Tomb Raider should work.
dellrifter (see the post above yours) apparently already did that, so check the cloud profiles first.
The ALT key is blocked intentionally as a safety measure to prevent collisions with vorpX hotkeys (which use the ALT key per default). You can disable this block on the input page of the the vorpX menu.
Caveat: the according option is only available in the vorpX menu if expert settings are enabled in the config app.