something went very wrong when vaicom updated itself

[lolwut845]

I've been having a blast with vaicom until yesterday, when vaicom decided to update itself. The next time I started dcs, all my menus were flickering. So I followed the faq, reupdated my dcs custom path and then hell broke loose.

All the menus just vanished, and even without VA, I can't use the radio in DCS anymore or interact with any of the F# menus. Jester is completely gone, too.

 

Vaicom seems to recognize what I'm saying, but doesn't know which module I'm flying and doesn't seem to interact with dcs.

 

So far I've :

1- repaired dcs -no luck

2- reset vaicom, tried "Hide on-screen text" ticked and un-ticked -no luck

3- repaired dcs again -no luck

4- updated dcs to the latest open beta -no luck

5- deleted all subfolders related to vaicom in my saved games folder, and all i could find in dcs main folder related to vaicom, repaired dcs once more -no luck

6- rolled back to stable -you guessed it, no luck

 

my next step would be a complete reinstall of dcs and VA/vaicom, saving only my liveries and joystick profiles. Before I do that and redownload 200GB, what else can I try ?

 

When I'm running debug mode, vaicom seems to be messing with both DCS and DCS.openbeta folders, which is really weird, since my registry entries seem to be correct and the sliders set to standalone and release/open beta/whatever I'm running at the time.

DCS is looking for the files in my "saved games/dcs" folder, not dcs.openbeta

 

Any help would be greatly appreciated

Edited June 12, 2020 by lolwut845

[Talvid]

My pc prompted me to update, at 1am, after reboot my X52 programming software won't open.

[hornblower793]

Could you post a screenshot of the VA log (with VAICOM in debug) for when you have just started VA - particularly interested in the bottom of the log (the first entries). Alternatively, attach the VAICOMPRO.log file (found in your <install path for VoiceAttack>>Apps>VAICOMPRO>Log folder)

[lolwut845]

Could you post a screenshot of the VA log (with VAICOM in debug) for when you have just started VA - particularly interested in the bottom of the log (the first entries). Alternatively, attach the VAICOMPRO.log file (found in your <install path for VoiceAttack>>Apps>VAICOMPRO>Log folder)

 

Thanks for the quick reply !

 

The log is attached.

VAICOMPRO.log

[hornblower793]

Looking at the log file it seems to think that both stable and openbeta are installed in the same location. Did you roll back to stable by updating the OB install?

 

 

If you currently only have the OB installed, it might be worth going into your registry and deleting the DCS stable key (Computer\HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World) and seeing what happens

 

 

Also, the FAQs might help (https://forums.eagle.ru/showpost.php?p=4311067&postcount=5)

 

 

If this doesn't work come back and we can think of something else

[lolwut845]

You're right, I messed up and mistakenly merged the release and the openbeta. Looking through the registry, my dcs installation was a bit of a mess anyway. I had remnants of 1.5 in the registry (!!!).

I binned it all, and restarting fresh with correct paths.

 

Thank you for pointing me in the right direction :smilewink:

 

edit: everything is where it needs to be and everything works correctly !

Edited June 12, 2020 by lolwut845

[hornblower793]

Good to know:thumbup: