VirusAM

Bravo Andrew [emoji122] Sarò di parte ormai...ma concordo perfettamente

Beh la open beta, per chi se lo ricorda, era nata esattamente con questo scopo. Ma nessuno (o pochi) ha voglia di mettersi a fare prove, creare tracks...uploadare logs scrivere dei report dettagliati... E poi...Un po’ per colpa di tutti è diventata la release di fatto... Noi che vogliamo i nuovi giocattoli.... I server più importanti sono solo su OpenBeta La ED che ovviamente rilascia prima su Open Beta (in realtà cosa giusta concettualmente...ma accentua il problema)

Are you sure your lss laser code matches the jtac one? it is better if you switch off the hornet own laser. Also did you follow all the steps with the JTAC? You should “tell” him to lase with the “laser on” radio command

Unfortunately not...I already tought of that, but it doesn’t accept special characters or phrases..only single words

Yes i know all that.. But vaicomm needs to identify in a very specific way what i am saying for it to work... For example 225.0 need to be recognized as 250 decimal 0 (instead of 225.0) Or ‘tacan tune yankee 074’ needs to be recognized as ‘tacan tune yankee 0 7 4’ (0 7 4 instead of 074). If not it won’t recognize as a command included in the profile. So for me the culprit resides there... The thing that makes my computer recognize decimal as the . Is the first issue. I don’t want to retrain again every thing so I don’t want to switch profiles (i did already once without results).

Hi.... I had the warthog throttle before and what i did with it was using "cummunity curves" for every plane (there is a thread on this somewhere).... With the winwing throttle you just calibrate afterburner and in DCS magically you have the detents lined up for every plane...or at least the ones i tried (Hornet, F16 and F14). I don't know what is happening under the hood but i do suspect that winwing software is doing some scripting with DCS

VAICOMM/AIRIO - problems with recognizing some functions I tried almost everything... I tried to use VSPX...and it is worse. I tried to use UK speech engine instead of US and it is worse (probably because i need to redo all the training). in my image you can see (note that for easier recognition i changed 'radio tune' to 'radio change' and 'tacan tune' to 'tacan change'): if i say "radio change 225 decimal zero" then "radio change 225.0" is recognized but VAICOM report it as 'unrecognized' if i say "radio change 225 decimal oh" then "radio change 225. 'O' " is recognized but VAICOM report it as 'unrecognized' if i say "tacan change yankee 074" then "tacan change yankee 074" is recognized but nothing happens in the SIM and VAICOM report it as 'unrecognized'. With link tune happens the same. There is no way i am able to make x-ray being recognized (and i also recorded my pronouncation of it). If i say "decimal" alone...the speech engine correctly recognizes the 'decimal' and not the point. So i don't see this as my fault, or my pronunciation fault. Also in the image you can see that if i use the standard VAICOMM commands "select Washington" "Link host Stennis" and "Tacan Tune Texaco" they work flawless. The last resort for me is to try to record every radio frequency combination in the windows speech dictionary... So I do insist that VAICOMM, and particularly AIRIO special commands, have an issue on my particular computer. Maybe some language settings, maybe some errors of mine in the configuration (but i did RTFM) but definitely not my speech recognition. I demonstrated that with all the screenshots i uploaded. Also i did as Hollywood asked (reset everything and deleted the folders he indicated) but nothing was solved. So please could Hollywood try to understand what is wrong? This is not a free mod....I paid for it...in 3 years (since i bought VAICOMM) i never asked anything, but now that i am using AIRIO (bought last year but really started using just couple of weeks ago) and the supercarrier extension, I pretend the support from the developer in helping me solving these issues. I sent also an email describing this issue to the official support email but didn't receive any answer. This lacking of support, and the "bored" answers by Hollywood really make me upset, more then the fact that I am not able to use a paid product. Edit: i did another picture hoping you all can see it better

Well as I wrote above it is required also for having the backlighting and apu light sync with the simulation

Ok thanks... As i was seeing others posting good pictures of it, I thought just that was me doing something wrong or missing some configuration

Vabbè lì sono stati proprio cretini....tanto hype per un aereo del cavolo che per carità può anche avere il suo perché ed essere interessante...ma è bel lontano dal generare quel tipo di hype

VAICOMM/AIRIO - problems with recognizing some functions Thanks hornblower...but i am very sad...this didn’t solve my issue.... I really don’t know what you do. In the screenshot here you can see that i have not any issue with the recognition... Is this damn decimal that will always be recognized as a . You will see the difference when I pronounce ‘decimal zero’, and ‘decimal oh’. You can also see that the word decimal alone is recognized without issues. Also since Hollywood told me to reset everything i am not able to make it work also tacan tune (change for me) yankee ‘xxx’ that before and link tune that before were working As you can see the airio commands are inserted in the profile, but it seems as if these 3 AIRIO special commands will never work (radio tune, tacan tune, link tune). The map marker and scan altitude range are only ones working. Strangely enough tacan tune texaco or link tune stennis (examples) both works well...mysteries.... I hope Hollywood will be able to figure out what is happening.

