Donut

Thanks for posting these tracks. This is the same exact behavior that I am experiencing and have posted in my tracks as well. This problem still exists after today's hotfix. I would think that an issue like this would qualify for a hotfix...for me, it definitely qualifies for making the aircraft unflyable and "game breaking."

Correct as is? Can we get a little more explanation from ED about this than just that? Why is this an intended feature and what does it simulate? How does this work for those of us with regular, non force feedback sticks?

Disconnecting the rudder pedals was one of the first diagnostic tests I did. I also tried deleting the rudder axis binding in the controls menu to ensure that there could be no possible rudder input. The results were the same. The F-16 exhibits an uncommanded left yaw/slide no matter what I have tried.

For me , it only happens with the F-16 (not with Tomcat or Hornet). I think it could have something to do with the F-16's gold tinted canopy.

SP

I am curious as to why some are having problems with rudder behavior and others are not. I would have attributed this to the diversity in setups, rudder pedals used, and virtual pilot skill, however; I only experience rudder and ground handling problems in the F-16. I use the same exact setup and controls with other aircraft and have no problem at all with using the rudder. I have been flying flight sims for 30+ years now and have never had issues before. This is what leads me to believe it's a bug of some sort with the DCS F-16 itself. I have flown the F-5, F/A-18, and F-14 right at early access release and the F-16 is the first aircraft that I have seen with rudder and ground handling issues. I have yet to takeoff or land in the F -16 without, as Emmy has perfectly described, "wandering down the runway like a drunken sailor."

It seems that way, which makes it even more strange. I have posted a number of tracks showing the issue. At first, I though it was an issue on my side with controls or calibration. I ruled all that out and of course, if it was a controller issue, I would see this behavior on all aircraft, but I do not.

Same here...except for the F-16. A-10, F-5, F-86, F-14, F/A-18 require no rudder input with zero wind conditions and symmetrical or clean loadouts. The F-16 requires significant and constant rudder input, even clean and with no wind. There seems to be a very significant issue with the rudder and how it handles on the ground.

Some feedback from Wags or ED on this would be greatly appreciated...

I don't need any rudder input on takeoff in the Hog, Hornet, or Tomcat with symmetrical loadouts and no wind. The F-16 requires constant rudder input in all loadouts and conditions. This is either or bug or there is something unique about the F-16 that explains this behavior. Input from Wags and ED would be very much appreciated.

Interesting question...other than WWII aircraft, I have never had to use so much rudder on the ground as I do with the F-16.

Are you saying that when you takeoff, you are applying rudder input at all times, even with a clean jet and no wind? If so, do you have to do the same in other DCS aircraft? For me, if I load a mission all set up for takeoff on the runway, the F-16 will require rudder input, other aircraft do not. This is with a clean jet and no wind. Why does the F-16 require so much rudder input during the takeoff roll and other aircraft do not? When I fly the F/A-18 and F-14, if they require rudder input from crosswind or asymmetrical loadouts, I am able to apply appropriate rudder input and stay in control, keeping the aircraft straight down the runway...I have been unable to do this in the F-16 for some reason.

I have tried all types of curves and deadzone settings and the rudder sensitivity/behavior is just too much to control. I have yet to accomplish a straight takeoff roll, clean jet or asymmetrical loadout. Even during taxi and low speeds, I am just moving the rudder a fraction of an inch at a time. The same rudder curve I use on other aircraft is far too sensitive with the F-16...the same physical rudder input in the F-16 gives a far greater response in game than other aircraft. Something just seems way off with the rudder control in the F-16. I have never had issues with any other aircraft in DCS (A-10, F-14, F/A-18). For those of you who don't have any issues, can you post a video of your rudder behavior? Make sure to have the control indicator on screen so we can see the input. Maybe the F-16 requires a different rudder technique. If so, I would like to see what you guys are doing to stay in control to keep in straight down the runway.

I tend to do the opposite and drift left... https://forums.eagle.ru/showpost.php?p=4079176&postcount=97

