Menus slowly turning on and off

[dakuth]

I have read every thread I can on this topic, and nothing is working for me. I see it mentioned all the time and the solution is usually to point to a custom path or delete the export.lua.

 

Things I have tried, restarting VA and DCS after each change:

 

1. Delete ..\Saved Games\DCS\Scripts\Export.lua and restart DCS and VAICOM

This broke my SRS and TacView and did not fix the problem

 

2. Set custom path: Go to VAICOM configuration and then Config tab, tick Use custom DCS path set it to the DCS root folder (that has Run.exe in it). Do not tick ob (I'm on stable version.)

No change, though VA logs mention 6/7 files DCS-side files were updated each time I start VA

 

3. Reset Lua: Go to VAICOM configuration and then Reset tab, tick Lua code, and click Master Zero.

No change.

 

4. Reset Lua and Profile. As above, but also ticked profile

No change.

 

5. Toggled Easy Comms on and off. The PTT tab consistently shows Easy Communication: ON, even though I have it off. After toggling it, it changes to OFF, but this doesn't change anything.

 

6. Change PTT Map from SNGL to anything else.

No Change.

 

7. Added in new registry entries:Computer\HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World\Path

This allowed VAICOM to detect DCS without error when I did not set the Config/Custom Path, but menus continued to flicker on and off.

 

 

 

Some added info. This was working. I have made a bunch of changes lately to take advantage of the free month, and I don't know which one "broke" this.

 

I have been using the Steam Version. I moved this install to a Standalone directory and changed it to the Standalone version primarily by using Skate Zilla's updater GUI. Move, modify version.txt, run a repair, that sort of thing.

 

So that got DCS working, and I needed to update VAICOM with a custom path, but otherwise I'm pretty sure it was all working.

 

I then got SRS and installed it. Other than tearing my hair out over how to get SRS and VAICOM to work together in a way that I didn't find frustrating, they were both working.

 

Started using OVGME for mod management because I've started to use a couple - the VR shaders mod, and a asset mod for a mission I was building. Also I've started using MOOSE for mission design. To set a "baseline" I used OVGME to take a snapshot of my DCS directory. I'm pretty sure I ran a repair first, then snapshotted it, then installed the VR Shader mod back. The asset mod goes into Saved Games, so NBD.

 

Possibly because of that process, I'm not sure, I suddenly "lost" several modules. Ka-50, A10C were the first two I noticed. Not ALL modules, just some. Skate Zilla's app seemed to think I had them - I couldn't reinstall them via that utility, and trying to install them via DCS would exit DCS but not fire up the updater. So I used the command-line for DCSUpdater.exe to reinstall those modules. It was all very strange.

 

It seems to be *after this*, that VAICOM started giving me the flickering menus. The reinstallation of the mods didn't make sense to me as a cause, so I figure it was whatever corrupted things so I "lost" those modules. I don't have any idea what that was, but COULD have been the repair. I don't think so - I'm pretty sure I was playing in the A10 after that last repair. I THINK I was playing the A10 one night, logged on the next night to work on my mission, and noticed I couldn't add a flyable a10 to the mission ... thought it was a quirk of the mission editor, then later realised DCS didn't think I HAD the a10.

 

ARE YOU STILL WITH ME!?

 

Ok, so what now? As you might be able to tell, I'm desparately trying to avoid big reinstalls. I've frankly found VAICOM quite frustrating and there have been so many little tweaks and changes that I can't remember to make it all work acceptably, I'm loathe to reinstall even the app - let alone Voice Attack, or god-forbid DCS.

 

So if I can't get a fairly easy solution, I'll probably just stop using VAICOM. I have more and more resorted to just using it for "Options > Take 1/2/3" anyway. I disabled AIRRIO because using the Jester menu was so much simpler and I couldn't have both. I also really need to reformat and repartition at some point (a chore I've been delayed....) so if it looks like a massive reinstall is in order, I'll probably just give up and revisit after i wipe my whole computer and start again.

 

So, to summarise .... any silver bullets anyone can see that could get me back on track so I don't have to shelve VAICOM until I reformat some point in the future?

[dakuth]

If you've seen my other post, you may think I have given up and don't need help. If anyone is willing if give me suggestions here, I'm willing to try and work it out.

 

Of course, if we're out of ideas I'll just wait for my reformat and try again then.

[Greyman]

Have you seen this FAQ post by @Hollywood_315?

 

https://forums.eagle.ru/showpost.php?p=4311067&postcount=5

 

There are some of your symptoms covered on there and hopefully the associated solutions will work for you.

[hornblower793]

We are more than willing to try and help.

 

 

Just as a thought, it might be worth trying to tick the OB box if yours is a converted Steam install as i know that some Steam users have reported success doing this

 

 

 

If the pointers in the FAQ don't work then it might be worth contacting Hollywood directly (either a PM on these forums or e-mail to support@vaicompro.com).

 

 

It might also be worth attaching screenshots of your VAICOM config screens to a post here (along with the lua files that have been updated) so we can take a look.