Forum Replies Created
-
Posts
-
The expert settings toggle just affects a handful of settings in the vorpX menu and the config app that can severely break stuff if used unwisely. They are definitely visible when you checked the box in the config app. If you want to be extra sure you can check whether after clicking ‘More 3D Settings’ with G3D enabled you have a settings named “Focal Offset”. That’s one of the extra settings.
As far as your actual issue is concerned: that’s fairly weird, with default settings head yaw/pitch is what should always work before anything else. Check these things:
- The game must let you look around with the mouse.
- On the head tracking page in the vorpX menu head tracking must be on and sensitivity must be > 0
- If you use a gamepad, for many games the ‘XBox Gamepad Override’ option must be on. Why? A lot of games can’t handle simultaneous mouse/gamepad input. If you want to play such games with your gamepad and mouse emulation head tracking, you need the override, which enabels a built-in gamepad > mouse/kb mapper.
That means that vorpX couldn’t initialize the VR headset, which is a fairly severe issue. Most likely something is messed up on your system.
You *might* be able to deal with that by selecting a different headset type in the vorpX config app.
If e.g. you are using a Quest and currently have selected SteamVR/OpenXR, try native Meta Link instead. Most headsets should work with SteamVR, Meta headsets work best with Meta Horizon Link.
—
Sidenote in case you happen to use OpenXR while SteamVR is set as your system’s OpenXR runtime: Valve knowingly violates the OpenXR spec by not providing a 32 bit version of their OpenXR implementation. So Valve’s OpenXR cannot work with older 32 bit games.
Confirmed, one of those fix-one-thing-break-something-else-changes… Until this gets addressed please start vorpX as administrator, which should resolve the issue.
Can’t replicate.
Please check *thoroughly* for conflicts with other programs on your PC that may also hook into games. That’s the most likely cause of issues like this.
You can find more details on the matter in the trouble shooting guide in the vorpX help (or alternatively pinned to the top of this sub-forum).
Can’t replicate.
Please check *thoroughly* for conflicts with other programs on your PC that may also hook into games. That’s the most likely cause of issues like this.
You can find more details on the matter in the trouble shooting guide in the vorpX help (or alternatively pinned to the top of this sub-forum).
Looks like after a recent change the installer under certain circumstances could hang indefinitely at the end for fresh installs. An updated installer without this glitch is now online.
No such problem here. Please be more specific about the issue you encounter. What exactly happens? Is an error message displayed? If so, what does it say?
The only recent issue with the EA app that I’m aware of, which was caused by an EA app update a while ago, has been resolved in the latest vorpX update 25.1.5.
Many games can‘t handle simultaneous mouse/gamepad input. Sounds like such a case.
If you want mouse based head tracking in affected games and still play them with your gamepad, you can use vorpX‘s built in configurable gamepad to mouse/kb mapper.
The X-Box Gamepad Override option has to be set to On for that. If necessary you can then configure the mapping to your liking. In some lucky cases you might get away with a partial override of just the right stick and leave the rest of the gamepad native.
If you don‘t want/need mouse based head tracking in affected games, you can instead dial the head tracking sensitivity to 0.0 and turn off the gamepad override to use your gamepad natively.
Many games can‘t handle simultaneous mouse/gamepad input. Sounds like such a case.
If you want mouse based head tracking in affected games and still play them with your gamepad, you can use vorpX‘s built in configurable gamepad to mouse/kb mapper.
The X-Box Gamepad Override option has to be set to On for that. If necessary you can then configure the mapping to your liking. In some lucky cases you might get away with a partial override of just the right stick and leave the rest of the gamepad native.
If you don‘t want/need mouse based head tracking in affected games, you can instead dial the head tracking sensitivity to 0.0 and turn off the gamepad override to use your gamepad natively.
@ chtiblue
IIRC another Pimax user recommended to turn off fixed foveated rendering in the Pimax software regarding a similar issue. Doesn‘t really make sense performance wise with vorpX anyway since games always render at their own resolution. Foveated rendering only applies to vorpX’s second render step where the final image is sent to the headset, which costs almost nothing compared to the actual game rendering.
Also make sure that the virtual monitor is actually active. It‘s not active when you just launch a game from your normal Windows desktop. You can activate it e.g. by launching the vorpX desktop viewer and putting on your headset.
@ 333hronos
Fixed obviously.
AFter going through the tutorial slides once you can always directly press E on your keyboard or A on your gamepad/motion controllers to enter the game.
Back to the original topic: while checking the OpenTrack stuff now I get borked or completely missing depth on various occasions since the profile tweak from earlier today. I’ll have to revert that.
Please send me the config files and savegame I requested above so that I can check whether I can resolve your problem without breaking things for me (and others). I’m willing to spend a little bit more time on trying that, but if in doubt it will be mirrors off.
You can’t be sensitive enough to notice a microsecond (1 millionth of a second). The only option is that there may be unknown circumstances that make the check take (a lot) longer than it should on your system.
As said above this will be moved to an extra thread just in case. Just not right away. Thanks for your understanding.
There is a periodic OpenTrack activity check every second, shouldn’t really cause a noticable hiccup though.
Barely measurable on my rig, i.e. ~1 microsecond. Except for the very first time in case the evaluation yields TrackIR is available and thus gets initialized. Once that is done, further checks again take ~1 microsecond.
I put moving the check to an independent thread on the nice-to-have list, just in case there may be circumstances that can make it take longer than usual. Don’t expect that to happen anytime soon though. While easy to implement, this would have to be thoroughly tested with a good portion of TrackIR games.
I made one more tweak to the profile, which may or may not help. You should receive a profile database update next time you launch vorpX. If not, check whether you maybe disabled automatic profile updates in the config app.
If your issue still occurs after getting the profile database update and you want me to take yet another look at this, I need some files that allow me to reproduce your problem. Send an e-mail with the following files from your [Documents]\My Games\Farming Simulator 2025 folder to support at vorpx dot com.
- game.xml
- gameSettings.xml
- a savegame that shows the issue immediately after loading it.