Search Results for 'directvr'

[cc_rock]

Hi all,
I am not completely new to VorpX, I used it in the past with an Oculus Rift (a few years ago, so most likely quite a few versions ago), and I remember Dear Esther working particularly well, with almost perfect Direct VR, positional head tracking too.

I tried again now with a Quest 3 through Virtual Desktop (I read that it should work if I select Steam VR mode).. the game launches and it is hooked by vorpX, but it works terribly.. flickering, no positional tracking, head turning works but I can see black areas when I turn my head and the rendering that “catches up” later and gets in front of me with some delay, if you know what I mean..
I am on Windows 11 so I read Ralf’s message about performance issues with DX9 games (not sure if DE falls into this category) on Windows 11 and so I tried upgrading to vorpx 24.1.0, but nothing changed.

I tried re-scanning directVR but it seemed to have made things even worse.. what am I doing wrong? Any suggestions?

[Ralf]

Hmmm. First please try to reset the profile to default in the vorpX menu. All you should have to do for KCD is running the DirectVR scanner for FOV and 1:1 low latency head tracking, plus potentially adjusting the resolution in the vorpX menu.

If the issue still occurs after resetting the profile and running the DirectVR scanner, make sure that vorpX is set to native Oculus mode or OpenXR, not SteamVR. Shouldn’t really matter, but worth a shot. If that still doesn’t help, try to disconnect the PlayStation gamepad.

[Greyhaim]

Thanks for coming back to me Boblekobold.

Still not sorted but close! I haven’t had this with other games im playing such as Starfield or Stalker Anomaly, just with Fallout 4.
I am playing the Fallout Anomaly mod pack and it all looks really good apart from this scope thing. I have tried with as many FalloutPrefs, custom etc to match up FOV’s and done the directVR scans in game but nothing works.
I then downloaded the 24.1.0 vorpx beta today, fired the game up and did a DirectVR scan and it worked! Scopes were working as they should and zooming in. Paused the game, it then went really blurry and crashed when i tried to reload. Now getting in game and doing the scan doesn’t change anything and scopes not working again.
The FOV does stutter around in game so i think it might be one of the mods causing problems but with 816 mods i have not idea which one!

[Boblekobold]

@Greyhaim :
I guess you could not use DirectVR and check “Don’t Optimize game settings”.
Then you set a very high 4:3 resolution (for Quest 3 or Reverb G2) in game (use VorpX Beta and virtual monitor to enable any resolution you need).
I usually use 3840×2880 or at least 2880×2160 on my Reverb G2.
Try to set ClarityFX to full (and adjust sharpness).
Unzoom full VR.

Then raise FOV (google “change fallout 4 fov”)

Try 120 and adjust it until you have the right scale (remember the value, it will be approximatively the same in every game).

Adjust headtracking sensitivity.

[Ogrescar]

DirectVR never works correctly with Skyrim SE, at least not for me, but I use version 1.5.97. The fov scan almost always works, but the rotation always fails, even when the scan result is successful. Probably because of my 1100+ mods though, including 3 direct11 hooks and a directinput hook, so I’m lucky that vorpx even works.

[Senan]

I Just started playing Skyrim again after about a year or so and my FOV part of the scan is failing every time. The game is currently unplayable without the proper setting and the manual option in the Vorpx menu is greyed out so I can’t alter it. I never had an issue with the DirectVR before so I’m confused what changed.

Any help is appreciated.

[theflashig]

Hello everyone,

every works fine except one thing: Looking down unarmed.
When doing it, the vr view flickers and also it changes to poster view for a moment.
It happens with headtracking on/off and with vr-controller or normal controller/keyboard input.
But when holding a weapon (also melee) or with the opened options menu, the problem doesn’t occur.

What setting could be here the problem?(config below)
Bug or conflicts between headtracking and input?

I couldnt find any similar topic.
I appreciate the help and thanks to devs for this awesome mod!

