Forum Replies Created
-
Posts
-
Don’t want to sound like a broken record, but if you use anything else than Windows Defender, please try to REMOVE your AV software for testing purposes. Some more invasive AV programs can’t really be fully disabled unless you remove them. There is no risk involved in removing invasive third party AV on Windows 10, which has a built in AV solution that is more than good enough for several years now.
Apart from that: two last things you might want to try are a full vorpX factory reset and if that doesn’t help resetting your PC to the state from before your issue started to occur.
I’m out of ideas otherwise, sorry. Both games work perfectly fine here, FC3 always did, FC4 also does 100% reliably with yesterday’s modified profile that addresses the occasional black screen issue. Checked on two different machines.
It should just work normally. The game has an issue with losing input focus occasionally though when run windowed. Clicking inside the game window should help with that if it happens.
Try to make sure that games safely run with at least half your headset’s refresh rate, e.g. by reducing their graphics details. You can check the framerate with ALT+F. The first value shown is the game frame rate, the second value is the headset frame rate.
WoW currentyl is supported in DX11 only. Should be set automatically when you launch the game with vorpX.
For better image quality you have to raise the game’s resolution not the Oculus resolution. For FullVR games a 4:3 resolution like 1920×1440 is a good choice. If your PC does not support this resolution, check the Custom Resolution section in the vorpX help. It contains a step-by-step guide regarding adding custom resolutions.
FOV is handled by adjusting some values in the game’s ini files. If that fails, please check whether you maybe have forbidden apps to access your documents folder (e.g. in the Windows options). The game stores its .ini files below the documents folder.
Decoupling the camera from the walking direction is out of vorpX’s scope. That’s something that has to be supported by a game, one (rare) example would be Arma III with TrackIR tracking.
Try with vorpX in SteamVR mode, DX12 Steam games currently don’t work with native Oculus. There is some conflict between the DX12 Steam overlay and the Oculus runtime that leads to a crash.
Not every game has a DirectVR button. The button is only available/necessary in games where vorpX scans the game’s memory for head rotation/position or FOV memory addresses.
In Titanfall 2 the memory scanner is not used, instead DirectVR adjusts the FOV via editing the game’s .ini file, while tracking is done via mouse emulation, hence there is no memory scan button.
Please follow the instructions in the top left corner of the game window regarding enabling TrackIR in the game’s camera options. F1 2019/20 now use the new integrated TrackIR support in vorpX.
The only way to override an official profile would be to rename the game .exe and then add the renamed .exe to the custom profile.
There is no need to to do that though. Please reset the profile to default in the vorpX config app and then check the instructions in the top/left corner of the game window. The profile now utilizes the new integrated TrackIR support, and works great in FullVR mode.
Note that whenever this option is enabled per default, it is enabled on purpose for the reasons outlined above (at least in official profiles). It’s never enabled just for fun.
Unless this option happens to be enabled unnecessarily in the profile you are using (unlikely in case of an official profile), you will encounter issues with mouse based head tracking and gamepad input at the same time after disabling it. The purpose of the gamepad override option is to deal with games that do not support simultaneous mouse and gamepad input and usually is only enabled when that is the case in a game. Typical symptoms would be failing/stuttering gamepad input and/or head tracking after disabling the override.
There is definitely something getting in the way if you experience an issue like that. Both games should hook normally and I’m fairly confident that the ages old FC4 black screen glitch is also gone with the updated profile.
If you have some experience with 3D programs and want to do an environment yourself, shoot me a mail to support at vorpx com. You would have to follow some rules in regard to scaling and object placement, also the poly count has to be *really* low to keep the performance impact minimal, but I could provide you with guidelines in that regard.
The actual integration into vorpX would have to be done by me since the scenes are built programmatically from individual objects in a vorpX specific file format exported from 3ds max. At some point down the road I might create full scene export/import from 3ds max to vorpX. Wouldn’t be overly difficult, currently that doesn’t exist though.
If you come up with a cool scene, I’d be happy to do the integration work. You could even built it in Blender or whatever you prefer. Would have to be something original though, just copying the SteamVR theater is out of the question unfortunately, copyright and so on.
Short update: You can grab a slightly modified FC4 profile from the cloud that *might* work better in regard to the notorious black-screen-before-first-menu glitch. You can import it on the cloud profiles page of the config app, name: Far Cry 4 [vorpX].
Since the issue only occured every now and then for me anyway, I’m better a bit careful what I say, but as far as I can tell the modified one seems to work 100% reliably. Switching the game to windowed might still make sense if you encounter issues running it fullscreen.
There is no one-size-fits-all answer to that question. It all depends on the game. The best resolution is always the one that works with a high enough framerate to not feel uncomfortable for you.
General rule of thumb: For FullVR mode games ideally try to find a combination of game detail settings and resolution that safely works with half your headset refresh rate. Technically vorpX works with framerates below that on most headsets, but if you are prone to motion sickness, things may start to become uncomfortable beyond that point.
In cinema mode head tracking is off per default, in immersive screen mode it is not. Mouse based head tracking and native gamepad at the same time do not work in games that don’t allow gamepad and mouse input simultaneously. That’s pretty much the reason for the built-in gamepad to mouse/keyboard mapper.
To use your gamepad natively in a game that dislikes simultaneous mouse and gamepad input, you would either have to disable head tracking or alternatively configure vorpX to simulate a gamepad via head tracking instead of a mouse. Due to the heavy filtering games typically apply to gamepad input that’s fairly laggy though.