Guppy

It was captured at 30 FPS, so it exaggerates the impact. But it is still pretty noticeable.

Those have both been done already.

Here is a video of the issue. Pay attention when I look out the sides, it becomes super apparent at that point. Happens in F2/F3 views, too. Adjusting graphical settings to the lowest doesnt do anything either as it's not a frame issue. I'm a solid 60 the entire time or much higher when I lower settings. This is with all exports and DCS BIOS, etc shut off. I also did a flat spin so you can see just how terrible it gets. Oh... and the game crashed -- lol!

Mine is already off, but I continue to get the same behavior. 8700k @ 5.3ghz 32GB solo SSD for install 2080Ti OC'd Whether I use my exports or run a single screen... the micro stutters are there since the last update.

I have the same behavior here; exactly as you describe with or without GSYNC or VSYNC enabled and shaders deleted.

I'm not sure if my link fell off before, but here you go: https://guppy.home.blog/2020/07/13/out-of-control/

Thanks! I need to post updated shots, but this is the latest post on my blog. https://guppy.home.blog/2020/07/13/out-of-control/

As I stated in a previous post regarding other important issues, 100% agree. I am not asking nor am I insinuating That this is a critical issue. It is, an issue, that I would like one day addressed as the module matures.

Here's the thing, a real hornet pilot does not need to worry about dead-space in their throttle movement because the jet puts a physical barrier that does not allow the hornet pilot to transition into that space (gate) while in the air. To remember that pulling your throttle all the way into that space will do nothing is as unrealistic as my solution of two separate curves. I'm not arguing realism here, ED has made compromises to bridge the gap for chairforce pilots already. I'm arguing practical implementation given the limitations of consumer hardware as a fair compromise. You don't like it

randomTOTEN, please correct me if I am wrong, but the actual Hornet physically limits the throttle from going into ground idle position. That is, it does not allow the throttle to transition into ground idle while in the air. So yes real Hornet drivers deal with a limited throw, but they do not deal with a dead space between ground idle position and flight idle positions like we do. Your example of the Q400 is an example of throttles that work like ours do. There is no physical limitation that prevents the throttle move into the ground idle position. So you get the alarm because, in the rea

No I think this dialogue is good. I appreciate the candor and the context of all of this. There are inconsistencies here and there are trade-offs for realism that make other things "less" realistic and it is good to talk about such things. As the OP, I can say this. haha :)

I honestly fully disagree with most of your assessments, randomTOTEN; you're trading one piece of 'realism' while having unrealistic throttle behavior on our home throttles. While I do agree that yes, the real jet does limit the throttle throw when in the air it also does not have a dead zone. So the game is forcing us to have an unrealistic deadzone. That is, there is a physical component that moves forward in the throttle in real life that calibrates itself. Our home throttles do not do this and there is no workaround for this unless we are willing to make WoW thrust unrealistic. Case and po

The issue is not from off to idle. It is from idle to anything. The 1/2" movement that you experienced is exactly what I am talking about. You lose part of your throttle throw when transitioning away from idle in the air. This is not a problem on the ground. The problem you are going to experience now that you have adjusted your curve is that while you move your throttle from idle to X in the air to compensate for this... you are going to be way more sensitive on the ground because on the ground it works without adjusting the curve. Weight on wheels physically changes the lowest RPM in the

I don't use the TMWH any more - I use the WINWING throttle. But it really does not matter as the behavior is the same for every throttle out there.

Well... this issue is beyond the TMWH and A-10, as I noted in my original post this is an issue across ALL throttles, because of the way it is programmed in game. ED has programmed a dead zone for the first 5-10% of the throttle movement range when in the air. When in reality the game should just recalculate a curve when you are flying. The way it should be coded is the following: I forget the actual values off hand here, so bare with me.... Lets say a throttle range of movement is from 0 to 100. At 0 you are at idle and at 81 you have engaged the afterburner; 80 would be full mil. At 1