Ohioflyer15

I went into SteamVr and uninstalled-reinstalled, no change. But luckily, SteamVR has a "beta" options that is essentially an intentional rollback of the version to allow compatibility with older HMD's. I selected it and it rolled back SteamVR all the way to 1.15.12 and this appears to be working! What method is best to run the incompatibility of the new SteamVR release up the flag pole? And should I rename this thread?

Weird, I'm not opted into any betas in SteamVR. Let me see if I can reverse that

Thanks Flappie, I have tried the things you mentioned. Much has also changed overnight including a new graphics driver (which I certainly checked yesterday!) and DCS also updated itself to a .1 version and I have both installed now. Long story short, the problem remains. Attached are windows updates that I did as a package. I also remembered that steamVR indicated it updated itself when I launched it prior to these issues. I apologize for not including it before. steamVR is on version 1.16.8, released only 3 days ago. I agree there might be more than one problem happening. The 310 error certainly points to the VR while the dx11 error I was getting in 2D regardless of the VR status. I always open SteamVR manually before starting DCS. SteamVR has no problem running on it's own or running other games. I followed your helpful links in attempting to resolve the 310 error. Launching the server before the utility doesn't seem to have changed anything, and launching SteamVR in safemode didn't either. I had some issues when first starting VR that many files needed admin privileges. This didn't seem to help either.

Lange, I have the same issue and I did update to the latest preview... I started another thread possibly pointing the finger at that with logs etc

Hello everyone, I've been playing DCS in VR without issue for a few weeks now. Nothing unusual to report at that time. Today I did a windows update (one of many during these weeks) and then opened DCS in 2D to work on a mission. No issue. Upon trying to open DCS in VR later today to fly the mission with others, DCS checks for an update, displays the DCS logo initial splash screen, logs in and authorizes normally, and then hangs on that initial splash screen (desktop visible) for a very long time (minutes) before appearing to abort loading in VR and instead loads the 2D game. It won't load into VR at all. I try to then play a 2D game and it fails to load into a game because of what appears to be a graphics/DX11 issue and crashes When my Index is shut down and DCS isn't trying to load into VR, the game loads faster to the main screen but still runs into the same error message and crashes. I'm not sure what changed between the Windows update > Successful 2D play > Attempted VR play fail > Attempted 2D Fail. I've checked for driver or other updates for Steam/Valve, Windows, Nvidia, DCS, etc and think I'm up to date, multiple restarts, etc. I was playing fine and well about 3 days ago and the windows update is the only thing I can think of that changed. Logs, system info, and (possibly unrelated) error message below. edit: I followed the general troubleshooting guides on removing saved games folder, repairing the program, checking pagefile size, etc. I removed the shader files to allow them to rebuild as well. All mods are removed. I appreciate your help Valve index HMD dcs.log sys.nfo

I've been looking for a mod that would continue to cut down on redundant radio calls while playing VR (and therefore cut down keyboard searching). I'd be grateful for someone to point me to it if it exists please. If a friendly is within a 1/4 or 1/2 mile of a tanker, why not just have the tanker extend the basket and be ready to give fuel immediately on contact? If it's a large aircraft, and there are two friendlies in the zone, extend both baskets. At least this call requirement could be optional so the player could decide whether to utilize the multi-step radio interact personally, or if the pilot would self-call, like he/she does over the carrier tower on the break (no player interaction, call is made autonomously "Tower, 215, overhead, state 5.6"). If someone could explain the need for the "pre-contact" calls (and resulting basket denials if unsuccessful) and why it's required for the player to physically select that call in game, I'm happy to receive an education! Thanks all, Cheers!

Hello friends. Is there a tactical advantage to NOT running IFF? I'm spooling up on multiplayer and accidentally killed a teammate returning from an objective tonight. Night mission, everyone was flying out in the teens (long haul), and this flight of two were flying opposite direction, sub 5,000 feet, passing at 2-2:30. They were both returning constant unknown/ambi IFF interrogations while the rest of the screen was green friendlies. I thought they were bandits that squirted through, running for an objective behind us. I rolled in behind them and :doh: Obviously I botched that one, but why not run IFF? Especially when passing other friendlies while headed home? Did I myself have settings wrong? I just turn it on usually and it seems to work...Thx still learning