Hotas delay/lag
-
Hello everyone,
I have thrustmaster 16000.m hotas and after i configured it using alternate launcher i noticed there is a little delay/lag between the throttle movement and rpm gouage movement. Is it sopuse to be like that? Why it not react immediately?
The same issue happens when i move the stick. There is a bit of delay between the movement of the stick and the movement of the Jett.
I didn’t configure any dead zone whatsoever.
Any idea ?
Thank you,
John
-
The RPM gauge doesn’t react immediate. The most responsive gauge is fuel flow
-
On the Throttle, I was wondering that myself. (I have the x56)
How much of a lag is it…1/2 sec, 1 sec or more???
When I fly online, I find it difficult to adjust the throttle when trying to catch the formation without zooming past, or lag to far behind… -
Response speed should be tested in the UI bar graph. The engine itself may lag and should not be used to diagnose controller issues. DirectX axis lag should be so low as to be imperceptible.
-
….I find it difficult to adjust the throttle when trying to catch the formation without zooming past, or lag to far behind…
Practice will solve it.
-
Hello everyone,
I have thrustmaster 16000.m hotas and after i configured it using alternate launcher i noticed there is a little delay/lag between the throttle movement and rpm gouage movement. Is it sopuse to be like that? Why it not react immediately?
The same issue happens when i move the stick. There is a bit of delay between the movement of the stick and the movement of the Jett.
I didn’t configure any dead zone whatsoever.
Any idea ?
Thank you,
John
Yonts, a friend of mine once explained, during AAR practicing, that you need to be “ahead of the airplane, not behind it.” When you change a control setting, stick or throttle, you are initiating a change, but it’s not an instantaneous change. Pilot Induced Oscillation(PIO) was given to me as an example of getting behind the airplane. Plus, in the case of your throttle question, what you are doing is commanding the engine(s) to initiate a spool up/down.
As Fish said, it’s a Practice Thing.
So, the direct answer to your question is this is not a bad setting or a bug. -
BluWolf kindly pointed me at the material here - http://flyfast.org/sites/all/docs/FAST_FKG_2.0.pdf - to help with AAR, pointing out that it’s essentially just formation flying. (With a little bit of a mating ritual in the middle)
-
That’s a great document, thanks for sharing
-
There can be huge differences in “input-loop latency” depending on your OS and graphics settings, and your average frame-rate performance.
Some tips on lowering latency…
-
Try running in fullscreen-exclusive mode (to eliminate the DWM buffer). And if “tearing” artifacts don’t bother you, turn off v-sync. That will always result in the lowest possible latency from sampling your stick inputs to displaying the resulting motion on screen.
-
Try to get to 60fps or higher, consistently (eg. turn off shadows, reduce cloud density, reduce antialiasing, etc) especially if you’re running with v-sync enabled. Else you can find your effective frame rate is suddenly 1/2 your monitor refresh rate – typically 30fps… 1/30th of a sec (33ms) may not sound like much but that gets multiplied each hop, from cpu to gpu to dwm to your monitor… it can quickly add up to over 100ms of latency.
-
Try a G-sync or FreeSync monitor (whichever pairs with your graphics card)… that can help, especially at lower framerates
-
For faster systems, try Triple-buffering (with a frame-rate cap set about 30% higher than your monitor’s fixed refresh rate). This can help reduce the average “age” of frames from input polling to display… almost as good as v-sync off but without the tearing.
-
-
Also… I also have the T.1600m (just the stick, not the hotas throttle) and I have to say the throttle slider on the stick is pretty rubbish. Mine’s a few years old now, but I don’t remember it ever being great. (I don’t think it’s a Hall effect sensor like the stick… just an old school pan-pot.)
I do remember, however, it seemed to improve (? not sure how to measure or quantify) after I actually installed the TM drivers.
https://support.thrustmaster.com/en/product/t16000m-en/
https://support.thrustmaster.com/en/product/t-16000m-fcs-hotas-en/Worth a try if you haven’t done that already.
-
The RPM gauge doesn’t react immediate. The most responsive gauge is fuel flow
The FTIT gauge (right next to rpm) also seems to respond faster than rpm, and is easier to read at a glance. Over time, I’ve found myself glancing at that one as I’m making fine throttle adjustments – my throttle slider is old and dodgy, and doesn’t always move when I tell it to.
-
Check the video from the links below where you can my the input and pit response. Captures were from different devices, and were synchronised to within couple hundred millisecs using a short sound pulse. If your response is like this then I would not worry. If its not, then you must investigate the chain of events which happens between you moving your device and the game response (with input and Video) to it.
-
Yonts, a friend of mine once explained, during AAR practicing, that you need to be “ahead of the airplane, not behind it.” When you change a control setting, stick or throttle, you are initiating a change, but it’s not an instantaneous change. Pilot Induced Oscillation(PIO) was given to me as an example of getting behind the airplane. Plus, in the case of your throttle question, what you are doing is commanding the engine(s) to initiate a spool up/down.
As Fish said, it’s a Practice Thing.
So, the direct answer to your question is this is not a bad setting or a bug.Yes, IRL flying you should always be ahead of the aircraft. More ahead for more advanced planes, obviously, but always ahead. Before you begin descent in a 747 you better have been into the arrival in your head; before you go super sonic in the Concord you better already be there in your head, and before your sailplane departs the current thermal “street” that you’re climbing in, you better have already figured your gateway Go/No-Go landmarks before you begin you next sprint to the next promising piece of sky.
As a RW sailplane pilot I can tell PIO is a real thing - I went through a plateau during my licensing where I couldn’t land a darn without PIO - after having greased em before. Turns out I was reacting to the flare, and not flying it mentally before the aircraft got there.