E61-v1T1

Yes, I confirm that it is fixed in the last Beta. Thank you :thumbup: :pilotfly:

To prevent don’t change Azimuth or Elevation in TWS mode ... You must let RIO have complete control in this mode... Once the bug has started, you can not do anything else, just wait, sometimes it stops after a few minutes, others you must change slot or plane.

ACM Mode and any STT Lock. In others words ..., this bug neutralizes the radar completely.. you can still launch your Phoenix in TWS Automatic , that’s all.

You're welcome, The bug persists in 726 :thumbup:

All your "Unrecognized" commands are perfectly valid, because they do not belong to the profile. If you say something there's not in the profile you get Yellow "Unrecognized" You must understand that the correct function of the VAICOM Plugins also depends on two extremely complex platforms, 1: Windows 10, Speech recognition (Windows version, installation, drivers, etc..) and 2: VoiceAttack. In my opinion you are having problems with these last two, this is where you should find a solution. You can also try to change your Speech Profile..., go to Windows Control Panel\Ease of Access\Speech Recognition , then click in Advanced speech options, there you can change your profile, or make a new or delete. Greetings

Hello; I come back with more tests, this time I have made a small video so you can see exactly what happens and what steps I am doing. Always in multiplayer. Interactions with RIO are made at the following times: 00:15 (trying STT Lock) 01:44 (Scan Center command) 02:17 (Radar Mode TWS command) 02:56 (Scan Center command) 04:10 (Launch Phoenix, Bug Start) Greetings

Your image is unreadable .. Have you tried changing the Speech Recognition?

Yes, sorry bad input, using "Break Lock" mapped in Hotas. I think yes, i was using STT too, But since then I have not had time to do more tests, I will do some more and come back with more details. Greetings

Is ok for me now, was the "o" pronunciation. Sorry. If i say "Radio Tune 124 decimal "o"25 works fine! @VirusAM, youo dont need to change nothing in profile, juste say "o" instead of "zero" Greetings

Hi, thanks for your support I have done all the recommended steps, but without results, the same problem remains.. "Radio Tune 1-9 decimal 1-9" It works very well From the moment I use "Decimal Zero" the problem persists.. It is important to emphasize that "Decimal" is recognized by the Speech independently, and "Zero" the same. So there's not a problem about Speech pronunciation or training.. I'm not saying it's a VAICOM Plugins problem. But some other conflict with the Speech reconigtion in Windows. At the beginning of having installed VAICOM, I wanted to use Speech Recongnition USA, but in this case "Radio Tune did not work at all, even doing the training. The I had the idea to uninstall USA and install Speech UK, and it was here when everything started working immediately, but with this "zero" problem...there is clearly a conflict somewhere, and it is not about pronunciation or training. For my part I have no more ideas... the only thing I have left is to continue using it in this way, and cross my fingers so that I am not forced to enter a frequency "decimal zero two five" Greetings

Ok, If you say "124 decimal o" works.. BUT, then try saying "124 decimal o25", what do you get? there's a problem for me.. This workaround works halfway, but is not the ideal solution.

:doh: I have no idea

Not related to the Mod. https://forums.eagle.ru/showthread.php?t=276609

Whell , sorry to say, this BUG still persistent in the last OB But not in the same way, 1- TWS M 2- Azimuth , Scan Elevation 3- Launch Phoenix (Aim-54A MK-60) Everything OK.., launch multiple PH Then used "Break Look" , and the bug returns immediately.. Multiplayer Conditions. :(

Have same problem, you must say only "251 decimal" and then you get 251.0 try it :thumbup:

You'r the boss :thumbup: Thanks!

Solved, back to Windows 10 1909...

Yes, I have done a clean installation of both VoiceAttack and VAICOM, and this problem persists. Maybe there's something i can do with Windows??, or need to wait next Windows Update?? Grettings

Is this BUG declared ? Steel happens in release version... I can’t shoot Phoenix en TWS mode auto, only in STT Lock mode, when this bug occurs the radar becomes useless Can I made a video for you if need it. Greetings

Correct

Oh thanks!! I have done some tests, and find for myself that these values are more natural: font_properties = {"DejaVuLGCSans.ttf", 5, 0, 0, 0} But you have to change alls alignments to CenterTop :thumbup:, dot is now more smalls and keep it in center. Thanks a lot GTFreeFlayer. :thumbup::thumbup:

HI guys, I am currently using this mod, and it seems a "must have" for any VR user. I have a question, does anyone know how to change the dot size at 4-3 km??, To make it a little more smaller. Thanks!

What about read the first post? :doh:

Hi. It is possible to obtain a "light" version of this mod ?. for example to recover the reflections and brightness of the sun in the canopy? Or is this essential to maintain performance???

Yes , I may not have explained myself correctly. Sorry for the Google Traduction.. This solved only my performance problem, ASW we know is broken, There's nothing to do, if it is not wait for a fix. :thumbup: