Dirt Rally 2.0 Star VR settings:
Dirt Rally 2.0 is quite good now with these settings!
My point below is about the Mura issue only.
Yes, this started happening to me also after a recent update with Steam. They incorporated a sort of security mechanism. It seem that it may be causing an issue with Steam not loading the Mura files, perhaps with Steam locking the headset on a constant basis. I am getting this idea from an exchange I had with Lionel not long ago.
He asked for the "the _G suffix " and if there were any errors with the StarVR drivers âvrserver.txtâ (itâs the log file from openvr server located in C:\Steam\logs\vrserver.txt IIRC)
I provided him the files and an extra file called âvrserver.previousâ that I found.
" Ok I donât see anything wrong with your PCD files.
However I see the communication failed with the HMD firmware in the log file (previous one):
> Sat May 23 2020 09:28:30.655 - StarVR: Reading device settingsâŚ
> Sat May 23 2020 09:28:30.824 - StarVR: Invalid display serial number L: R:
> Sat May 23 2020 09:28:30.824 - StarVR: Could not retreive the SteamVR tracker serial number in the StarVR stored json file
> Sat May 23 2020 09:28:30.824 - StarVR: Reading device settings done
> Sat May 23 2020 09:28:30.824 - StarVR: Serial Number:
> Sat May 23 2020 09:28:30.824 - StarVR: Model Number: StarVR One
> Sat May 23 2020 09:28:30.824 - StarVR: Tracker Serial Number
> Sat May 23 2020 09:28:30.824 - StarVR: Left Display Serial Number
> Sat May 23 2020 09:28:30.824 - StarVR: Right Display Serial Number
> Sat May 23 2020 09:28:30.824 - StarVR: Window: 0 0 3840 2240
> Sat May 23 2020 09:28:30.824 - StarVR: Render Target: 0 0
> Sat May 23 2020 09:28:30.824 - StarVR: Seconds from Vsync to Photons: 0.001800
> Sat May 23 2020 09:28:30.824 - StarVR: Display Frequency: 90.000000
> Sat May 23 2020 09:28:30.824 - StarVR: IPD: 0.064000
> Sat May 23 2020 09:28:30.824 - StarVR: Display Order Right
> Sat May 23 2020 09:28:30.824 - StarVR: Display SPR status OFF
> Sat May 23 2020 09:28:30.824 - StarVR: Render Plane angles h:0.000000 v:0.000000 n:0.000000
> Sat May 23 2020 09:28:30.824 - StarVR: Render Plane fov h:0.000000 v:0.000000
> Sat May 23 2020 09:28:30.824 - StarVR: Opening pipe for inter process communication
> Sat May 23 2020 09:28:30.824 - Driver âStarVRâ attempted to add tracked device with no serial number
and then everytime afterwards it says:
> Not loading driver StarVR because it was blocked by a previous safe mode event
It seems that the first time you launched steamvr, the device wasnât properly communicating with the driver and it was put in safe mode to prevent steamvr to crash.
Itâs weird because you shouldnât be able to use the StarVR at all, unless the log file is not complete and somehow recovered later.
The above is what he found
Not sure if anything here sparks anyone anything regarding the StarVR and SteamVR
Interesting. I searched my vrserver.txt and I never had a line which mentions âno serial numberâ. It appears my serial numbers were always recognized. However I did have the Not loading driver StarVR because it was blocked by a previous safe mode event.
I think when it crashes with a critical error is actually related to the timing of when I power on the index controllers. I think if I wait until the headset is on my head and everything is working properly BEFORE I power on the index controllers, then it doesnât crash.
I wonder if rolling back to an older 2019 version of steam vr would fix both the mura and the crashing?
Holy âŚ, hopefully this can be resolved so we can enjoy SteamVR without Mura lol.
Does anyone know what the fake âVive Trackerâ does in SteamVR? I assume itâs for the hmd tracking?
It causes problems with VRCHAT. I e-mailed the VRCHAT team and they are helping resolve the issue hopefully so we might have it working in the future. 
I will keep everyone updated.
I think StarVR should mention why Sebastianâs calibration files fixed the mura for him but the same files downloaded doesnât get rid of it for you guys.
It does get rid of it for the showdown demo/dolphinvr. I think SteamVR isnât loading the Mura patch correctly on our hmd and maybe Seb has an older one which doesnât have this problem for x reasons? Hopefully we can find a way.
Very possible. But begs the question, if that is indeed true, they really messed up when deploying these units
I just tried the StarVR One with SteamVR 1.1.4(all the latest 2018 depots) and sadly there is still a lot of Mura.
edit: Just tried with all the latest depots from July 2019, doesnât even launch. All latest December 2019, still Mura.
Here is the info I used to downgrade SteamVR if anyone is interested in trying with other versions.
I wonder if the type of PC you have matters. Sebastian has a 1080 Ti which is the recommended card on their developer page
| Graphics Card | GeForce GTX 1080Ti or Quadro RTX5000 |
|---|---|
| Nvidia Driver | 441.41 for GeForce GTX 1080Ti and 431.86 for Quadro RTX5000 |
They donât say 2080 Ti though which is what I have. Maybe the headset doesnt work well with RTX graphics cards? That could explain why it looked better on @VR-TECHâs other PC. Also maybe the nvidia driver version needs to match whatâs listed?
I tried on both a 2080ti which needs 1 mini dp to dp adapter and a 1080ti with 2 native dp and it looks the same to me. 
Great minds think alike. I tried this one, because it was the latest version of steam vr when the star vr most recent compass app was released (i.e. April 2020) and it seems more stable and it hasnât crashed since. I completely uninstalled star compass as well. Then I installed this older steam vr version, disabled updating, and then I installed star compass. I disabled automatic updates using the advice in the thread to block update of SteamVR putting
StateFlags = 4
in âappmanifest_250820.acfâ under steamapps folder.
Selected Branch: v1.11.11
buildid: 4912955
description: 4/17/2020 build
I have asked about that. The RTX 2080ti is fine, they used them internally. The same point you made here, I ask them about
I did more tests with VRCHAT and it actually works fine. You must hold both controllers to the side and press both triggers everytime you boot the game and join the first world and everytime you change avatars but then it works great. VRCHAT sees the tracker as the hips tracker so the character is standing with itâs hips forward a bit but nothing crazy.
How is the Mura on that app?
Note:I donât use it, just curious
Pretty bad lol. On HL:A level I would say. The fun thing is that there is no culling at all.
I managed to get the Compatible Mode working and tried Dolphin VR(Gamecube emulation in VR) with both eyes open finally and the Mura is on the level of the showdown demo.
I just donât get how Seb barely has any Mura for HL:A⌠While it is playable, it is definitively visible and a nuisance.
I will research how to trigger the Mura with Unity using their recommended settings.
Something is activating it for some reason, if Dolphin doesnt suffer from it
Yeah nvm⌠I tried on other Dolphin games and in some games itâs bad too. In Sonic Adventure 2 Battle itâs really really good but it might be just because of the colorsâŚ
Nevermind, I take it back. It still crashes. Anyone else having the issue of steam vr crashing a lot with âcritical errorâ with their star vr one? It is kind of driving me mad and I have tried everything I can think of, different steam versions, complete uninstalls/reinstalls. I do think it has to do with the index controllers. Because before I had the headset with no index controllers and just used it with a gamepad, and it never crashed.
What version of Steam and SteamVR are you using? Try opting in to the beta versions and seeing if that helps.
I once got a critical error on Steam a few months ago while using my Index and then heard a metal grinding sound in my PC. That happened only once and my PC has run fine since then and I havenât had any errors. So it could be a hardware issue. What are your PC specs? (CPU, GPU, Ram, and Motherboard)
Me, all the time. Extremely annoying