Here the configs:
[Image]
fImageZoom=0.850000
fUiScale=0.675000
fUiScaleHorizontal=1.000000
fUiStereoOffset=0.565000
fEdgePeekScaleMin=0.660000
fEdgePeekStereoMultiplier=0.500000
iImageBackground=0
iAspectRatioCorrection=1
fImageSharpness=0.500000
fImageGameGamma=0.840000
fImageGameSaturation=1.010000
iImageInputGeometryType=0
iImageInputStereoType=0
bImageInputStereoFlip=False
iImageInputSurroundFovH=360
iImageInputSurroundFovV=180
bImageInputSurroundGuessParams=False
iGameDisplayMode=1
iVirtualScreenScene=100
fVirtualScreenHtMultiplier=0.000000
fVirtualScreenDistanceOffset=0.000000
fVirtualScreenCurvature=1.000000
bVirtualScreenCurvedVertical=False
fVirtualScreenBrightness=1.000000
fVirtualScreenEnvBrightness=1.000000
fVirtualScreenEncGamma=1.000000
fVirtualScreenEnvSaturation=1.000000
iVirtualScreenAspect=0
iVirtualScreenAntialias=4
fImmersiveScreenHtMultiplier=0.500000
fImmersiveScreenDistanceOffset=0.400000
iDirectModeRenderQuality=3
bDirectModePresentOrigImage=False
iDirectModeThreadSync=2
bVirtualScreenMode=False
bVirtualScreenLockHeadTracking=True
bEdgePeekDisableStereo=False
iEdgePeekBackground=0
fImageAmbienceBrightness=1.000000
fImmersiveScreenCurvature=1.000000
bImmersiveScreenCurvedVertical=False
iImmersiveScreenBackground=10
iImmersiveScreenEdgePeekBackground=10
iDirectModeRenderAsyncModeNew=0
fVirtualScreenPitch=0.000000
fImmersiveScreenPitch=0.000000
bEdgePeekLockVertically=True
fVirtualScreenScale=1.000000
fImmersiveScreenScale=1.000000
iImageRenderQuality=0
fTextureDetailEnhance=1.000000
fImageSharpnessV2=1.000000

[General]
sVersion=23.1.0
bSkipStartRoom=False

