lxsapper

Well that was my thought process that since options were added for AIRIO maybe they were corrupted for people no running AIRIO due to some bug, but that theory was already thrown out the window by Hornblower.

Ha well then I might have been using a too limited selection of airplanes to know. I think recently I've only flown in the F-14 and F-18.

Ok before I am able to help I need to get a few things clearer. You want this two functions to work on the Hat1 correct? Because the: SetSCurve(&Throttle, SCX, 0, 0, 0, 20, 0); // Control curve is for the X axis on the ministick. Are you also trying to do something on the mini-stick? Also the TARGET trim curve function is not meant for the game function (R_SHIFT+DARROW) so I assume that's the trimming you want to apply), the TARGET Trim is meant to change on the fly the way an axis responds, you can off set it, effectively trimming, or you can dynamically change the response curve. All of this is possible you just have to realize what is it you actually want to do.

Should be as precise as the WH, but the one I tried felt a little more "sticky" than my WH. Also the Throttle felt a lot more difficult to move precisely, might just be lack of habit for me, but that was my experience. Electronics wise, should be precise enough.

No that does not sound right at all. I think randomTOTEN got the right of it. You are not moving your throttles from the OFF position to the IDLE position. that why they work when you start in flight. When doing a cold start you have to move them from OFF to IDLE. In the A-10C this should be configured for you but there is trick. In other planes you will have to set it yourself or use the keyboard shortcut or click the throttles in the cockpit. Now the trick is if you load up the mission to do a coldstart and your throttles are already in the OFF position the game won't acknowledge them there and won't detect them moving into IDLE. So you must either enter the cockpit with the throttles mid range and then move them into OFF prior to starting your ramp procedures. Or in you enter with them in the OFF position, move them into mid range and then to OFF again, and then you are ready to start Ramp. Also it's a good practice to move them around anyway and visually confirm they start moving accordingly to the HOTAS position. Might be something else but from what you described so far this might be the most likely culprit.

Nice, those analogs should be quite handy too!

Come to think of it, you guys who are reporting the problem, are you AIRIO users as well?

I do use it (mostly to handle F10 menu items in multi-player) and I do not have this problem. "Take #" is working for me both in the Comms menu "options" and with "Jester Options".

So you have the joystick behaving as relative instead of absolute? are you using TARGET?

You should never calibrate TMs Contollers like the warthog in windows. Just don't... very bad practice. If they need to be recalibrated us TM tools for that. Link should be avaiable here on the forum but do tell if you need help finding them. However sounds like you may be having some internal issues on the throttle, not unlike I had some time ago. A friend of mine who is good with electronics cleaned the circuit boards and contacts for me, and heated the soldering on the components with a hot air soldering station (to get rid of any cold solders), not sure exactly what the issue was, but it's been perfect since then. Some have reported this behavior to be related to pinch wires on the cables that go to the throttle axis HALLs, in my case it definetly wasn't pinch wires but it may have been a dirty/bad connection on the same cable(left one). I also had ghost presses on buttons because of the throttle issue. JOY_BTN26 is the APENG button so that's definitely a "ghost" press. JOY_BTN29 is the IDLERON so it's tied to right throttle lever position so if the axis is jumping around from off to Idle you will see it blinking on and off.

Make sure you are binding in right the input type(select axis binds in the category) and that you are also selecting the input in the right controler column (it wouldn't be the first time I tried to bind throttle inputs on my rudder pedals or even on the Keyboard column). Also this isn't quite the right section to post this at, there is a "Input Output" sub-forum and there's Winwing a Sub-Sub-Forum there. https://forums.eagle.ru/forumdisplay.php?f=728

Don't listen to people who say "do this" or "don't do that" in absolutes. TARGET is finicky but extremely powerful, it may not be for you. I get that it's not for everyone, but it will allow you to do things that you can't do any other way (except maybe Joystick Gremlin). So don't rule it out without checking it out and understanding the pros and cons and what it is capable of doing.

@Pyker, TM Target handles doing multiple things on one press quite nicely. But you have to be carefull about the assignments you make. For example if second detent to fire the weapon works with "Space" and your first detent has a Ctrl, Shift or Alt Modifier, DCS will only see and interpret "Ctrl+Space"(ex.) not "Space" as you need to fire your gun. So using the keyboard macros on your HOTAS can be quite detrimental to your simming. Keep as many commands as you can aford as DX inputs (If you use the the 128 inputs mod for Targer you can will have more inputs avaiable than your Warthog has button/switch positions even if you program them to the off position of a switches). Or at least be very carefull with commands that can be used at the same time that use keyboard modifiers, even if they are generated from another button/switch it will still cause you problems.

I think the reason Hollywood made it this way, from my observations I made with a small .lua malfunction (I believe) that I got before last update, I was able to see that if the regular Jester Wheel was kept active using AIRIO commands would still blink it to appear on screen. I personally would prefer to have this option too, but after my initial disappointment I'm not unhappy with things as they stand at the moment. You can actually still do what you want, Jester Wheel still works in the background (it's just invisible) if you know what keys to press. If you do need to see it without saying "Jester Options" you can to the HUD only view (LALT+F1) and press 'A' to use it there.

Updated, see first post.

@Hollywood_315 spotted an error in the manual that may cause Confusion. In the command List for AIRIO it's listed "Enable/Disable Grid", but the correct commands are "Grid Enable/Disable".