Here is an image of what i described above

You need to have the software running only if you wish to synchronize panel backlighting and APU light with the DCS Hornet. I disabled it, as the winwing export scripts are causing cpu load issues for me. Anyway with just the software installed you can change the behavior of some axis/buttons and calibrate the throttle afterburner to be at the correct level for DCS planes. But after doing all your configuration you can keep the software closed and you won't lose any functionality.

I ask to you also then... In order to work did you change from 0 to 'o' letter in VAICOMM profile or without changing anything just pronouncing the 0 as 'oh' works out of the box?

[emoji23]

The Channel Map by Eagle Dynamics Con dcs l’msaa nel pannello nvidia non viene rilevato...come dice blue se lo disattivi in game ed attivi nel pannello nvidia praticamente lo hai disattivato..con il deterred shading deve avere almeno un passaggio. Per cui se lo metti a 2x in game e metti su “enanche application settings” nel pannello nvidia...allora forse funziona. L’fxaa viene applicato sull’immagine finita quindi funziona. Io la differenza con uno schermo 3440x1440 la vedo parecchio....in VR ancora di più. Ad esempio guarda l’immagine negli specchietti ed i bordi del cockpit. Poi occhio che per alcuni settaggi devi riavviare DCS...l’AA è uno di quelli e non lo fa lui in automatico.

No I think it is a bug...absolutely not normal. Good catch anyway

Ok, i will definitely need to try this then... but did you change the 0 to 'o' in the VAICOMM profile...or it is just recognized this way if you pronounce as 'oh'?

I tried UK engine but the recognition is way worse then US one...I guess i need to retrain the speech engine? I hope not

Hello, I have some stopping issues with VAICOMM and AIRIO described here: https://forums.eagle.ru/showthread.php?t=275397 But i would like to make another post to keep it separate for smaller non blocking issues that i would like to solve (if possible). - Issues with the SuperCarrier module First issue is that the Supercarrier recipients are not recognized when using the select commands, or the link and tacan tune with AIRIO. I try to explain better.....if in a mission there is a tanker (example Texaco), an Awacs (ex. Focus) and a Supercarrier (ex. the Lincoln)... If i say Tacan tune: The dialog says that available units are the tanker and the awacs but the supercarrier is not listed. So if i say "tacan tune texaco" it works, but not for the carrier...so "tacan tune Lincoln" or "select Lincoln" does not work as the unit is not recognized. Same with the Link host command (it gives me only the Awacs in this case), while if in a similar mission i have the regular stennis, it shows in the AIRIO dialog and works when saying for example "link host stennis". The same happens with the select command, so i am not able to switch radio frequency using this command to a Supercarrier unit. In the Hornet these are not big issues as I can change the radio and tacan frequencies easily with the UFC and the Datalink works out of the box. In the Tomcat, having big issues with AIRIO tacan, link and radio tune commands (described in the other thread linked above) it is a problem as I cannot tune the main radio and the datalink from the front-seat. Other then that the Supercarrier addon works quite well as I am able to contact marshall, and do all the steps (given that I am on the correct frequency of course), so the SC addon is activated in the options and working...Is there something else that I need to do?? I have the options in VAICOMM dialog to automatically import new theatres and modules (for example in the VAICOMM logs i saw the Burke added as ATC) - Small issue with VAICOMM trying to interpret my voice before I stop talking and release the tx button Sometimes with longer commands also if I don't stop talking and don't release the KEY for TX VAICOMM recognize (wrong) partial commands. So I think it should wait for me to stop, or release the button to start interpreting what i said. Is there an option to improve this? Thanks

Yeah probably it would need more digging in the target.h file.... As i fly mainly VR, i don't think I am going to lose my sleep on this one...

Ti consiglio di guardare il suo sito...flyandwire... non passa spesso dal forum ita.....

Sure i will send you immediately. Thanks

I am having issues with this....hosted (for only myself) on my local server... After a while the Carrier ends to be on the ground. And also when using the spawn options (redkite scripts integrated in f10 menu) for the deck...the spawned aircraft are drowned in the deck. I will post screenshots of both issues later, when will come back home later. But in the meantime I would like to know if someone else experienced this. Thanks

I don't know...I had this thought this this morning while going to work.... Definitely will be the first time I will try this afternoon when back home.