oz555

I have an issue with the initial calibration on my Reverb, just before the cliff house loads up. The "look left, right, down" feature sometimes appears, sometimes not and sometimes just for a brief moment. The quality of the tracking from then on seems to depend on how much time was allowed during this calibration. The reliability of the calibration window appearing at all seems totally random. I've tried multiple re-installs of WMR and also with and without the auto/manual switch sensor option. Any ideas what may be up?

I get the same sort of thing in the MP server list. Can be quite nauseating.

Right, may have sorted it. I assumed the feature had been dropped or was temporary, so after a bit of fiddling I swapped the input sensor setting from manually switch to automatic (default). I now get the calibration page on WMR startup. Odd eh. Cheers

I have similar issues to OP. When you say "do the moves" I assume you mean the look left, down, up request. That seems to be a missing feature now on my Mixed Reality. It was there when I first installed and was also there initially when I re-installed twice. I also notice that if I create a boundary, it's usually not there after a re-boot. Any suggestions?

I have also had some major issues with the MFD getting stuck in a blank INS screen. This usually happens when slaving to MKP or WP. Process I have been using on right MFD- Select desired WP, check not in FLIR mode, check slave is selected, press DESG. This process initially works just fine and will slave the TGP to my target, but after repeating a few times, when designating, the TGP will switch to INS or some times DMT instead of slaving the pod. Often this will result in a locked INS MFD screen that will not respond to any input at all. I'm not even going to go into the LSS mode function......

+1

Just found this. DCS 3080 demo No DCS settings listed unfortunately.

I was unhappy with the overall quality of the new Harrier sound engine, particularly on start up following the igniters/off throttle stop. I reverted to this great mod from CPT. Creosote. https://www.digitalcombatsimulator.com/en/files/3300537/ I was happy to find out that the Razbam spool down sounds and igniters were retained. I assume it's a separate sound file.

I was unhappy with the overall quality of the new Harrier sound engine, particularly on start up following the igniters. I reverted to this great mod from CPT. Creosote. I was surprised and happy to find out that the Razbam spool down sounds were retained. I assume it's a separate sound file as they cannot be heard in F2 or other Harriers.

I just tried and couldn't reproduce it. All seems to work fine for a short time and then all sorts of things go wrong. It's way over my head now and sapping my time, so I've uninstalled the lot. I'll re-visit at some point as it's great when it works. Cheers

I fly AV8B and yes, I do use the select command a lot and it may well be the case that things go downhill from that command onward. Have now un-installed and re-Installed numerous times, configured, researched. I'm done with it for now, Cheers anyway.

Hate to be back pestering, but here we go. Everything works fine when I boot up DCS, but during the flight Viacom commands stop responding and the program seems to accumulate a huge delay. I get no confirmation beep or commands appearing in VA and it gets to the point where I keep trying commands and eventually, maybe 30-40 seconds later I get a beep and a string of gobbledegook commands in the VA window.

I didn't convert no, I downloaded Open Beta and used my old saved games stable folder for the settings.

I had checked open beta in config as I'm running open beta. I did just switch it to release following the resets and it's working now. So a result I think albeit with some odd DCS folder issues. Again, thanks a million. Fingers crossed I won't be back soon...

Just followed those steps and no joy I'm afraid. It just creates a separate open beta file again and ignores my DCS saved games file.

Vaicom is working just fine on it's own. It just won't interact with DCS as it creates the export.lua in a separate open beta file. I'm guessing due to DCS not being in the registry.

I don't have DCS actually Installed within Windows. Since I did the new Windows Install, I just run it straight from the exe on my SSD.

So I'm still having issues with my Install. When VA/Vaicom is opened it creates the DCS Openbeta file in my saved games which contains the export lua. Problem is, my DCS saved games is just called DCS, not DCS open beta. If I remove my DCS saved games file and launch the sim, a new one is created, but It's just called DCS. How do I get Vaicom to drop the correct files in my DCS saved games instead of creating a new Open beta file?

Think you may have nailed it. Just found a new DCS Open Beta file in Saved games.......Must have automatically created one after the Windows re-install. The Vaicom LUA is there. Should be able to work it from here. Will get back if not. Thanks both for your help.

No luck unfortunately. Tried re-naming and deleting the Export lua. Started VA, it says Viacom 2.5 pro initialised, but no new lua in the scripts folder.

Checked and done. This didn't add anything to my export lua.

Appreciated. Thanks.

The run in debug mode was already ticked and does nothing when I uncheck/re-check it in the VA window. I have dropped the AIRIO d11 into the extensions folder alongside Chatter and then tried importing the commands through the edit profile in VA. However, when I point VA to the extensions folder it is empty. Chatter and AIRIO are there if I access it through My Computer though. My scripts Export lua below if relevant. local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') dofile(lfs.writedir()..[[scripts\SimShaker-export-core\ExportCore.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

I'm still getting nowhere with this. I have run repairs on DCS, uninstalled Vaicom, reset luas etc. I cannot get Vaicom to communicate with DCS. I installed aerio, although I cannot import the commands through VA.

Just tried it too. No joy.