lxsapper

https://forums.eagle.ru/showthread.php?t=263116&page=2

Unless I'm missing something because I don't have the M2000, what are you talking about? The F-14 does have Discrete commands for the Airbrakes. Default Keyboard commands LCtrl B and LShift B. The only thing it doens't do is stop the closing once initiated unless you repress open.

@Hollywood_315 Waistcat's confusion was from this page in the manual and he does have a point: This was not only present in 2017 versions of the manual (as he stated), but current version as well.

Ok then, Just trying to help. I for once find it strange. I got like everyone got the hang at 10% when DCS got updated to 2.5.6. But after Vaicom was updated it has been working like a charm for me and obviously others. The problem as much as I and others could tell was specifically caused by vaicom's altering of gameMessages.lua in ...\Eagle Dynamics\DCS World OpenBeta\Scripts\UI\ PS. This has been mentioned a lot of times, but make sure you check the "OB" checkbox in Vaicom's Config Tab Right at the end of "Use custom DCS Path" line.

Stenji any other mods? Vaicom might not be the only thing that was giving the stuck at 10% after 2.5.6 got out. Vaicom was updated but other mods probably have not been.

Good question, but I don't see that as a Vaicom problem rather players discipline using the map markers when they are shared by everyone. Now I do think if we could have Jester Wheel and Vaicom at the same time it would be quite a nice backup for certain situations, but I believe Hollywood has commented that this may be thecnicaly difficult.

@waitscat I had no idea Vaicom's manual had that. I gess I never paid attention to that section. But you are right it's there and it's an error. I have no idea how the commands worked back in 2017, I wasn't using Vaicom back then.

yeah like Clorydric said. Forget that File, use this one instead: https://forums.eagle.ru/showthread.php?t=171098&highlight=targetdx128

I belive the Problem is a Macro name (or several) beeing repeated in the second .ttm file.

Vaicom silencing of the Pilots own voice is working. But Vaicom was updated, I imagine the stand alone No Pilot Voice Mod, needs to be updated as well.

Not sure what you mean. The Super Carrier Commands aren't supposed to be active yet. They are just sitting in the list of commands until we get the SuperCarrier, and I imagine they will come as a paid expansion to Vaicom as well (As AIRIO). But all the commands you are supposed to uses and are supported at this time are in the manual. What exactly do you feel is missing from the manual? I do agree that some things should be explained better. Integration in particular is not covered very well in my opinion. But I'm genuinely not sure what you are getting at.

The Checking in with JTAC has been "[JTAC] Playtime 10-60 minutes" (in 5 minute intervals) for at least over a year. About the time when I got Vaicom I think and made a video. I just checked it and that's exactly how I spoke back then. The video in question has actually been added by Hollywood to the very first post of this thread. The "Checking In" command is I suspect regarding the new SuperCarrier comms. There's a few SC commands already in Vaicom and have been for a while. There's even a check box for it in the EX tab. If you want to add the "with you" alias, you must add it to one of the "Playtime x minutes" command. Sugest you add it to the 60 minutes one, and then just checkout whenever you want. Or you could go all out and add an Alias for each one with something such as "With you for x minutes"

Strange I just updated, it's all good on my end. All I did was enter VA after updating reset Lua and restarted VA. DCS loads, commands working both base plugin functions and AIRIO.

I made my own Kneeboard for referencing Vaicom and AIRIO commands. It's in a style that suits me. Trying to condense info in an organized manner as much as I could but keeping things clear and readable. Following Vaicom manual for the most part, but putting everything in double columns and swapping the order of a few items. Both for spacing and organization. Got it to 11 pages. Sharing it here in case anyone wants to take a look. lxSapper_VaicomKneeboardRef.zip

LWS Power Switch is missing from the Cockpit. you can still operate it, but 3D and Textures are missing.

Yes but you use a diferent setup for PTTs you don't keep VA on open mic (I don't eighter, but 'pocketedition' does). But good stuff I didn't notice 'emc's question.

Same.

t1mb0b that is a valid setup of course. But I am curious why don't you use the option "radio select as PTT" on SRS? Not only you are saving a button, it's also more realistic for most plane's. And if you use Vaicom, with the right set of options it can be realistic for all planes. Nevertheless pocketedition was asking for a solution that does not involve Vaicom because he's not using it. It also involved keeping VA on open mic and suspending listening when talking on SRS.

@Hollywood_315 Hey, found some ground stations missing from the TACAN list on AIRIO: Nevada: Tacan TPH (119X) Tacan TQQ (77X Tacan ILC (110X) Tacan MLF (58X) Tacan CDC (120X) Tacan BCE (75X) Persian Gulf: Tacan BND (78X) Tacan KER (97X) Tacan KIH (112X) Tacan MIN (99X) There is also an error with one of the Nevada Tacan Stations, EER should be EED (99X).

Ok I just tested this out, you don't even need to use key mapper. Do the following, disable all global hotkeys for Voice Attack. Edit your profile and create a new command. Name your command and disable "when I say", and check "when I press button", I'm assuming here you are using DX inputs for SRS PTTs, but you can use key presses mapped through RSmapper as well. Just select "when I press Keys" instead. Assign your SRS PTT to this function. And Under "when this command executes, do the following sequence" click on the box "other" and select "stop listening". Press Ok and create your command. Now Create another command exactly the same (just use another name for it), and when assigning the button check the first option "shortcut is invoked only when all buttons are released" and when selecting the function to execute select "start listening" instead of "stop listening". Create your command. Now you must repeat this for every SRS Radio PTT you are using.

Every body realizes that, and yet hardly any body is flying with a replica of the real F-18 HOTAS, so what? THis shouldn't even be that hard to code. Don't forget you are not flying the real F-18 eighter but a simulation made to "appear" that it's working like te real Jet. The way the internal code of the simulation works is not the same as the real jet works. And yet I'd even be willing to bet that if they wanted to redesign the HOTAS on the real jet and put a non spring loaded pot there, it would not be hard to program the code for it eighter. ED already implemnted the non-realistic TDC slew option because some of our HOTAS have limitations.

Hellios itself doesn't give a noticeble performance hit for me. But exporting DCS screens (MFDs etc ) Will have a noticeble one, that however should be acceptable on most systems.

I had a similar issue when I updated Vaicom two days ago. It was resolved after I deleted the Folder ..\SavedGames\DCSOpenBeta\Scripts\Vaicom. I also Edited ..\SavedGames\DCSOpenBeta\Scripts\export.lua and deleted Vaicom's entry. And Repaired DCS Install. After that I ran Voiceattack/vaicom again, reset the lua code. Restarted Voice Attack and after that everything is working as allways.

@Pocketedition I am very positive that what you want to do is very easy to achive if you have a programmable HOTAS or if you use something like RSmapper. I can try to give you a better idea on how to achive this, but only tomorrow as today I don't have access to my DCS PC.

You don't have to use "Instant select" for that. Just select "Single" PTT mode of operation and select which TX you want to use. I'm using TX5 atm as that works well for my needs. Only downside would be if I was flying the F-1 with a Human RIO he would hear my commands to VoiceAttack/Vaicom.