Tic-Tac

in case anyone is interested, I tracked down the cause and solved the lack of 'chatter' problem. The path to the .aac files is hardcoded into the profile, so it's only a problem if you've installed Voice attack anywhere but default C drive. Easiest way to fix is to find each instance of 'C:\Program Files (x86)\VoiceAttack\Apps\VAICOM' in the profile and 'replace all' the path up to 'VAICOM' with {VA_APPS}, so all after edit each line should read <Location>{VA_APPS}\VAICOM\Sounds\Chatter\XXX.aac</Location>, where XXX is the name of each .ACC file. Works for me but back up first just in case, that means export your current profile (with joystick set up etc) not just save the file with a different name.

Final part of the jigsaw (I hope!), if I enable 'chatter' I get following error in voice attack window (all other functionality continues to work as expected) Sound initialization timeout: C:\Program Files (x86)\VoiceAttack\Apps\VAICOM\Sounds\Chatter\2014-07-24_14-38-46.aac Any ideas? (I'm on Windows 10)

Correct RSBN channels for all airfields are in the Mig-21 manual

thanks for the tips! Seems my problem might have been/was a combo of the non US keyboard '\' issue and a conflict with F keys from my TrackIR...seem to be on my way now, at least A10C start up, taxi and clear for take off!

Thanks for the response, as long as I know someone else has it working...back to the trouble shooting!

Am having problems getting ATC to respond to requests using VAICOM profile and Voice Attack, even though the commands seem to be recognized. I am using the latest DCS 1.5 beta and noticed the static ATC plugin needed for VAICOM does not seem to work with 1.5 as highlighted by the author (https://forums.eagle.ru/showthread.php?t=138994). Does this mean VAICOM will not work with 1.5? anyone have it working?

To make TGP SOI it needs to be active, using the MFD soft key on top row of the right MFD, either A-G or A-A, not just switched on with the toggle switch...maybe that's the problem ?

I see the same issue in 2.0 Alpha

it's the same web site for support...

Didn't work for me straight away either. here's the troubleshooting I did (none of it my own invention, all tips from the internet!) 1) Add Ipad IP to Export.lua file (just IP not the port) and save to user saved games Script - if you get this right you should at least see the in game CDU display reflected on your ipad version - if this isn't the case then the ip is wrong or lua is saved in the wrong place 2) Firewall - make sure the correct exe is allowed access through in Windows firewall settings and any other firewall you have st up, I pointed at the exe in the bin folder 3) Port forwarding - Not sure if this was 100% necessary, but went into my router settings, port forwarding and added port 9089 4) to get it started click on the pulsating CDU icon on the ipad...took me a few mins to work that bit out! and I think that was it...good luck

This might be old news to some (or even most!) but came across a free A10C CDU app for ipad, as far as I've tested works great with 2.0 Alpha, no additional PC software required (although there is some lua configuration) Also includes radios [ame] [/ame] thanks

in the mean time you could go here https://skyvector.com/ Click on 'charts' (globe icon) and choose Las Vegas sectional Not only gives you the beacons but if you click on the airports gives you detailed info, ...although not perfect as doesn't cover everything for military sites thanks

where's the option to 'point' tacview...that's what I'm missing

well spotted! good to know for sure... Training miz will need to be updated before official 1.5/2.0, but I'm sure they have that covered! [ATTACH]123393[/ATTACH]

not seen in the release notes for the update anywhere that the functionality would change from the previous version, but maybe I missed it...back to manual mode it is then.

previous version floated and could be used as a queue to where the bomb would land, 1.5 seems fixed, so the change is either a bug or a feature I think...but which...

I'm seeing the same problem, the piper should be visible during dive until your low enough to see where the bomb will land, given angle/speed. Did you report this as a bug yet? I couldn't see it..or is there another explanation?

The solution for me was to follow the instructions here http://forums.eagle.ru/showthread.php?t=114030 and then run the hotfix I think it's 9th screenhot down, example there is for sabre...but I replaced sabre with MIG-21BIS and used the path to my beta installation, see below Hope this helps! And remember to run the hotfix after...

problem solved...used the command line option to install into 1.5 and has done the trick...

Hi, wonder if anyone else is getting this...Mig21 module seems to have copied over to 1.5 but when I launch any mission I'm sitting in an invisible plane, external views are fine, just F1 view I have a couple of instrument knobs and that's it... I've reinstalled beta, reinstalled the module into the production version, run the hotfix and tried manually copying the Mig21 folder from Mods/Aircraft in production to same location in Beta but no difference. All other modules seem fine (eg sabre, Mig15) Any ideas out there? thanks!

I know this was listed a s a bug early on, when changing NDB frequencies on the nav radio you get a combination of previous and new morse code signatures coming through, but I thought I'd seen somewhere is had been fixed, only I still get the problem...anyone heard anything about a fix? thanks!