lxsapper

Sending a PM for the curved extension.

I am interested but I am in Europe, I'd pay for the shipping difference.

Since you changed it, try saying exactly "Radio Change Two Five Four Decimal Zero".

I've suspected for a while that ED doesn't include this aparently simple feature because in DCS the throttle position isn't actually linked to the axis assigned to in but rather the position of the lever in the 3d cockpit and in turn that is linked to the axis position, which is probably the reverse of what other sims do.

No it's not. Apologies, I didn't pay close enough atention to all that you explained before. Not really but it sounds like you may want to check your F-14 special options inside DCS. The F-14 allows for some direct control of SRS with ingame PTTs, I don't care for it so I set the PTTs in special option to "Default", that way I keep "Allways allow SRS hotkeys" and "Allow DCS INCOCKPIT conttrolled PPT" both to OFF.

Absolutely agree, this should be stock DCS. Still one must get around as we must. In TARGET I have a profile for each aircraft, and I can change them on the fly.

+1 on the thread. Long time requested feature. Shrimp TM TARGET Script allows to set this up, doesn't the VIRPIL software allow for something similar?

I use TM TARGET Script for a custom axis response dor each plane, I get two perfectly linear response zones (For Dry and Wet thrust), much better than the messy thing you get trying to make a custom curve in DCS.

Absolutely agree, both with the fact that any F-16 would jump chocks and with the fact that there are much more important things to work on. Also consider the fact that chocks in DCS are probably an event implemented "on rails" with physics suspended, I supose creating an event that would deactivate the chocks when the aircraft (for all apropriate jets in DCS) was producing over a certain amount of thrust would be easy enough, but it wouldn't "jump the chocks" in a realistic manner. But do we really want/need it? When so many other core features would be more desirable?

I think a lot of the issues with TX6 come from when assigning the command to a button by default the "Execute this command when all buttons are released" seems to be checked for TX6 press (for joysticks). You must uncheck it! It should only be checked for TX release commands.

When using Integration with SRS when you first press the corresponding PTT if there is an AI entity on that same frequency VAICOM will inhibit SRS transition until: 1- you speak a valid AI command/ transmition. 2 - You speak the command "Swith". If there are no AI's listening it allows you to speak on SRS straight away.

I had this problem it was reported before by a few people, @Hollywood_315 tried to replicate it and wasn't able to. Bu the did give us the companion Vaicom app which relaunches VA if it closes (like a crash). Having said that I seem to not being experiencing it anymore. I changed two things I believe one of them might have been the culprit: 1 - I had three joystick devices added and being recognized by VA for push to talk purposes. I have only have one now. 2 - I reduced the joystick pooling frequency to 20X per second. It's quite low, but it works fine. 10 is a little on the low side, you can definitely tell some laggy response on PTT activation. Again I am not sure any of this was actually to blame, because I haven't tried to put the setting back to test, I was just glad VA stopped crashing and I wanted to make sure at first, but I haven't had a VA crash since.

Hi just wanted to say I found a "bug" within the file. Easily fixable, at line 929 is reads "define DX78 3076" when it shoud read "define DX78 3077" this little error causes programing DX77 and DX78 to both report as DX77. 3077

Joined! :)

Invite expire. You should create a non-expiring invite and post it here.

You do realize that Vaicom works on top of VA but it's not a part of it or is affiliated with it? If you do own VA and are already into voice commands Vaicom is indeed free to try with some limitations. If time is all you wasted then there isn't much to complain about is there? Is not like you bought VA just to try Vaicom and then hated Vaicom. Some people... seriously.

No. You can use the Select command (default VAICOM) or try my complementary profile. But AIRIO does not change ARC-182 preset channels through Jester AI atm.

One of the worst things about the Warthog is that ministick. Replaced mine with this: https://forums.eagle.ru/showthread.php?t=200198 Having said that you can tweek the response curves to make it easier to use. The A-10C is pre configured to have it be pretty useable from default.

That script is correct. Use device analyzer to confirm independent throttle movement for each axis. I suspect your trouble come from having the wrong assignment within DCS, you must make sure Z_Axis and ZROT_Axis are assigned to "Left" and "Right Engine Throttle" Respectively. You probably have Z_Axis assigned to "Engine Throttle" which is a setting for people with single axis throttle, not the one you want to be using.

Just like rob10 said. Under modifiers in DCS control assignments you will see two columns or boxes one called modifiers and the other called switches. Both work similar but switches are modifiers that work as an on/off toggle (exactly what you are asking for).

Nice tip! Thanks!

Just a dead stick I was forced to perform, turns out the Cat isn't so bad at gliding. Thought people here might like to see it. And please don't judge me too much... :cry: :D

Well for the Hornet you could use the Y axis on the spare one for Radar antenna elevation, should be the only type of analog axis (sprung to center) that works well with it at the moment.

@pabletesoy I think I know what you want, try this: MapKeyUMD(&Joystick, H1U, AXIS(MOUSE_Y_AXIS, -80, 20), R_SHIFT+DARROW, R_SHIFT+DARROW); //This will give you Trim in both M (standart) and D layers or this: MapKeyUMD(&Joystick, H1U, AXIS(MOUSE_Y_AXIS, -80, 20), R_SHIFT+DARROW, 0); //This will make the D layer a Null Command (no function) SetCustomCurve is only for axis inputs since you are using a digital input to control the mouse the rate of that movement is defined by the "-80, 20" numbers, play with those to get a different response. Let us know if it helped.

Tracks is DCS have all kinds of problems. Might be related to Vaicom commands being inputed into the simulator by less conventional means.