Greyman

The way I understand the function of VAICOM Pro is that it predominantly covers the conversation bit of radio/intercom comms. With the F14 having a "back seat driver"/RIO VP also now covers the conversations with them and as it is the RIO who tunes the radio, the commands you are talking about were added. The AIRIO commands are there to replace the command wheel that the F14 exclusively uses. I don't yet have AIRIO, but I wouldn't expect that it would work with any other modules.

Ah, sweet. That's now how it works on the A10c, after the latch has been set, but I'd be a little concerned about damaging someone's eyesight with the laser. ;)

the Pitot Heat switch is just next to the pilot's right knee IIRC or their thigh if not. :)

I suspect that the implications of not heeding such warnings would be modelled as part of the failure system, which I hope will be added at some point before the end of EA

It's not latched, so the target is illuminated for as long as you hold the trigger in

Maybe check that you don't have any other mappings on another device, for the gun select, that might be conflicting with the stick button. I've found some odd unwanted button mappings in the past, even on my rudder pedals.

Make sure that your toe brakes have the correct setting in the axis invert checkboxes and that they have been properly calibrated. It might also be worth checking that you are getting the full range on your throttle levers.

Hollywood will need to confirm, but I am fairly sure that VAICOM Pro is the only supported version now. So that we have a little more information on what it isn't doing that it should or what it is doing that it shouldn't could you expand a little. If VA is working that might suggest that it is recognising at least some of the commands, but is not passing them over to DCS. Maybe worth a try are a) make sure VA is running as Administrator and b) delete the export.lua file, in the scripts folder under your Saved Games/DCS folder and then restart DCS and VoiceAttack. Edit: maybe also check out the FAQs page at https://www.vaicompro.com/faq.html. Among other useful information are a couple of links to YouTube vids that might be of interest.

Watching or re-watching this one might help As Wags is setting up the LGB, you can see the "DUD" and the cross over CCIP disappear as he sets the efuse to instantaneous and the laser code respectively.

Probably most useful for cold and dark starts in the middle of the night, when you can't find the battery switch, for example. once it is on, the light shines where you point your mouse.

https://deltasimelectronics.com/products/thumbstick-slew-sensor-adapter would be definitely worth a look, albeit perhaps not overly attractive for a newly purchased device. I've had my WH for around 3 years now and this mod has given the throttle's slew control a totally new lease of life.

Sweet. I'll look forward to that. It does sound like a more efficient way of dropping the bombs. Setting them up with target coordinates will still take a while, which is fine, but dropping them should be just require repeated presses of the pickle button.

I think that he explains in his commentary, that it is the aircraft software locking on to bits of the ground and with the display being zoomed right in, any such system generated movements will be exaggerated. The slew works just fine.

the mission has all 4 targets within pretty close proximity and after programming the coordinates of each of those targets into one of my 4 bombs, i simply pickled all of the bombs at the same time. i would just have expected that the target coordinates would have been transferred directly into the circuitry of the bombs themselves, which would mean that they would each be targeted at a specific target, regardless of how and when you drop them. From their behaviour, it would appear that the coordinates are only transferred to the bomb at the point of release, oh well, live and learn i guess

hmmm, it looks like i should have followed @Bones1775's guidance a little more closely as even though i thought i'd programmed each bomb with a different set of coordinates, not selecting PP2 after the dropping the first pair, causes the bombs to hit just two targets. That seems odd if the 4 bombs themselves had been programmed with independent coordinates. the pylon must be what gets programmed and the target coordinates transferred to the bomb just before release. Edit: i've saved the track, just in case anyone might be interested. ;)

It looks like there are some PP buttons along the top of the JDAM display and it appears as though they might still work, even though they are crossed out. I'll give it a try Edit: sweet, it looks like the crosses disappear when the target coords have been input. now to see how they deploy

i am in PP mode, but i am looking for a way to toggle between two bombs on the same pylon, to enter the coordinates of two distinct targets. it sounds like there is a way of doing it, but as it stands, i am only able to program one bomb per pylon.

i've apparently missed something and having gone back into the mission i have been trying to do, i cannot find anything that looks like PB1 or PB2. Could you please give me a clue where i might find them or where i might find some instruction as to how to program and use multiple bombs on a smaller number of pylons?

so if you have a pair of JDAMs on each of two pylons, stations 2 and 8 for example, and have 4 targets to hit, how are you supposed to set different target coordinates for each bomb? the QTY command only appears to allow the two stations to be selected and the resulting STEPs only appear to toggle between two weapons. or, despite having a qty of 2, does it still allow you to program all 4 bombs? Otherwise, do you need to do one pass to attack the first 2 targets and then reprogram the remaining two bombs with the coords for the final 2 targets?

ah sorry, it's just an abbreviation for VAICOM Pro that i use. It also saves me from falling into the trap of calling it "VIACOM Pro". as many appear to do. :)

I don't think it will. The J-11A is not an aircraft i have flown before, so i thought i'd give it a try and although VP does suggest that it supports the aircraft, i am not overly sure that the ATC commands work with or without VP. As you say, the SU-27 works fine, albeit with, for me at least, illegible Russian responses, but there doesn't appear to be anything behind the ATC bit of the comms menu for the J-11A. I can get the ground crew to respond, but ATC does not appear to answer, even though DCS does appear to have actioned the command. I wonder if the Chinese assets have been installed properly by the update that added the J-11A? As you have also posted this issue in the ED part of the forum, you might get more joy from ED or from someone else that has experienced a similar issue. Edit: ah, sorry, was testing it out and hadn't checked whether you had posted again. It might be that the module only works with easycomms, as may be the case for the FC3 aircraft, with no radio tuning available. I'll try switching easycomms on alongside VP and see if that works. Nope, that doesn't appear to work either, but then again, i can't seem to get it working with VP off either. sorry

It might seem like a stock answer, but have you tried deleting the export.lua file, under saved games/DCS world/scripts? You will need to restart DCS and VoiceAttack after deleting the file. The switch from stable to open beta might have "confused" something.

With my 56-year-old eyesight and clunking great fingers, I struggled with the same issue, but was lucky enough to have a rather adept son, importantly with far less chubby fingers and better eyesight, to do the deed. The upgrade works wonderfully well and I'd recommend that you try to find someone with the necessary physical attributes to get the old sensor out and the new one in, before giving up.

Maybe check that your mic is still working and that it is still properly configured in VA. Also worth checking, I have to unplug my headphones, when using VA, as its mic tends to trump the mic on my Rift, which is the one that is set for VA. Edit: oh and just in case you have recently updated DCS, delete the export.lua file, in your saved games/DCS/scripts folder and reload DCS and VA/VP.

If you have recently updated it, then make sure that it is still running as admin. If it isn't loading or crashing, what messages does it give?