Forum Replies Created
-
Posts
-
Yes, please disable fluid sync on Oculus. As mentioned in your other post, please do not tweak too much, as tempting as that may be. Most options especially in the input and direct mode department are the right ones for your headset per default. They should only be touched under special circumstances.
If you already tweaked a lot, it might be best to do a factory reset in the config app.
Custom resolutions of any kind still work, but using the the recommended 4:3/5:4 resolutions is easier and also has some benefits in regard to async timewarp.
The higher the resolution, the better the image quality. But 1280×1024 is the perfect compromise between quality and performance on a normal gaming PC with recommended Oculus/Vive specs.
Compared to playing games on a monitor high FPS are a lot more important in VR, so that should be the primary concern when experimenting with different resolutions.
I would like to tell you something else, but a little test stroll here showed pretty much the same performance as always.
40-50fps in the grazelands around Whiterun, 30-60fps in Whiterun, 60-90 in the first tavern in Whiterun and 60-90 in the usual test dungeon (Bleak Falls Inner Sanctum). Everything with Geometry 3D on a CV1 at the new recommended resolution (1280×1024).
Direct Head Tracking shouldn’t be visible in Skyrim, please ignore for now if it doesn’t work.
Multi-threaded input didn’t do anything useful anymore since async timewarp was introduced, leaving the option visible was an oversight. For async timewarp it’s important to sample the head tracker at specific points in time. I’m surprised you found, with asnyc timewarp it usually caused judder.
Fluid Sync is mostly important on Vive. On Rift it can give a slightly better experience async timewarp experience, but in general just leave it off on Rift.
I would generally advise not to tweak too much although that might be tempting. The default options especially in regard to input and direct mode are the right ones for your headset.
That’s not possible with MPC/VLC. With vorpX and MPC/VLC you can watch 3D movies, but not 360° videos. Might be added in the future. It’s on the nice-to-have-list though without any specific date.
But there are a number of players that can do this: I used Whirligig (http://www.whirligig.xyz/) in the past and if I’m not mistaken it supports both Rift and Vive now.
Only the Vive support is beta, not vorpX in general anymore.
Talos Principle: seems to be broken (again) after a patch. Thanks for the heads up. I will look into it. It’s agreat game for VR, but it might just end up being taken from the compatible games list this time. Something similar happened three times already.
DXHR: Please try switching between DX9 and DX11. This is one of the DX11 test cases here. It *should* run with 45fps+ normally with G3D in DX11 with dips below that in some areas.. Maybe Dx9 works better for you though. Also make sure to try the default graphics quality settings and set the resolution to the recommended 1280×1024.
Just checked GTA5, HL2 and Portal to make sure not to say anything wrong. All three worked.
General advice: games not hooking at all are usually a sign of an injection conflict with some other program on your PC. Typical candidates are anti virus programs, any sort of GPU/CPU utility, ingame video recording/streaming programs and generally everything that can show notifications in games (like some chat programs for example).
The best way to trouble shoot this is to close/uninstall every background program that would not be there after a fresh Microsoft only Windows install.
It’s helpful because it enables async timewarp on the Vive. To be precise a combination of vorpX’s custom async timewarp with OpenVRs interleaved reprojection. On the Vive you pretty much only have the option to run games at 90fps or 45fps with nothing in between without vorpX’s FluidSync. Don’t be concerned about it showing 45fps.
If you are certain a game runs fast enough, you can disable FluidSync, which makes the render pipeline behave like with Oculus. But that makes most sense with rock steady 90fps.
Base performance should be pretty similar, but the Oculus runtime is a lot better in low frame rate situations.
BTW: New recommended resolution for Full VR is 1280×1024 now, no widescreen res anymore.
If I remember correctly you reported that earlier and I did some long time tests afterwards trying to replicate your issue, which ran through fine here. So unfortunatly there is no way to say what might cause this since it can’t be replicated.
Only advise I can give is rather general and I might have given it before: Try using a fresh Arma install and do not use any mods, which is the configuration used here. Mods generally cannot be supported, there are just too many of them.
Your best bet would probably be to configure the Steam controller as a standard XBox controller and then do any custom adjustments with vorpX’s gamepad emulation. That can be configured directly ingame in the vorpX menu. It also allows to adjust right stick Y sensitivity independently.
Edgepeek size/distance can be adjusted in the vorpX ingame menu if you enable expert settings in the config app.
The position can be recentered with [ALT][SPACE] (changable in the config app). To do this standing without the keyboard you would have to map that hotkey to your gamepad.
That search window only shows for games where the .ini files are stored in the game directory (mostly rather old games). In other cases it’s not as trivial as one would think to provide such a search window as settings may be stored in more than one place or the registry. But I’ll check where that might be possible.
Just in case: please make sure to not run the vorpX config app as admin, that may make it look in wrong places if you have different users on your PC. It’s also important to run games once before applying the Optimizer. Otherwise the settings files it is looking for may not exist.
The headset has to be in direct mode. vorpX shortcuts don’t work with most Steam games, just try starting through Steam.
The red screen sounds rather odd, never heard of that before, but maybe it’s an injection conflict with another program on your PC. Likely candidates are: virus scanners, any sort of GPU/CPU utility, video recording software, chat programs and generally anything that can show notifications in games or hooks games for any purpose.
Best way to trouble shoot this is to disable/uninstall absolutely everything that is running in the background and would not be there after a fresh Microsoft only Windows install.
If you can’t find anything, send the trouble shoot data and I will check whether you might have overlooked something.
You didn’t say what headset you are using, so just in case: DK2 owners with multiple runtimes installed sometimes can experience the symptoms you describe.
So in case you use a DK2 and are using a runtime switcher, please uninstall all beta runtimes that may still be present on your system, remove the runtime switcher and reboot your PC. Then let Oculus Home repair itself afterwards if it has something to complain.
If adjusting the FOV with the vorpX Game Optimizer fails for you, you can do it manually. There are a lot tutorials for that. For vorpX you need a horizontal FOV of 110-120.
http://hia3.com/tools/ArmA_3_wide-angle_FOV_calculator_online_by_Hi,A3.htm