Forum Replies Created
-
Posts
-
There should be a hint regarding adding custom resolutions directly below the option in the vorpX menu when you select an unavailable one… Honestly guys, sometimes it’s a bit disheartening to see how many people apparently don’t even read valuable hints that are shown directly within the app in the most obvious way imaginable at exactly the right place and time.
The post below (or the according section in the vorpX help) has a list of useful resolutions to add. A bit of a chore to add them to your graphics driver, but once you have added them, vorpX’s DirectVR auto resolution feature can choose the higher ones too.
They just made some minor changes, it’s not really a different headset.
The original model works fine for vorpX, but if you can wait for a few more weeks, it might be a good idea to do that and then order directly from HP to increase the chance that you really get the newer revision.
Seems to be a Vive Pro utility (provided Google is right). vorpX is not supposed to hook into it. Please exclude it either from the trouble shoot options that appear in the ‘Attaching To…’ dialog after a minute or directly in the config app (‘Excluded Programs’).
I’ll add it to the default excluded programs list for the next vorpX version.
vorpX displays this message when unexpected DLLs are found in the game folder. The full path to the DLL in question is shown in the message. You can simply browse to this path with Windows Exploerer and then rename/delete the DLL to see whether it causes an issue or not.
Please reset all game graphics options to default and then make sure to follow the hint displayed by vorpX in the top/left corner of the game window about running the game with common 16:9 resolutions. That should normally fix the issue.
If you haven’t done so already, please first try the trouble shooting options that appear in the ‘Attaching to…’ dialog after a mimote or so. Installing a hook helper can often resolve hooking issues without having to get to the bottom of the matter.
If that does not help, please check for potential hooking conflicts with other programs on your PC. That’s usually the reason for hooking problems. The trouble shooting guide on top of this sub-forum has more detailed information on the matter.
Depends on the game. In Titanfall 2 you can do that in the vorpX menu on the DirectVR page. Whenever that is the case for a game vorpX displays an according message in the top/left corner of the game window as well as in the headset.
Generelly useful hint: always pay attention to any messages vorpX may display in the headset and/or in the game window on your desktop. Saves a lot of trial and error.
No problem here with either game, latest versions, updated today.
If you haven’t done so already, please first try the trouble shooting options that appear in the ‘Attaching to…’ dialog after a mimote or so. Installing a hook helper can often resolve hooking issues without having to get to the bottom of the matter.
If that does not help, please check for potential hooking conflicts with other programs on your PC. That’s usually the reason for hooking problems. The trouble shooting guide on top of this sub-forum has more detailed information on the matter.
That looks weird for sure. vorpX just uses the data it receives via TrackIR, so I don’t really know what what to recommend here instead of resetting everything to default.
In regard to the FOV changes, please check whether maybe your ARMA settings are write protected or vorpX can’t access them for some other reason. Under normal circumstances it adjusts the FOV settings for any Arma III profile in [Documents]\Arma 3.
Apparently Valve recently made some changes to their anticheat system. You will have to run CS:GO without VAC. IIRC there is a launch command line parameter for that, which you can enter in the game’s Steam properties dialog: -insecure .
BTW: Please post technical support questions in the according sub forum. Future support questions will be moved without further notice. Thanks a lot in advance for helping to keep the forum better usable for others as well as yourself!
vorpX upscales the image to the final headset res before sending it to the headset, that’s what I meant above, but that aside the higher the game resolution, the crisper the image. You have to find a decent balance between performance and image sharpness though. Doesn’t make sense to crank up the resolution beyond a point where the framerate isn’t suitable for VR anymore.
Considering that in case of F1 2020 vorpX adds bars above and below the image to get the FOV right 1440p should look fairly good under normal circumstances, but if for you that doesn’t look good enough, you might want to experiment with higher resolutions.
You might also want reset all game graphics setting to default, maybe you dialed in some settings that cause a weird resolution issue. Unlikely, but just in case.
Has to be somehow connected to the video compression. If you run a game at 1440p, vorpX sends a roughly 2400p image to the Oculus app in the end after processing the 1440p output from the game. Everything beyond that is out of its realm.
Raising the ‘Clarity’ setting in vorpX will apply a bit more sharpening, maybe that helps.
Quest doesn’t send the image directly to the headset, instead the Oculus software encodes a video stream on the PC that is then sent over to the headset and decoded there. Don’t ask me why, if I had to guess I’d say say wanted to save a few cents for the HDMI output. You can change the encoding resolution in the Oculus app, but even with a higher encoding res there will be some image degradation, also the max posiible res is obviously limited by your connection. Ideally use an USB 3 port with a good USB 3 cable.
Due to its low price tag Quest is great for cheking whether VR is fun enough for you to do it more often, but if you later decide it is and what you want to do most is PCVR, better get a dedicated PCVR headset.
I only need a Pimax headset to make sure things are working, no need for anything elese than what I have here. Gifts always come with expectations. The main issue with Pimax in conjunction with vorpX is the ‘brainwarp’ software layer. Unfortunately no way to turn that stuff off entirely.
Wasn’t entirely clear above, sorry. What I should have said is that the second number in the vorpX FPS counter should ideally always be the refresh rate of your headset. If you select 72 in PiTool, it should be 72, if you select 90 in PiTool, it should be 90 and so on. vorpX works best when it can do all interpolation from the game framerate to the headset refresh rate by itself.
Unfortunately that’s where ‘brainwarp’ gets in the way. Pimax headsets are much less liekely to stay solid in that respect than other headsets and thus are more sensitive to judder with vorpX than other headsets. They just can’t deal well with an application that wants to do the game to headset framerate conversion on its own, pretty much like WMR headsets behaved over SteamVR before Microsoft came up with their totally awesome WMR OpenXR runtime.