imacken

Try Axes Curves>Throttle Linearity Calculation. Bit fiddly, but that should help. Go through it slowly until you get ticks in all intervals.

Thanks for the clarification, BN.

Can someone please clarify what is the correct IFF4 behaviour to unknown response. There are various threads on this but I haven't seen a definitive answer to this. TMS left short, response with a yellow square shown in - DCS Stable version, Wag's videos (e.g. November 2022 Update), NCTR Training mission, etc. No response - current DCS OB behaviour, various people contributing to threads here on this. Just curious to know.

So, as the TM says there should be a square for negative IFF response, and Wags's video from a few months ago shows a yellow square for a negative IFF, has the behaviour changed recently? Just curious.

Thanks guys. The only thing is, that the instructor in the TM for this topic specifically says that the unknowns will show a square around them.

However, I will say that the unknown IFF square does not appear ever as mentioned by @Chain_1 above. Has this bug been reported?

Thank you so much! I've been away form the Viper for a long time. forgot it was 2 up presses of TMS to get STT. All good now!

I use Skate’s utility for continuing use of ST and the batch file I posted earlier to swap presets and run MT.

Thanks guys, but I'm afraid it's just not working for me. Here's a track of the TM. You can see me doing regular long TMS presses on the target and getting nothing. NCTR.trk

I just can't seem to get any response from NCTR long TMS hold until the plane is around 5 miles away. I don't even get the INVL symbol. This is easily demonstrated for me in the NTTR 120 IA mission, or even the NCTR Training mission on it. I have STT on the target within 30 degrees azimuth and elevation. I get the LOS message in bottom left of FCR, but nothing under NORM until within about 5 miles. Something I'm missing?

Yep, exactly that. If you make any changes to the config make sure you copy 'Options.lua' over to the 'Options VR MT.lua' or 'Options 2D MT.lua' files before next use.

Guys, for me, the most useful aspect of the Utility was the ability to choose presets. I had one for monitor and one for VR and I chose them from the drop down menu in Skate's Utility - obviously. Now that we have to (temporarily) run MT from a shortcut, it was a bit of a pain to copy across the lua files to swap between monitor and VR. So, I put together a very simple batch file that offers the choice of monitor or VR settings, and then copies the appropriate one into Options.lua and runs DCS MT. I have attached it here if anyone would like to use it. Obviously, you will have to edit it to input your own paths and file names, but it's pretty useful. DCS MT Options.zip

Sorry, can I ask again, does this method not just run the shortcut? Presumably you can't actually use any of the Utility's functions - e.g. choosing presets - though, or am I wrong in saying that?

Is that not just running the shortcut though? You can't actually use any of the Utility's functions on it can you? Sorry if I'm missing something.

So, the Index/VP2 version I have of VRNS certainly runs OK with DCS MT, but, the rotation points are off centre so not really usable.

Unfortunately, XRNACKSAFER doesn’t work with VP2. Haven’t tried it yet. I’ll give it a go and let you know.

After ED's monumentally good patch this week, we still do not have this fix which was ready to go back in August. Seriously, what do we have to do to get this put in?

So, do we have to manually rename the presets to use them?

Well, the method you are using is the one I put together a while ago. Not everyone uses that method. Others may involve changing saturations etc. However, you do have to adjust saturation values as per my point 2)d in the post you linked to for planes that don't have afterburners.

Glad you got it all working nicely!

That all looks pretty good. A couple of tweaks I would suggest. Firslty, set 'sticky deadzone' to 0, and secondly give your hardware buttons values that are a it below your first detent calibration value. Try 45800 and 30800? This gives a bit of leeway when going over the physical detent. Re the idle function, can you post your button tab? Have you defined the logical buttons for your new hardware defined ones?

Copy the whole Input folder if you’re going to do that. Then you have all module binds, not just the Hornet. But, it makes sense to have a proper backup strategy for your whole system.

No, you can’t drop Tobii Experience. You can only drop GameHub. As I said above, there are drawbacks with using the Opentrack approach, and I would say it is more intrusive than GH imo.

Yes, and it works pretty well with Opentrack. BUT, you can't use eye tracking - no big deal for some - and, most importantly, you can't use the built-in native support in MS's sim for Tobii with Opentrack installed as it prioritises that as it thinks it's TrackIR. So, it's swings and roundabouts.

Can you post a screenshot of your axis tab (as per your first post) and one of the throttle axis tabs, i.e. rX or rY, by double clicking on one in the main axis tab?