[Input]
fHtSensitivity=0.250000
bHtInvertX=False
bHtInvertY=False
bHtPosTrackingEnable=True
bHtPosTrackingOverrideLock=False
fHtPosTrackingUserMultiplier=1.000000
fHtG3DLatencyEnhancement=0.000000
bHtCrouchJumpEnabled=False
fHtCrouchPosYThreshold=-0.100000
fHtCrouchVelocityThreshold=0.700000
iHtCrouchKey=162
bHtCrouchCrouchKeyIsToggle=False
fHtJumpPosYThreshold=0.050000
fHtJumpVelocityThreshold=1.000000
iHtJumpKey=32
bMouseDisableAcceleration=False
bMouseHandleCursor=False
bMouseForceVorpCursor=False
bKeyBlockAlt=True
bKeyBlockEdgePeek=True
bKeyBlockVorpX Menu=True
iXiOverride=0
iXiOverrideDirectVR=0
bXiOverridePartLeftStick=False
bXiOverridePartRightStick=False
bXiOverridePartButtons=False
iXiHtControllerNum=0
iXiHtMode=0
fXiHtDeadzoneCorrection=0.000000
fXiHtSensitivityX=1.000000
fXiHtSensitivityY=1.000000
fGpadSensitivityLeftX=0.150000
fGpadSensitivityLeftY=0.150000
fGpadSensitivityRightX=0.500000
fGpadSensitivityRightY=0.050000
fGpadDeadzoneLeft=0.200000
fGpadDeadzoneRight=0.200000
iGpadWalkRunKey=160
bGpadWalkRunInvert=False
bGpadWalkRunIsToggle=False
fGpadThumbStickCurve=2
iGpadVorpXButtonMode=2
iGpadVorpXButtonBind1=1
iGpadVorpXButtonBind2=0
iGpadKeycode0=69
iGpadKeycode1=70
iGpadKeycode2=82
iGpadKeycode3=32
iGpadKeycode4=71
iGpadKeycode5=77
iGpadKeycode6=2
iGpadKeycode7=1
iGpadKeycode8=38
iGpadKeycode9=40
iGpadKeycode10=37
iGpadKeycode11=39
iGpadKeycode12=162
iGpadKeycode13=81
iGpadKeycode14=27
iGpadKeycode15=9
iVhkKeycode0=27
sVhkVisText0=ESC
iVhkKeycode1=116
sVhkVisText1=QSave
iVhkKeycode2=120
sVhkVisText2=QLoad
iVhkKeycode3=77
sVhkVisText3=M
iVhkKeycode4=49
sVhkVisText4=1
iVhkKeycode5=50
sVhkVisText5=2
iVhkKeycode6=51
sVhkVisText6=3
iVhkKeycode7=73
sVhkVisText7=I
iVhkKeycode8=52
sVhkVisText8=4
iVhkKeycode9=53
sVhkVisText9=5
iVhkKeycode10=54
sVhkVisText10=6
iVhkKeycode11=0
sVhkVisText11=
iVhkKeycode12=55
sVhkVisText12=7
iVhkKeycode13=56
sVhkVisText13=8
iVhkKeycode14=57
sVhkVisText14=9
iVhkKeycode15=48
sVhkVisText15=0
iVrhcControllerMode=0
iVrhcTrackPadModeLeft=2
iVrhcTrackPadModeRight=1
fVrhcDeadzoneMouse=0.100000
fVrhcDeadzoneKeys=0.300000
bVrhcAllowLeftStickShift=True
bVrhcShiftSwapLeft=False
bVrhcShiftSwapRight=False
iVrhcKbmStickModeLeft=1
fVrhcSensitivityLeftX=0.250000
fVrhcSensitivityLeftY=0.250000
fVrhcSensitivityRightX=0.250000
fVrhcSensitivityRightY=0.070000
iVrhcExtraKeyLeftGamepadDefault=0
iVrhcExtraKeyRightGamepadDefault=3
iVrhcControllerVisType=1
iVrcKeycode0=1
iVrcKeycode1=2
iVrcKeycode2=87
iVrcKeycode3=83
iVrcKeycode4=65
iVrcKeycode5=68
iVrcKeycode6=69
iVrcKeycode7=67
iVrcKeycode8=82
iVrcKeycode9=70
iVrcKeycode10=71
iVrcKeycode11=32
iVrcKeycode12=27
iVrcKeycode13=9
iVrcKeycode14=160
iVrcKeycode15=162
iVrcKeycode16=38
iVrcKeycode17=40
iVrcKeycode18=37
iVrcKeycode19=39
iVrcKeycode20=136
iVrcKeycode21=137
iVrcKeycode22=49
iVrcKeycode23=50
iVrcKeycode24=51
iVrcKeycode25=52
iVrcKeycode26=69
iVrcKeycode27=81
iVrcKeycode28=82
iVrcKeycode29=32
iVrcKeycode30=0
iVrcKeycode31=0
iVrcKeycode32=0
iVrcKeycode33=0
iVrcKeycode34=0
iVrcKeycode35=0
fGpadNativeSensitivityRightYFullVR=0.600000
fGpadNativeSensitivityRightYCinema=1.000000
bHtEnable=True
bHtRollEnable=True
bHtOtEnable=False
bHtOtSupportsPosition=True
bHtOtSupportsRoll=True
bHtOtDisableMouseYawPitch=True
bVrhcGesturesEnabled=False
bVrhcGestureGeneralEnabled=True
bVrhcGestureCombatEnabled=True
fVrhcGestureSteeringSensitivity=1.000000

[DirectVR]
bDvrEnable=True
bDvrForceGameHelperFov=False
fDvrFovWorldOffset=20.000000
fDvrFovPlayerOffset=0.000000
bDvrLockLookPitch=True
bDvrPositionEnable=True
bDvrUseCache=False
bDvrUseMod=True
iDvrModCameraMode=0
fDvr3dMult=1.000000

[GameHelper]
bGhChangeSettings=True
bGhChangeResolution=True
bGhChangeFov=False
bGhChangeFovRT=True