Ok feeling a bit stupid now regarding the STT, apparently some options were added to AIRIO. I'm pretty sure "Track Single Target #" is fairly new, not sure when it was added. But I will remove any redundant features from this profile and update. EDIT: I feel double stupid now, I have a kneeboard for VAICOM/AIRIO, made by myself and this commands were already on it, so they are not new. So I will remove the TWS to STT part of my profile and update. Will retain the "Select Target" commands portion.

I made a small VA profile meant to be used as an Apended profile to VAICOM as a complement to AIRIO in order to give the ability of using some commands available in the Jester wheel that are still not included in AIRIO. This is in no way a replacement of a detraction from Hollyhood's outstanding work. But somethings that I was missing personally and decided to share. Hopefully at some point in the future Hollywood may decide to include equivalents to this functions to AIRIO. Until then I think they work well enough, minus the missing scratchpad from the Jester Wheel. Keep in mind this is just a keystroke profile so it's very unsophisticated in how it operates. I've Uploaded the profile to the user Files in DCS main site, but the file is pending approval, so I will add the final link when that's approved and in the mean time I'll provide it here as an attachment to this post. I made a Video that turned out to be a bit long explaining the use of the functions I added in this profile. It turned out longer that I intended but I'd recommend you watch it if you decide to give this a try. here list of the commands that are made a available: STT: Select Target - takes you to the visible Jester wheel select specific Target Menu, use next command to Complete. Target (1-7) - Finishes the Last Command by selecting a TARGET for STT and returning to Cockpit View. Radio: Push Button (1-30) - Invisible Command. Commands Jester to Set the ARC-182 to one of the Preset Channels. Done through Jester Functionality not VAICOM's Select Command. Navigation: Set (Steerpoint) With (Steerpoint) - Invisible Command. Default Functionality of the Jester Wheel Restore steerpoint Function. Input (Steerpoint) - Takes you to the visible Jester wheel manual steerpoint enter function. Use with the following commands to navigate. Go Back (Back) That's Correct (Confirm) North, South, West, East Digit (0-1) General Management: Cockpit View - Presses Alt - F1 in case a command doesn't return you to cockpit view. Can Also be used to switch to HUD only View. Not That - Presses A to Cycle to a Different Jester Wheel selection. Cancel - Closes the Jester Wheel Immediately by pressing A and Presses Alt - F1 to return to cockpit view. DO NOT use with AIRIO "Jester Options" Simply let go of your TX for that. Show me More - Use for example with Select Target if more than 7 targets are selectable. EDIT: Lock Target has been removed as it's functionality exists in AIRIO, "Show me More" is now "Show More" and "More Targets" you can use either one. This makes the video somehow outdated so be mindful of that. EDIT2: Added "Input Grig/Input YY" to allow direct input of coordinated for NAVGRID works the same as "Input (Steerpoint)". Download Link: https://www.digitalcombatsimulator.com/en/files/3311045/

Cool, don't usually use hot mic with voice attack. But it will be a nice touch

Never mind I finally figured it out. Had to have a AIM-54 selected with TARGETS prioritized by the AWG-9.

Hey @IronMike My question was not about tracking contacts and STT in general I realize Jester sometimes can't track what ever is out there. My question is about Functions 5 (FIRST TWS TARGET) and 6 (TWS TARGET NUMBER) under the STT LOCK menu. They seem never to work regardless of actually being in parameters to use functions 1-4 successfully. This is also regardless of radar mode (obviously this function was made to be used out of TWS, but functions 1-4 work, when within parameters both in RWS and TWS). So I'm puzzeled about options 5 and 6, when to use them, how to use them, are they working as intended, etc?

Personally I've actually gone through the steps of removing windows store entirely, still happens.

Oh it works alright, that's not the problem, it's also not a Target issue, on the contrary one of the reasons I started using Target was to get around this problem. Let me try to explain better. I don't know the VKB joystick or what's the button numbering on it. But that button you are using has a DX number 1-32, now if you are using a throttle that will also have a 1-32 button number. When you press the button on your throttle that has the same number as the button on your joystick that you assigned to trackIR that will do the same exact thing. This is because trackIR software is only locking for DX button pressed regardless of which controller sent it. This is a really bad oversight on the part of natural point and we have to work around it. Now like I said I don't know the VKB hardware but I remember it has a control box right? Do you connect all your devices there being detected as one device? If that's the case it probably has a higher button count, like TARGET can also provide, and that may be the reason you never encountered the issue when using the throttle.

I had a similar issue. It was actually something related to the left throttle axis, where the axis would stop responding, jerking it around would sometimes get it working again but often if would just act up again, in general behaving like I had a pinched wire. When the throttle was in its non responsive state I started to note that some buttons were generating ghost presses so using only the right throttle was out of the question. In the end a friend of mine who repairs electronics cleaned for me the whole electronics inside, the connector for the left throttle hall sensor, and I can't remember for sure but I think he also applied some hot air soldering to some parts just to make sure I didn't have damaged soldering on the components. Plugged it back, it's been solid since then (almost a year now). And obviously that concludes that the problem was not internal cabling as I also suspect initialy.

I have a question regarding the commands from the Jester wheel to STT a TWS Target. Jester always says unable regardless of being TWS or RWS. Bur he often seems to be able to STT from the "Select specific Target" Command on the Wheel also regardless of radar mode. Can any one elaborate on this, let me know what I might be doing wrong Etc?