-
Search Results
-
In reply to: Arma 3 settings
If that is the case, something as wrong. Like all VR apps vorpX creates intermediate frames when the framerate is below 90fps to tackle that. That cannot work with an external tracking solution though since for creating these artificial frames head tracking data is used.
Please try a factory reset in the config app and do not tweak anything manually except FOV which currently is ~10° too high. If you have changed the mouse sensitivity in the game, you will have to adjust the vorpX head tracking sensitivity accordingly. Alternatively reset the game’s mouse sensitivity to its default value, then you don’t have to do that extra step.
With everything at default, vorpX as well the game’s mouse settings, there is no such issue. Just double checked that for you yesterday before replying to your Reddit post.
In reply to: Arma 3 settings
Nope, I tried native tracking too. Same thing. Reinstalled VorpX. downgraded drivers. Went to the lowest possible resolution, still get it. Tried safest, safer, fast. All the same. All arma settings low as they will go (well some like shadows kept on high, otherwise arma moves them from GPU to CPU).
In reply to: vorpX 18.3.2 Available Now
The no transform and stereo separation options are mostly useful for sky/sun/clouds or 2D effects that are rendered at wrong depth. You typically either don’t want to have these any 3D at all since they are supposed to be at a very large distance or maybe just a little bit (clouds). You’ll notice when that is necessary for a game right away. Most of the time it isn’t anymore though since vorpX can handle that automatically these days in many cases, depending on the base profile you use. The newer the better in this regard.
Texture replacement can be useful to handle heavily broken reflections, like sky/cloud handling it’s often unnecessary these days though. Also not fully implemented for DX11. In DX11 you can only set a texture to nothing currently.
Broken shadows should be marked as (shadow/user). That allows users to decide whether they want to live with slight artifacts with nearby shadows (‘No S3D’) or turn them off.
For HUD/menu shaders you should usually use the default method, the other ones rarely work as expected.
The rest of the shader options requires some solid understanding of 3D rendering and are rarely useful anyway. Just ignore them. Most importantly please never use the “Test” option for an actual profile. It’s purely meant for internal testing, what it does may change at any time. Will be removed from the public build with the next version.
In reply to: Arma 3 settings
I have. It works great. Head tracking works in vorpx, so Opentrack isn’t required any more. However, I like opentrack better because its got perfect 1:1 tracking, while the vorpx is still mouse based, and takes some tweaking, never quite feels the same as opentrack.
DirectVR only uses 4:3 ratios, and the FOV isn’t quite perfect. Mentioned it on reddit, and Ralf noticed it’s off too. The value is calculated for the headset, which should be perfect, but Arma uses some zoom. Its pretty close on stock DirectVR settings, and will get tweaked in the next release (from talking to Ralf on Reddit). Helicopters use a slightly more zoomed FOV from on foot, so that takes even more tweaking. I highly recommend mapping analog zoom to a slider/rotary. I use the friction control on the warthog, its perfect. Lets you easily tweak it realtime, just swing your head left/right until things stop swimming and look normal.
There’s always issues with FPS. I get a strange double image when moving, like every other frame is one behind. Locking ASW 45fps makes it very obvious. You can still play, but its annoying. When i (rarely) get the FPS up to 90, it goes away. Since the best you can usually do is somewhere between 45-90, its not ideal. Someone mentioned judder issues w/ 18.0.3 on the newest nvidia drivers, I dropped down to 398.36 driver and things feel smoother.
For maximum tweaking, create these custom rez:
1080×1200 (oculus native)
1296×1440 (1.2x)
1512×1680 (1.4x)Then you’ll have to do repeated restarts to tweak up the FOV, but a zoom control lets you know which direction to go at least. Those are 9:10 aspect ratio. Start at 96deg vertical, and work down from there.
If you use opentrack, don’t disable headtracking in vorpX, just set the sensitivity to 0, and turn off roll/translation. That way you can still look around in edgepeak mode.
Is it possible will Nvidia Optimus get ever app support/troubleshoot?
Hello, my laptop uses Nvidia Optimus technology, I believe that’s the issue why I cannot either attach to the game, or I attach but my headset is blank, or the special case BigScreen (is itself VR) can attach on dedicated geforce in contrast to other games (but cannot go on intel integrated saying it must be on the same GPU as geforce headset=dedicated), while other games cannot attach on anything else except of integrated but well then wont get output to headset geforce dedicated.
Is there any older version which would work for me without Optimus you could send me?, or should I buy different laptop? Nvidia optimus is almost the standard nowadays. Thank you.
[…]
In reply to: Call of Cthulhu – G3D
I can make it into the game, but can’t see anything when it starts. Just crazy smears of screen across my eyes. Nothing coherent. Just the menu’s are visible.
I’ll check whether something has changed that caused this, but no promises.
Windows 7: vorpX will support Windows 7 as long as the headset runtimes support it.
At some point you should prepare for the jump to Windows 10 though, I’m pretty sure neither Oculus nor SteamVR will work forever on Windows 7. Not only is it almost 10 years old now, also the Oculus hardware survey currently shows <3% Windows 7 users. Windows 10 has quite a few advantages in regard to VR, which why the overwhelmingly large majority of VR system are on Windows 10 already.
I would like a rollback function aswell because I have a similar problem as the OP. Played Skyrim + ENB in the evening with 18.2 and the next day vorpx updated itself to 18.3 and now I only get a black screen.
I reseted vorpx to factory default.
Reseted Skyrims INI files.
Updated nvidia drivers.
Updated ENB’s dlls.Not even ENBoost without the graphics enhancements is working. Vorpx does hook (I have sound, can load saves etc) but I can’t see anything and the biggest problem is that my Skyrim is so maxed out on mods that without ENBoost TESV.exe goes over the 2.8GB memory limit instantly and just crashes.
And in terms of whether a rollback option is a support nightmare or not, one question: Will I lose Windows 7 support eventually because “we can’t support everything”?
The Oculus software tells me everytime that Windows 10 provides the best performance and Steam charts show that more and more people are using Windoes 10 instead of 7/8…….
In reply to: Getting error – oculus headset not found
The issue with some old games like this one is that vorpX has to apply some Windows version check workaround for the Oculus runtime to init. According to your logfile that failed apparently. Might be due to an update of the Oculus runtime.
I’ll check whether something can be done, but in general please do not expect any unsupported game to work at all. Whether it worked at some point or not doesn’t really matter.
One thing you could check is whether you run either vorpX or the game in some compatibilty mode. If that is the issue: please never run vorpX or a game you want to play with it in XP/98 or any other compatibilty mode. And I really mean NEVER. :)
In reply to: Getting error – oculus headset not found
The game that showed this issue in your logfile (Thief 3 – Deadly Shadows) is not supported by vorpX.
ok, thank you.
only one thing to conclude: I have already applied the dgvoodoo to the game, and in fact until a few days ago it worked perfectly without the error of “oculus not found”
In reply to: Getting error – oculus headset not found
Please create a trouble shoot data archive in the config app after trying a few games that bahave this way for you. Send the .zip file to support |at| vorpx com, I’d like to check whether your logfiles show anything unusual.
i’ve send it: thank you.
In reply to: Getting error – oculus headset not found
Please create a trouble shoot data archive in the config app after trying a few games that bahave this way for you. Send the .zip file to support |at| vorpx com, I’d like to check whether your logfiles show anything unusual.
Not sure if I’m hallucinating, but since the last update (I think), it seems like the 3D effect of dishonored 2 has been reduced quite a bit. You mentioned you made some changes which may have affected AC:Odyssey (which is still good), perhaps this is the same thing. Seems closer to flat than 3D, although there is still some little bit of 3D-ness. Played with all the settings to no avail.
But its very noticeable in Dishonored 2 now. Liked it much better the previous way.
Unless I’m hallucinating, in which case I liked my hallucinations better before.I played around with the brightness settings in the VorpX menu and the actual game menu. There is actually a brightness slider in the VorpX menu (press Delete and cycle through the pages). Raising or lowering any of these does not take away the glare. For some reason the glare occurs when you turn up the 3D slider/intensity.
I mean I just played the first game and turned up the 3D to whatever I wanted and I had no glare. Can any programmers on here edit the user made profile and correct this and reupload it to the cloud? Because nothing in the menu’s will fix this…
The glare makes it hard to see at times. This is a really awesome Star Wars game and it would be really nice if it was officially supported, with this problem ironed out.
In reply to: A little bit of development talk