I am glad I am not the only one seeing this behavior on the takeoff roll. For me, the F-16 yaws/slides to the left on takeoff and I have posted the tracks here: https://forums.eagle.ru/showpost.php?p=4079176&postcount=97

After today's latest patch, I am still experiencing left yaw on takeoff and left roll while airborne. Clean jet, no pylons, no wind. I have included several tracks of the F16 showing the behavior on each map as well as tracks with the Hornet showing no yaw on takeoff. For the track that shows the left roll while airborne, I made no inputs other than throttle and then turned on the autopilot. Once stabilized, I turned off the autopilot with no further control inputs. After a bit, you can see a slight left roll begin and a degree change in heading. F-16 left yaw takeoff Nellis.trk F-18 no yaw takeoff Nellis.trk F-16 left yaw takeoff Batumi.trk F-18 no yaw takeoff Batumi.trk F-16 left yaw takeoff Al Dhafra.trk F-18 no left yaw takeoff Al Dhafra.trk F-16 left roll airborne.trk

Why are your FPS limited to 62 and not 60? I am looking forward to your results. Some people may be more/less sensitive to the stutter. I had a 60Hz monitor before my current one, so there was no issue with TrackIR. I immediately noticed the stuttering when switching to the 144Hz GSYNC monitor. I first had it set at max FPS which in DCS, my FPS varied greatly from 80's to 144. I realized after a lot of research that this did not work with TrackIR's 120Hz refresh rate, even with GSYNC turned on. 120 FPS is not sustainable in DCS of course unless you lower the graphics settings, so I limited my FPS to 60. This improved the stutters significantly but they were still noticeable, especially when looking to the side...it seemed like the ground/scenery would stutter by, almost like skipping a frame. This all has led me to my settings I posted earlier.

Yeah, I don't think this is a control issue or an issue on the user's end. Too many people are experiencing this and for me at least, I only see the uncommanded yaw on takeoff/roll while airborne in the F-16 and not with any other aircraft.

I have that exact same monitor...TrackIR will stutter at anything other than 120/60Hz...I have also not had any luck with GSYNC working with TrackIR and using a frame rate limiter.

Hmm, good point. I wonder if ED can at least make use of the track file to see the problem. I have never recorded a video of DCS before. Maybe someone else has the ability to post a video of this...

I have a 144Hz GSYNC capable monitor... After much trial and error, I have found the following to give me the smoothest TrackIR performance: GSYNC off Set monitor refresh rate to 120Hz Set vertical sync to Adaptive (half refresh rate) in Nvidia control panel No frame rate limiter I had tried using GSYNC and limiting FPS to 60, but the microstutters were still present, most noticeable when looking to the side. The capabilities of my monitor are useless and not compatible with TrackIR...I wish I had l known this before purchasing the monitor. Oh well.

Okay, just tested opposite runway takeoff at Al Minhad...the yaw was back to the left. So, runway 27 was yaw to the right and runway 09 was yaw to the left. Yaw is always to the left at Nellis and Batumi no matter the runway direction.

The same behavior, left yaw. I did a takeoff at Batumi and had left yaw as well. Only the takeoff at Al Minhad yawed to the right. All takeoffs on NTTR and Caucasus yaw to the left. Strange!!! I repeated all takeoffs in the Hornet and it stayed right on centerline during the entire takeoff roll. There is no wind present. All wind is set to 0 in the mission editor, default weather.

Okay, here is something to add... All of my takeoffs have been at Nellis so far. Just for the heck of it, I decided to test this behavior at Al Minhad on the Persian Gulf Map. During this takeoff, I actually experienced a very slight right yaw on takeoff but it stayed straight for the most part. What in the world would explain this?

Well, I have no idea what is happening. The fact that it only does it with the F-16 and no other aircraft rules out a problem with my rudder or calibration. I have also checked to make sure there are no conflicting controls and that nothing else is assigned to the rudder axis. I have used the Thrustmaster calibration tool and controls are centered and functioning properly. I have even unplugged my rudders and results are the same...F-16 yaws left on takeoff and other aircraft stay straight.