UNPLAYABLE IN VR
This game is unplayable in VR. It just loads incredibly slow. Its so slow in fact that you cant navigate the menus. Its unplayable garbage I paid $60 for. If this problem isnt fixed I am returning th...
Forum Discussion
Pimax 8kx VR head shake/drift issue and blur in distance.
I hope someone can help, especially with the head shaking issue.
Issue description:
1. Whenever I am standing still with the car, not moving my head at all, the car is shaking around me. Almost like it is drifting a bit, but it is not drifting, it is shaking/like the car vibrates around me. It causes nausea. It is not noticeble when driving, but still, something feels off, if I compare against how Iracing runs in VR for example (which runs perfectly).
When in the garage, it is noticeble even more. In the garage I do not get a smooth 75 fps either. It tried motion smoothing, which helps in the garage with fps, but it does not solve the shaking of the car around me.
Settings:
- I've managed smooth fps driving all tracks using these settings with a 5950X an RTX3080, steady 75 fps, all tracks and weather conditions. Get ok quality image but still pretty blurry in distance if I look at billboards or kerbs and cars in distance. Closeby it is fine. (again Iracing looks perfect in distance in comparison).
Pitool:
Render Quality: 1.25
Field of View: Small
Parallel Projections: Off (tried on as well, no difference)
Smart Smoothing: Off (tried on as well, no difference)
Compulsive Smooth: Close
Hidden Area Mask: On
Tracking Mode: Lighthouse (using 2 lighthouses, both perfectly in range)
Refresh Rate 75 (90 possiblee, but scaling resolution is more important to me)
Steam VR:
Resolution: 3044 x 3036 74%
Motion Smoothing: Off
F1 22 Hardware_settings_config_VR.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<hardware_settings_config applyOOTB="false">
<cpu name="AMD Ryzen 9 5950X 16-Core Processor " processors="12" processorStride="1" processorBinding="1" />
<graphics_card deviceId="0x2206" rating="4">
<resolution width="1024" height="721" displayMode="0" vsync="false" vsyncInterval="auto" frameRateLimiterEnabled="false" frameRateLimiterValue="120">
<refreshRate numerator="0" denominator="0" />
<windowPosition x="1182" y="340" />
<outputMonitor index="1" />
<aspectRatio auto="false" width="16" height="9" />
<hdr mode="0" peakNits="1000" />
</resolution>
</graphics_card>
<motion>
<dbox enabled="true" />
<udp enabled="true" broadcast="false" ip="127.0.0.1" port="20777" sendRate="60" format="2022" yourTelemetry="restricted" onlineNames="off" />
</motion>
<antialiasing taa="true" checkerboard="false" cmaa2="false" dlss="false" cas="1" fsr="0" fsr2="0" />
<dlss_quality value="0" />
<dlss_sharpness value="0.000000" />
<fsr_quality value="0" />
<fsr_sharpness value="0.000000" />
<dynamicresolution_enabled value="false" />
<dynamicresolution_target_fps value="0" />
<dynamicresolution_profile deltaDown="0.05" percentageDown="0.85" deltaUp="0.01" percentageUp="0.8" alpha="0.95" />
<dynamicresolution_min_scale value="0.500000" />
<ssao enabled="false" algorithm="0" />
<ssrt enabled="false" quality="0" />
<texture_streaming sizeInMiB="1024" texelDensityBias="0.0" concurrentTextureSwaps="1" />
<led_display fanatecNativeSupport="true" sliProNativeSupport="false" sliProForceBrightness="127" />
<anisotropic_filter level="16" />
<lighting quality="1" volumetricFogLighting="true" volumetricFogLightMapWidth="160" volumetricFogLightMapHeight="128" volumetricFogLightMapDepth="32" />
<postprocess motionBlur="false" godRays="false" depthOfField="false" lensStreak="false" lensFlare="false" bloom="false" />
<shadows enabled="true" skyShadowMapSize="2048" skyShadowCascadeCount="4" skyShadowLowLod="false" worldShadowMapSize="2048" skyShadowMap32Bits="true" nightShadowMapSize="2048" nightShadowCharacterCast="true" nightShadowSourceCount="4" sampling="1" spotShadowMapSize="1024" spotShadowSampling="1" crowdInShadows="false" />
<particles enabled="true" distanceScale="1.0" rate="1.0" high="true" />
<crowd distanceScale="1.0" billboardDistance="1500" />
<vehicle_reflections envMapScale="1.0" envMapUpdateMode="alternate" envMapRenderMode="carsAndCharacters" cubeMapEnabled="false" cubeMapScale="0.75" cubeMapUpdateMode="oneFacePerFrame" />
<mirrors mirrorsUpdateMode="alternate" mirrorsRenderMode="cars" treesInMirrors="true" crowdInMirrors="false" highDetailMirrors="false" highDetailTyresAndCar="false" particlesInMirrors="false" />
<weather_effects rainSplashes="true" rainSheets="false" rainBeads="false" rainHigh="false" trackHeatHaze="false" planarReflectionsEnabled="true" planarReflectionsHQEnabled="false" planarReflectionsRangeScale="1.0" planarReflectionsRTScale="0.5" planarReflectionsMipTailBlur="true" proceduralCloudRTScale="1.0" proceduralCloudTiling="7" proceduralCloudQuality="1" />
<ground_cover enabled="true" grassFlattening="true" drawDistance="60.0" meshes="false" />
<skidmarks enabled="true" parallax="true" />
<skidmarks_blending enabled="true" />
<audio audioUpdateRate="2" numHelperThreads="8" />
<async_compute enabled="true" />
<cs_culling enabled="false" />
<vendor_shader_pack enabled="true" />
<replay_directory path="" />
<rt_quality quality="3" />
<rt_shadows enabled="false" />
<rt_reflections enabled="false" />
<rt_transparent_reflections enabled="false" />
<rt_ao enabled="false" />
<rt_version version="0" />
</hardware_settings_config>
In addition, I had this issue before patch 1.05 as well, now on latest of today (1.05) the issue remains.
Also one other (minor) issue: whenever I start the game it wants to calibrate 'VJOY' (which I use for irFFB with Iracing) and even if I set it up and safe the settings, the question to configure the device returns every time. I simply discard to change the settings every time now, because I have already set up a profile for me wheel/pedals/button box, which works fine. I don't get why I need to set the device settings every time the game starts though. I could uninstall vjoy of course, but that is not my preference because I need it for irFFB.
I think I found the cause, it seems to be a tracking issue, so this may be related more to steamvr, pitool or hardware.
I have created a video showing the issue I am having with jitter in F1 22 in VR with the Pimax 8KX and using two 2.0 basestations: https://youtu.be/T17lT52N_N4
first showing pitool version and basestations are both detected followed by some VR gamecapture where you can clearly see the jitter I talk about when the car is standing still. At this point I was not wearing the headset but I put it on a steady flat surface to rule out any movement from the headset. One of the lighthouses is now on a tripod, I have already tried other (wall and standing) mounting solutions as well, it does not seem to have any effect on the jitter problem, neither does just using one basestation. However as soon as I choose 9 axis instead of lighthouse tracking, no more jitter (but also no forward/backwards/up/down moving possible anymore). Are my lighouses broken? Is there a problem with the tracking sensors or something else on the 8kX? Or is this some F1 22 related? I have now created a ticket for this with Pimax as well, as I am not sure if this is a F1 related issue anymore, but in F1 22 the issue is very pronounced though.I am using to Lighthouses (2.0). They seem to be positioned fine, no reflecting surfaces, both stations in range, did not notice anything off in other games, but playing F1 22 I now notice there may be an issue with them though.
I changed tracking mode from Lighthouse to 9-Asxis (so bypassing the basestations) and the in cockpit ; jitter/vibration/shaking) is gone instantly, but I loose a dimension than of course...
I do notice there is a firmware update available, but unfortunately, there is no way to upgrade the basestations firmware without a Vive HMD and connector, it is not possible using USB in the 2.0 basestations and will not connect and update over bluetooth, so I am not sure if a firmware update may improve things.
Usefull tips are welcome...
- @Gustav543212345 no, this is not related to tracking or hardware. this happens on any headset and any GPU, massive jitter if fps is under headset refresh rate, or otherwise, huge lag between head movement and tracking of view in game. this is a bad implementation of VR in the game, with codemasters / EA to blame
Featured Places
