VirusAM

Unlikely... Dcs is mostly cpu bound in scenarios with many AI units and scripts going on... A new gpu won’t help there

Really nice idea..... I wonder if this can be replicated with an ipad someway... I hope the matric creator port it to iOS

You can use the command "Map Marker"...if you say "Map Marker 1 to Waypoint 1" Jester will use that f10 map marker and will input its coordinates in the Tomcat NAV system. You need to enable the AIRIO dialog extension for that to work. To place the markers on the map and label it I suggest to watch this:

Mamma mia ragazzi quanta gente si diverte a sparare cxxxxxe... Cmq ED dovrebbe fare la open beta solo dopo su richiesta e non liberamente scaricabile... Per accedervi devi accettare clausole precise... Ormai è l’unica per evitare questa gente lamentosa

I thought of something like that (replacing decimal with point or other words) or record every combination of frequency and tacan channel. Of course starting by one example to see if it will work. Thanks for all your help hornblower, really appreciated

Thanks for your reply. Yes I already wrote in some of the post above that I recorded it. Don’t worry i Know you guys are trying to help and can’t read a wall of text any time :) Today vaicomm support wrote me...and gave the blame on me that I corrupted the profile....i told them that i have done the reset twice...but they did ask it again...i did again (so 3rd time now) and no solution yet to this....so unless i corrupted a new profile it is not my fault... Anyway i discovered other quirks... For example “link decimal xx” command works well with every digit except with 0.. If i say “link decimal seventy” it is ok and works... If i say “link decimal zero” or “link decimal oh” then the result is an unrecognized “link 0.0”

Yes it is a known bug.. Transition between cases are still a little bit off...they don’t always work as intended. The SC is still WIP so we just need to wait a bit I guess :)

Once and forever, let me explan what OPEN BETA is meant for. Well my friend...you will get a big +1 by me... The last phrase especially is what I think.... The open beta/early access model is not meant for everyone... If you cannot accept blocking bugs...use the release and don’t complain in this way...do you want to help?report and provide tracks... For the ones who says that also the release has bugs...well software free of bugs doesn’t exist sorry... But if you do happen to find blocking bugs on the release...then you can be a bit more vocal (within the limits of good behaviors and kindness)...but i guess it is really difficult to have blocking bugs in the release. Then bigger servers that host big events...even the ones with prizes should be on the release... I don’t think there is a game out there were such kind of events are hosted on a beta branch...well because a beta is meant to be cutting edge and break things....

I think that all the main events and server should be on stable... Openbeta was born to help squashing bugs, but it became the new toys store for kids. Nothing wrong with this...all of us like the new toys...but then we get no guarantee that all will be working as intended. So openbeta can be used for testing and for playing with new features and modules...but then people should not complain this way as it is...well a beta.... Also I think that the 6 months between 2.5.5 and 2.5.6 on release are an exception for the complexity of that change...before usually 1 or 1 and half month was the timing between updates and I guess will be more like that in the next future

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.