Elite Dangerous has lost headtracking. SteamVR is reporting a room setup error, but only after ED has been launched. I’ve rerun the room setup, first in PiTool and (when that didn’t work) in SteamVR. I’ve checked my ED in-game headlook/headlock settings, which look OK. I know it’s not a tracking issue, since the “round grid” startup area in SteamVR tracks fine. I know ED is still running: I can use the menu and the cargo-bay launch area is animating, but it’s not moving when I turn my head.
Has anyone else seen a problem like this?
The only configuration change I made was to the maxResolution setting (from 4096 to 8192), but that should not affect headtracking.
[Update] I fixed it by uninstalling and re-installing SteamVR.
Are you still having problems? I have just started VRing again after a couple of months’ summer break (hot weather and VR don’t go well together for me), and have had no tracking issues with Elite in VR in the last couple of days.
I seem to have worsening performance however, not sure why. I’m using older drivers (PiTool .129 and Nvidia drivers from July or so). It may not be a new issue, but I have had to drop quality down to 1.0 in PiTool and In Game SS, and it’s struggling to maintain 45 fps in space - before I was able to run higher quality settings before seeing this kind of performance hit. This is with a i9900k and 2080Ti and a pretty clean setup. Not a PP issue as far as I know, unless somehow demands have increased with an update? Elite or Win10 etc?
I guess I should update everything, but with Pimax, the latest update doesn’t necessarily mean best stability and performance
Up until last night, I hadn’t had any problems with PiTool .180 and recent nVidia drivers (currently ver 436.15).
My PiTool settings have changed and been restored to the previous values (I think). This is because a friend came by to experience VR and I reset stuff like Vertical Offsets and ran some other games and apps (which I hadn’t run in weeks). I also set the SteamVR maxRecommendedResolution to 8192 (up from 4096).
None of those things should have affected headtracking, so I think this is an ED-only issue.
