Greyman

Do the IFLOLS on the ship and the recently added overlay disagree or are they both wrong?

Perhaps if you asked for help on the Vaicom Pro subforum, https://forums.eagle.ru/forumdisplay.php?f=733, you might have more chance to get it working. I see that you have posted on that forum today, for the first time, but with no indication of the problems you are apparently stating here. MS Speech recognition, which is required by VoiceAttack and thus Vaicom Pro, does require a fairly significant investment of time, to get it to understand your voice and to suggest that it must be bugged because you have yet to ask why it doesn't, is hardly fair.

asymmetric load?

Thanks for that. So might that explain the apparent inaccuracy that peeps are experiencing? For example, if the IFLOLS is set for an F18 and the aircraft landing is an F14?

after a DCS update, it is the export.lua that sits beneath the Saved Games branch that you should delete and no others, if you aren't seeing the module name in the PTT window. A restart of VA and, probably DCS, should then correct the problem.

Is it like this on both the F18 and F14, I only have the former, or is there a difference between the two? Would the IFLOLS be set the same for each of those aircraft?

It works great with the F18.

Vaicom is focused on the voice operation of the radio communications system, which you are very likely to struggle to do with just VoiceAttack. There is a free version, which although not fully featured, will give you a good idea of what it is capable of. Maybe give that a go.

and you have added "decimal" to the dictionary and recorded your pronunciation of it? If it still recognises that as ".", maybe record yourself saying "point". If that returns "point" then just block that, so that "decimal" is returned.

can you block recognition of "." in the MS speech recognition dictionary, hopefully forcing it to recognise "decimal"?

does turning off easy comms make it work any better?

but have you tried "carrier, select"? The select command should make your target carrier the unambiguous target of subsequent radio messages

I'm not sure it was the same question, but the one you did raise was about being diverted to the alternate airfield, when declaring inbound. When Easy Comms is enabled, the inbound call will be sent to the nearest ship, which would probably have been one of the support vessels that effectively create a ring around the carrier. As those support vessels cannot accept the recovery of an F14 or F18, they will automatically send you to the alternate field. Also, the fact that Vaicom thinks you have selected a ship that isn't a carrier, might also explain why none of the other calls would work. Maybe try saying "carrier, select" or "<carrier name>, Select", as appropriate, and then say "inbound".

It'll probably be Easycomms selecting the nearest tanker, Arco in your example. Try "Shell, Select" before "approaching to refuel" and see if that has the desired effect.

but shouldn't "kiss off" be stated to your flight and not the carrier?

You might want to ask the dev, but I'd expect that you should be OK, as long as you don't try to use the graphics enhancements of both mods together. Maybe just give it a try. Personally, I've now done loads of JTAC missions using the copy/paste bit that i would never have been able to do, without taking off my headset and writing the coords down.

https://forums.eagle.ru/showthread.php?t=242134&highlight=jtac+copy+paste contains a really useful feature for, as well as any message, keeping the 9-line on screen. If you fly the F18, you can also combine that with the coordinate conversion mod, at https://forums.eagle.ru/showthread.php?t=228750&highlight=jtac+coordinates

Maybe check your anti-virus software, to make sure that the missing file has not been quarantined

According to Chuck's Guide, it's in the centre of the Pilot's HSD and is the bottom number.

https://forums.eagle.ru/showpost.php?p=4311067&postcount=5 Read what the linked FAQ says about "blinking menus", as that appears to be the issue you are experiencing. The fix will probably also fix your apparently reversed disable menus option.

That option had to be provided, mainly for TM WH HOTAS users. The TDC control on the Warthog throttle didn't like to be pushed and moved around at the same time, so this option makes it behave like the one in the A10C module.

also, as per the FAQ, for general unexpected behaviour, make sure you are still running VA as admin and that you don't have any Garmin mods activated in DCS.

If that doesn't help you, if you Google "Windows 10 speech recognition won't work", there appear to be a fair few people that have had what look like similar issues and there are quite a few suggested and apparently successful fixes.

What if you type "speech recognition" into the Windows 10 search box and then select the app that results in? Hmmm, https://answers.microsoft.com/en-us/windows/forum/all/windows-10-speech-recognition-wont-start/ec6c690c-8486-4179-b6f2-929070231d9c might be worth a look.

I'm fairly sure that VP doesn't send anything to DCS until it detects the PTT being released.