Stubbies2003

I was in F2 view but wasn't looking specifically for that but I can the next time I fly MP.

That is why I specified that I hit cancel twice. I didn't change anything I simply went in and looked at the movement on the axis to verify it was going full one way then the other then I cancelled out back to the main menu. That shouldn't have changed anything.

No it isn't even an issue of pushing it over too fast as I can do that and as long as the aircraft isn't going too fast then it behaves fine. If I did that with too much speed and it behaved badly I wouldn't be here talking about it.

The problem I have with this theory is when it is working correctly and the aircraft gives the sudden stop I can leave the rudder/NWS position the same and give it a fair amount of throttle to get it to move and it doesn't slide. It turns in the direction selected.

No. I know what you are referencing as during testing after this problem almost went away I can see the aircraft come to a sudden stop in tight turns but the problem isn't related to that at all. When I could duplicate this just to prove to myself it wasn't an issue of going too fast I had the aircraft going VERY slow. I would fully deflect and it would start to go to the correct side, then after a bit straighten out then turn and start heading the wrong direction then it would stop due to lack of speed combined with friction/drag of the moving tires. That stop wasn't sudden at all unlike the ones I see now with big turns with it working properly.

Sigh. So right before I went into SP to make a track I had looked at the rudder controls to verify it didn't look like it was doing anything funky. All looked fine so I cancelled twice back to the main screen which *shouldn't* have changed anything and now I can hardly get this problem to occur at all. If DCS decides to start doing it again consistently then I will make a track showing the issue. As it is I have tried several times in SP on caucus and PG maps and NWS works just fine. I can see it rarely when in MP but not consistent at all.

The slider on the TM WH isn't a digital on or off only input it is a analog input and that is what I am using for rudder/NWS inputs. Not much different than any other axis to use. If I only input about 85% or so of max input to the rudder then NWS Hi works just fine. The only problem comes about when the full rudder input is given. Which is fine but getting "stuck" isn't my problem at all. That is something bbrz just starting talking about in the last few posts and isn't relevant to the issue I see. The only reason I even got to the point of talking about the aircraft stopping in the first place was the countless times I was told I was just taxing too fast. Hence me stating that I can duplicate the issue at such low speeds that the aircraft will stop itself. Nothing to do with the problem at all. Just proof that isn't believed.

Yeah a Thrustmaster Warthog is such a PoS HOTAS I know. Perhaps if you read the entire problem that this DOESN'T happen outside of NWS Hi you'd understand that it isn't HOTAS based. If the HOTAS was sending funky rudder input at full deflections it would also be doing that outside of NWS Hi. Which it is NOT. If it was an issue of only having a bad button for the NWS Hi then this would be intermittent with wings extended and locked but consistently good with wings folded or wings extended but unlocked. Which again it is NOT.

That would be you misunderstanding what I am saying. I am not saying he is calling me a liar for asking for a track file. I AM saying that for his insistence that my problem is based on the speed I am doing this at even though I have stated multiple times that I can duplicate this at any speed. Him insisting that it is speed when I say otherwise only leads to two conclusions. He either thinks that I don't know what I am doing or am lying about it. I will test and see how well making a track file works through VR. I have no problems in showing the info as it will just give a visual representation of what I can always duplicate.

Yeah wrong answer. So in a phenomenal waste of time I downloaded and watched that track file. Not exactly earth shattering. You are showing what mine doesn't do. The only benefit was in learning where the track files are kept and how to use them. This problem wasn't negated by your track file example of it working.

Once again it has NOTHING to do with speed. The only reason I was even trying it that slow is to prove that it wasn't an issue of going too fast. Yet once again I can duplicate this problem at ANY taxi speed. With you getting hung up on this whole "stuck" bit I'd think you were responding to a completely different person or problem. No I have not. I can look at it but I know how to taxi an aircraft around. Even with this problem I know the work around and have done plenty of taxing both at airfields and on carriers. Easy enough.

Seriously how many times do I have to point out that it was going so slow that it stopped BY ITSELF before you might not think I am lying about this? I've never done a track file and don't know the procedure.

At what point did I ever say it is getting "stuck in a turn"? It never gets stuck in a turn. It straightens out the aircraft then reverses the turn direction all on it's own. If left hard over the rudder it will start left, then straighten out and then turn hard right. It will keep turning right until I either go from NWS Hi to regular NWS or I remove 15-20% of that input to the rudder. If I do the same but full right rudder it will do the same as left rudder but reversing the turn to the left. Regardless of if it should do that or not that IS what it is doing. I can duplicate this with speeds all the way down to where the aircraft cannot even sustain movement itself. Adding throttle isn't going to fix that. It will just allow the reversed turn to continue.

I don't know how many times I can say it but I am NOT GOING FAST when I duplicate this issue. As stated not but a few posts ago I can be going so slow and duplicate this problem that the mere fact that the aircraft is turning at idle thrust plus friction stops the aircraft all on it's own. That is WELL below 5 knots. THIS ISN'T A SPEED PROBLEM.

Going to take a guess and say you ordered an aircraft repair. Aircraft repair on the F/A-18 breaks the radar altimeter. Known issue bug reported ages ago.

Not with the problem I am seeing. I get that if you are going too fast that it won't behave right. See the above two. I can duplicate this at speeds where the aircraft will stop on it's own.

Even mine will for a very short period of time. Then it does the straighten and reverse bit every time without fail. The only thing that folded wings gives you is the ability to stay NWS Hi without having to hold the button down. Either way it matters not as the problem exists for me regardless. As stated in the previous post I can duplicate this at such low speeds that the reversing of the turn stops the aircraft entirely.

Very low speed for me is the aircraft is going so slow that by the time it reverses the turn and starts turning the wrong way the aircraft stops completely on its own due to idle thrust, lack of speed, and the turn. For me this never works correctly when fully deflected and NWS Hi. If I fully deflect either to the left or the right it will always start turning in the correct direction, then straightens out, then it reverses the turn to the wrong direction. Without fail it does this. No mods done to my DCS or to the F/A-18. Normal NWS never does this. Always does in Hi regardless of speed.

OK I am only posting on this one again to link a video of some F/A-18 deck ops just to prove that the real bird can do these super tight turns. Precisely like the one I brought up so no if you are going slow enough it isn't going to behave like it currently does in DCS. DCS it doesn't matter what speed you taxi at the odd behavior of it centering then turning in the wrong direction is still there. Fast forward to 13:40 if you only want to see the nose wheel turn 90 degrees to the right and turn just fine. Watch it all for the enjoyment of seeing the professionals at work. No need to respond. This is mostly so the folks in charge of the F/A-18 can see this needs fixing in DCS.

This is a real function of the real F-16. It basically just swaps into CCRP once the indicator is below the HUD FoV but the release time isn't there yet.

Well the one thing that totally set me off of the X-65 path was the horrid weapons release button placement. To this day I don't understand why they placed it where they did. Last thing I would ever want is inadvertent weapons release thanks to bad design. Personally I went TM WH and then later added in a FSSB R3 Lighting and, to me, that is the perfect compromise. Yes your throttle is an A-10 one and not a F-16 one but I like the extra buttons and switches to program. :)

Perhaps the problems could be intertwined but that video is for a temp fix on a completely different problem. I'm in the same boat (pun!) as Preendog. I've never asked for clearance and I've never seen this bug. It isn't for a lack of trapping and catapulting from carriers on my part.

I've seen this bug a few times and it isn't limited to right side as I've seen it left side. The annoying thing is I haven't found a way to un-bug it once it get there. Cycling through all different azimuth scans doesn't fix it. Changing AAM to guns and back doesn't do it. Recycling power on the FCR doesn't do it. Moving a target to the side it is scanning and locking it then dragging it to the other side and unlocking doesn't do it. The Rset option on the FCR page doesn't seem to do anything that I see in the FCR and definitely didn't fix this issue either. The only thing I've found to fix it is get a new aircraft. Thankfully this has been a rare bug and I've only seen it twice.

More like you are mixing up/confusing engine anti-ice with pitot heating. Which are two different switches entirety. Engine anti-ice has test/off/on. Only pitot heat has auto.

Once the AMRAAM goes pitbull it will find and attack the first thing it finds much like a AIM-9. If the AWACS was closer than the MiG-23 or the AMRAAM picked it up first then yes this is a thing.