Forum Replies Created
-
Posts
-
yeah, I tried messing with mouse input settings, no luck. But turnning off headtracking makes it normal. That’s when I discovered headtracking wasn’t working in general.
Wondered if emulation is getting confused with some game controls update, even though I never have a gamepad plugged in. Game used to work fine until earlier this year. Let me know if you have the same trouble. Thanks.
Cool. Might be getting this soon then after all.
Would you say performance is near fallout 4? Z3D also working right?
When you test Battlefield 1, can you recheck the headtracking?
I think a game update broke it, causing severe jumpy mouse when enabled. And when you turn it off, not even cinema/edgepeek tracking works.
I too have high hopes for Red Dead 2 PC. Been waiting for years thinking surely this time we’d get it. This one looks like it would be great for vorpX too, with first person and all. Imagine :)
Mine was crashing the same.
By restoring pre-vorpX settings, disabling vorpX optimization, and creating a fresh cfg, I was able to load into the game.
rename/delete user.cfg in both:
C/Users/yourname/Appdata/locale/4Agames/Metro 2033/manynumbers/User.cfg
and Steam\SteamApps\common\Metro 2033 Redux\user.cfgThis will create a new cfg upon launch.
Might just be a bug with vorpX optimizer that a game update broke.
Now I need to figure out why all my keybinds are unassigned.
Looks like it runs on Unreal 4. So profiles to test first could be:
Conan Exiles
Hellblade
VampyrTry both G3D and Z-normal.
Let us know if it works with 3D. Might pick this one up on a sale.
I just messed around in Return to Castle Wolfenstein a bit. DirectVR scan generally works well for FOV and rotation. Sometimes though, headtracking locks up. It also tends to teleport your view from floor to ceiling whenever you look down with mouse controls.
In case this bothers you too, I’ve uploaded a profile with DirectVR disabled to solve that. It has letterbox image zoom adjustments for FOV correction (you can see edges of the screen), but still looks pretty good in my Pimax. Zoom out a few more notches to look better on rift.
The cutscene 3D seems broken, and possibly the scopes and binoculars. But general gameplay is good. If skybox is too distracting, turn off “Draw Portal Skies” in game options.
Yeah, that sounds similar to what I saw when testing the DOOM demo for G3D. Caused just enough eye strain to make unplayable.
Thanks for testing that out for me. Would be cool to one day play the new Wolfenstein games in 3D glory.
I restarted from the beginning, and yes, the hands look good now. Holding them up reveals no halo. Nice.
I’ve loaded a couple saves and found the hands themselves now look as they should in each eye, it’s just the watch and weapons that still halo.
I’ve discovered you can now make one eye halo-free using the main eye setting, with camera height at zero. So this helps to minimize it some.
Hopefully a full fix wouldn’t have to be on a per item basis. Neat that the hands are working though.
What? The New Order is late OpenGL (unsupported by vorpX). Are you sure that profile manages actual G3D stereoscopic?
If so I’ll be purchasing the game soon.
I’ve always thought black background for edgepeek would make sense, as it is mostly used for watching cinematics.
Maybe to avoid additional settings clutter, just have the current selected cinema background apply across all modes.
Look for a “Lock headroll” type setting in the main vorpX config. It might also be in the delete key menu.
While you could adjust zoom/curve settings of cinema mode match or go beyond that of immersive screen (including change the ambience gray to black), I’d use immersive for it’s edgepeek ability – making cutscenes/dialogues more comfortable to watch.
That said, I personally use the letterbox Fullvr mode to lock-in head tracking, which also has edgepeek. I do have a camera mod that increases FOV though.
Two high impact game settings I would turn down first are hairworks and foliage distance.