Hahaha, the joy didn’t last long. The inability to map controls in IL-2 is back again. Can’t continue swapping DP everytime I want to change something. Since it appears only IL-2 suffers from this strange “null/null” decease in VR I’ll stick to DCS. The development of IL-2 and particularly the will to adress bugs and strange things is absent it’s perhaps time to let it go.
1 Like
I have been thinking the same… Unfortunately this is where I get my WWI fix.
Ad spatial audio solution:
I understand that if I plug a wired earbuds (like those provided with the Aero) directly to the headstet, I will get spatial audio (i.e. audio reacting to my head position vis-a-vis the sound sources).
But how about if I want to use my Bluetooth earbuds with the Aero? If I connect them to my PC, am I able to use them with the Aero in such a way so that I get spatial audio?
Any experience with such a solution or you always plug your headphones / earbuds to the Aero’s 3.5 jack?
Thanks.
False alarm, actually.
I connected my bluetooth earbuds (Jabra) to my PC, fired up the MSFS and it works as it should - I get spatial audio as I should - no special fiddling with settings.
No idea how that is possible but I am not complaining 
2 Likes
I think you get that with TrackIR or simply a POV hat too. It’s the viewpoint in the sim that determines the position of the sound.
2 Likes
Makes sense 
It looks like I am overthinking sometimes
2 Likes
I never do that…
3 Likes
@Troll Running IL-2 as admin makes it possible to map controls. Tested it and it works. Not happy running software with admin privileges so I will map the controls and when happy I’m disabling admin rights. Disturbing that only IL-2 requires this “workaround”
2 Likes
@Troll
Got info about another way to map controls in IL-2 without the need to do it in 2D or give admin rights.
Start IL-2 and when in VR open the virtual workspace via the HMD menu button. Do the mapping and return to IL-2 
It works, I have just tried it.
3 Likes
I would never have thought of that…!
So far still no solution to my SteamVR problem with the Varjo Aero. No matter what I tried, SteamVR refuses to even start with the headset connected, always a critical error upon start. Varjo support seems to be also overasked by this behaviour. For now it’s back to 2D and TrackIR… the headset is for now an expensive paper weight.
1 Like
Away from my PC but still…
-
Are your SteamVR base stations working properly? (i.e. steady green LED light; one of my base stations started to blink red and stopped working, Varjo Base software shows only one base station connected).
-
Haven’t you, perhaps by chance or when tuning DCS, switched off OpenVR support in Varjo Base? What error are you getting from SteamVR? I got an error message with OpenVR off when running Room Setup.
Thanks for your reply! Any assistance debugging this is welcome.
The headset and base stations work just fine on my racing rig PC. The main desktop/flight sim PC is having the trouble. OpenVR and OpenXR support is both set to on in Varjo Base.
Unfortunately SteamVR only shows critical error, not much information else. I once got an error code after deleting and re-installing everything, but according to google it was a generic one as well.
Steam Support won’t help as they don’t support Varjo Aero headsets.
1 Like
thats unfortunate. but … did you try already to turn off and turn on your PC ? 
just joking
how about reinstalling the whole windows? or you are trying to not go this way unless its really necessary?
Am I reading this correctly, that it works on one PC but not the other?
Is the failing PC overclocked?
I’ve re-installed Windows 10 while keeping my files, as this did not result in a fix, Varjo support advised to try Windows 11. This is where I’m at now, it’s not too bad, only some powershell script broke, rest seems ok so far.
Neither the racing rig nor the main desktop are overclocked. Also I did not alter anything drastic between 15th October when I last played with the VR headset to 20th October when the positional tracking was broken and SteamVR refuses to start.
It’s not that I’m actually unfamiliar with broken systems, but this one is a bit mind boggling. I checked the Windows install history and tried to revert the driver updates since 15th, but this did not help either. I even wrote a Google doc with all the troubleshooting steps outlined: Varjo Aero Troubleshooting - Google Docs
What bothers me most is that the Varjo support person has not even shared a hypothesis with me on what’s going wrong. It’s more like ‘did you try this, did you try that, upgrade this, downgrade that, check your BIOS version’.
Cheers,
TeTeT
Have you tried resetting SteamVR?
definitive method to reset or restore SteamVR to default / factory options (clean Reinstall) :: SteamVR Troubleshooting (steamcommunity.com)
Yes, I used a different guide, but I uninstalled SteamVR, deleted all artefacts remaining, rebooted, installed SteamVR, same result: Critical Error upon Varjo Aero availability.
Meantime Support has confirmed that they inspected all my debug and troubleshooting info and it seems one of the devs has a similar if not the same problem. They will come back when they have a theory and hopefully guidance on how to resolve the issue. I just hope the dev has the exact same problem
Cheers,
TeTeT
2 Likes
Frustrating for sure. I recall hours trying to get my G2 working a few years ago. Turned out it was my USB port - only one had what it took to generate…whatever it needed?..to connect. And I had about 6-8 ports.
Was a last ditch effort. Funny though my Aero can plug into any slot and work. Enough to make a person want to buy a console rig…[shiver]
2 Likes
Varjo Support recommended me as probably a last step to re-install Windows on the system where the SteamVR does no longer start. I was less than thrilled about it, did some reading and now installed a second Windows 11 on my hard disk.
And indeed, on this vanilla Windows 11 system SteamVR starts, VarjoBase calls the SteamVR room setup and everything is happy. But for me, who now needs to reinstall the main system on the SSD and can only hope that whatever software conflict caused the problem does not happen again. When I go from a vanilla Windows 11 to one that I actually want to use, who knows what will happen… But at least some light at the end of the tunnel!
3 Likes