gambit78

Hi Andy, I meant it as starting DCS, without starting VAICOM at all. If you are already stuck at 10% at this step, that means an earlier launch of VAICOM has already messed up some files. To solve this, go to Steam and perform a verification of game files. It will likely detect 3 files that have failed and fix them. After this, launch DCS WITHOUT launching VAICOM. You should be able to launch DCS without this problem anymore. However, when you next launch VAICOM to check the openbeta box, it will corrupt 5 files. Then you have to perform verification again. But after this time, all should be good going forward.

Well well, this worked! I'm still flabbergasted that we have to check the custom path as well as check the ob box, something that is EXPLICITLY indicated that Steam users SHOULD NOT do. Something really went wrong in this patch. :doh: Anyway, sequence of my own recovery, if anyone is interested. (Steam openbeta user). 1. Run DCS without VAICOM, to verify all ok. Loading was successful. Closed DCS. 2. Run VAICOM to check "use custom DCS path", point to Steam installation folder, and checked "ob". 3. Run DCS. Loading failed as usual at 10%. 4. Closed DCS and VAICOM, initiated Steam verification of game files. 5. Instead of 3 files found faulty, 5 files are found this time. 6. Launched DCS without VAICOM. Ok to launch. Closed DCS. 7. Run VAICOM normally. Run DCS. 8. Things seem normal as per the good old 2.5.5 days. Thanks to everyone who helped!

I'm also not daring to do what you are doing! Just crossing fingers and hoping another update from DCS or Hollywood would fix it. Very sad at the moment.

@Japo32....if it makes you feel any better...I'm in exactly the same spot as you. If all the other Steam users have had no problems, then there may be a reason why our VAICOM is corrupted. Did you go through the same sequence below as I did? a. I was on Steam 2.5.5, that was when the DCS patch was yanked from Steam. b. I played DCS on that 2.5.5, and before I did so, I launched VAICOM as normal. The VAICOM update came in. I continued to play DCS 2.5.5 with no problems on VAICOM. c. Couple days later, the Steam 2.5.6 came out. d. And that's when I got all the 10% freezes with VAICOM, and smooth running of 2.5.6 if I verified my files and don't launch VAICOM. I am suspecting our VAICOM got corrupted because it came in before the Steam patch. I have no evidence, though.