[D3D12]
i3DCreateMethod=0
fSeparationNormal=0.620000
fFocOffsetNormal=0.040000
fSeparationComplex=1.000000
fFocOffsetComplex=0.000000
bUseDOFComplex=True
fZMultF=0.500000

[oculusquest369]

Hi… after update 2.11 and 2.12 the game is unplayable with lots of stutters. If I disable CONNECTION MODE the stutters go away, but the option to enable DIRECTVR disappear, only Z-normal and Z-adaptive is active.
I have the last CET. Tested with pimax and pico 4.
In flat screen is fine.
I used Vorpx and CyberpunkVR the same story. Any idea? Thanks

[bravekat]

For CP2077 2.12, I had to update CET modding framework for directVR 3D to work. I am using stand alone version of vorpx CP2077.

[Ralf]

Huh? There are profiles for all Metro games except for the Exodus DX12 version, which for the most part was an nVidia marketing stunt with marginally improved lighting at the cost of performance anyway.

BTW1: All Metro proflies come with DirectVR (“in-engine”) head tracking, automated FOV setup and various VR related tweaks. Also games like these are perfect for motion controller gestures (requires vorpX 24.1.0). Good luck finding any of that that elsewhere.

BTW2: IIRC the original DX9 versions of the first two games also perform better than their DX11 counterparts, which obviously is highly important for VR. So whether the enhanced edition builds are the better choice is quite debatable.

[Ralf]

Still working here (Steam version). Both 3D and DirectVR tracking.

If you encounter issues like broken 3D or a wrong camera field of view, please reset the game’s graphics options to default and double check whether you maybe accidentally disabled automatic game settings in vorpX. Often vorpX auto-adjusts settings that are vital for 3D to work correctly.

[Ralf]

Please stop spamming the forum with the same question over and over again. You don’t get better answers by posting the same thing half a dozen times. I have deleted your other posts.

Both options mentioned in my reply above unock the Y-axis, depending on whether the game has DirectVR headtracking or not. If you still have an issue with your Y-axis after applying the hint(s) above, your issue is not caused by vorpX.

On a sidenote: Looking up and down with your head only is typically what you want, so think twice before you disable this feature when it is available. All native VR games work that way. Keeps the horizon in VR in sync with the real world horizon.

[ceedj]

Seems the program (normal vorpx) can’t/won’t re-apply the Z-Normal setting on a new session. I flip it to DirectVR and back, presto, the UI looks smoother when, well, looking. Moving the camera with the mouse is very smooth, but using the right stick is a little jittery. Just the camera moving I mean, controls seem fine otherwise. It’s probably a game limitation.

It would be nice if we could keep the UI in place while still being able to adjust elements, but I understand if it’s related to the way you hook into the UI and make it work with tracking and such; it seems very similar in GTA: SA. I did play around with turning small things on and off like the head tracking, but then it becomes a game of pick your poison: ghosty UI or ghosty main screen. I’m sure it’s all a very delicate dance behind the scenes.

Anyway, I am pretty much sorted at this point, so thanks, and again, really nice job with this!

[Ralf]

The underlying issue here is that the game can’t handle simultanous mouse and gamepad input. Since vorpX per default emulates a mouse for head tracking it has to convert your gamepad input to mouse/keyboard input to deal with this issue.

There is an very easy method to improve things though in this case:

Make sure to run the DirectVR scanner as suggested by the instructions shown in the top/left corner of the game window. After a sucessful scan vorpX can directly access the game camera for head tracking and doesn’t have to use mouse emulation more. It will then automatically disable the gamepad override and you can use your gamepad natively.

[romandesign]

Interesting, I tried a few FOV settings and nothing worked, then I reset the game to what I had before and it worked perfectly. I’m not sure why it didn’t work right away with this FOV. Maybe because of some other settings I edited in the stock profile. It’s basically empty, so I had to set up everything from scratch: gestures, some key maps, and other settings – because it’s not possible to override a stock profile with my own, only to change its settimgs. So maybe something else affected this.

DirectVR Scan still doesn’t work. Sometimes it fails, but usually it reports “success” but then the head tracking is not working at all.