honeycool75

I'm trying out CCRP for the first time today. I did the following: 1. Select bomb 2. Radar on and Alt on 3. Select TAS and RS 4. Set fuse to instant 5. Designate the target 6. Master arm on When the horizontal line move upward and passes thru, press and hold trigger. However, the bomb won't release. Did I miss a step? P/S: I've no problem with CCIP bomb release.

Is there a user created mission downloadable from the web to test out Mirage GBU whereby the target is lased by AI? Thanks.

Since the Mirage is without a targeting pod, how do we go about buddy lasing? I watch a few videos where to enable CCRP, the pilot will have to manually designate the target while your buddy is supposedly lasing. This not like the Harrier where there's a function to scan for lased targets. My point is, how do we coordinate the effort, i.e. manual designate the correct target that is currently lased? There's a lot going on during a mission. Hope to get some pointers here.

With regards to the NVG, I'm aware 2 ways of loading the case into the Mirage, ground crew or mission editor. On a few occasions during MP missions, I requested the ground crew to load the case, the crew complied and confirmed. However, the case was missing. Has anyone experienced this problem?

About the vaicom editor keyword training mode and after the recent update v2.5.20, simple keywords such as vector and tanker which used to be easily recognized, are no longer working. During the keyword training session, the ms voice recognition will request to "spell it" if it can't understand my pronunciation. So, I spelled it and the "Finish" button gets to light up. If I click on that button, it will export to a file. Questions: 1. The keyword "vector" is not found in the editor list, was it ever been there before? 2. Does the keyword training store the outcome, i.e. the user's individual pronunciation somewhere so that it could recognize from now on after the training session? It appears the experience are kinda of erratic for me. 3. Clicking the "Finish" button, exporting to a file, what will I do with that file?

I noticed the Mirage easily gets stuck on the ground or grass, e.g. if I accidentally roll off from the asphalt into the sand. 99% of the time afterburner won't help to get the plane moving. Is this realistic?

From your explanation, it means the WP has to be within the radar line of sight arc, something I never thought of.

To add waypoint into the radar scope, I will do this -> Prep -> <waypoint no> -> val However, I've to do this multiple times to get it work and at times it won't. Is anyone else getting this problem?

I am on latest open beta. Is the Mirage radar that weak?

I was practising Mirage BVR using the stock SP Caucasus destroy F16s AI mission. Attempted 4 times, PID/TWS won't see any blip even the bandits were 40nm dead ahead, moving the radar antenna up down doesn't seem to have any effect. Later, I tried BVR by creating a fast mission, TWS worked. Any comment?

Please refer to the attachment, I have a clean startup without any warning lights. While the plane is on the ground, if I'd mess around by intentionally changing the FBW Gain to something incorrect and change it back to normal, several warning lights will appear, MAN/DOM/BECS. These warning lights will stay on forever even though I reverted the changes back to original. Is this expected by design or a bug?

How about voiceattack, anything to reconfigure? Thanks.

I am planning to move my DCS to another drive location. May I ask whether there are manual steps to perform without having to reinstall/reconfigure both VA and Vaicom?

Hi MAXsenna and Hornblower793 Easy communication off issue resolved with select tune radio untick/off. Indeed the F18 most likely doesn't like freq 71.000 Btw, does vaicom work with Mirage 2000, thinking of getting this module while the sale's on? Thanks so much for all your help.

Yes, I use SRS and pretty familiar with F18 radio operation. :) Tried every single thing I know of but still no joy with Vaicom easy communication off. Try replicating my steps, let me know the outcome.

Sorry, I missed mentioning another step before saying command: AWACS. I did change to another frequency before that. Thanks for pointing out. Please replicate my steps, I've also attached a link to the mission that was used in an earlier reply to MAXsenna.

Hi MAXsenna, I tested both Easy Comm ON/OFF scenarios using this mission available here: https://www.digitalcombatsimulator.com/upload/iblock/8ef/Persian%20Gulf%20FA-18%20Strike%20Fighter%20(Full%20Mission).miz

Hi Hollywood, I've read the user manual, many times since :) With Easy Communication = OFF and Select Tunes Radio = ON, using commands like example "Batumi,..Select" is all along working fine, at least for me, there's no issue from my end. ---- My problem is not the above but rather using Easy Communication = OFF, Select Tunes Radio = OFF and manual freq tuning to communicate with AI. Please replicate this example in your DCS: 1. In DCS options, set Easy Communication = OFF 2. Ensure Select Tunes Radio = OFF (Untick) 3. Use F-18, start any mission that has crystal palace or JTAC or AWACS available. 4. Using Comm1, either "M" or Channel "1", tune to freq 71.000 5. Say command: crystal palace,..interrogate [VA recognizes the command and statement but no response from AI] 6. Say command: AWACS,..request vector to tanker [VA recognizes the command and statement but no response from AI] 7. Get out from the mission, in DCS options, set Easy Communication = ON 8. Ensure Select Tunes Radio = OFF 9. Repeat step #3 10. Repeat step #5 for crystal palace [VA recognizes the command and statement, AI responses perfectly well] 11. Repeat step #6 for AWACS [VA recognizes the command and statement, AI responses perfectly well] To be fair in the testing, I did this in a controlled manner, where my plane was just sitting on the carrier deck, in the very same mission. Thanks.

Glad you were able to replicate the issue. The select tunes option does get the correct frequency like Easy Communication ON but without response from AI. Wonder if this could be a bug, this is just my 3rd day with Vaicom?

Yes, the VA window did recognize the command with a green indicator. Similarly to when Easy Communication set to ON. The only thing I don't get is the response from AI. Immediately switching back to Easy Communication to ON, the command works fine. That's what puzzles me.

For 71.000, I think it doesn't have a selection for AM and FM.

Had to reupload the same log file in .txt, without the highlights. VAICOMPRO-log.txt

I've attached the logs from debug. Sections highlighted in "RED" was from Easy Communication = OFF while the "GREEN" is after switching Easy Communication = ON. Thanks for helping to take a look.

I'm in F18, the command used: Easy Communication = OFF Manually tune to 71.000 in Comm 1 "M" Select Tunes Radio = Untick Then say > crystal palace interrogate Nothing happens, no response from AI After changing back to Easy Communication = ON, all works fine with the same freq and command. :(

I untick/turned off "Easy Communication" in the options in DCS. Next, Vaicom configuration preference, I enable "Select Tunes Radio". In the game, I tune to the correct frequency, e.g. COMM1 Channel "M" with ATC frequency. I can hear my player request, i.e. startup. But no response from AI ATC. If you see my screenshot, the command was recognized. So, has anyone using "Easy Communication = OFF", how does it work with Vaicom? Thanks.