What is it with MSFS and taildraggers?

Alan_A said:
You can use a low power setting and a long groundroll, and you'll still get it at 40 knots. As YoYo notes above, it's the result of the rudder suddenly going from zero to 100 percent effectiveness at that speed.
Click to expand...

This is correct and can be adjusted in the flight_model.cfg [CONTACT_POINTS], for example here's the Savage Cub:

max_speed_full_steering = 10 ; Defines the speed under which the full angle of steering is available (in feet/second).
max_speed_decreasing_steering = 20 ; Defines the speed above which the angle of steering stops decreasing (in feet/second).

Put a 1 in front of each those numbers and note the difference on take-off:

max_speed_full_steering = 110 ; Defines the speed under which the full angle of steering is available (in feet/second).
max_speed_decreasing_steering = 120 ; Defines the speed above which the angle of steering stops decreasing (in feet/second).
 
I still want that castoring tailwheel. To me there is no point in trying to perfect any sort of takeoff or landing in a tail-dragger unless the wheels are doing what they are supposed to do. The sim needs fixing. I can still do handbrake donuts in the Icon in the middle of the Atlantic. So add "proper" floats to the list.:engel016:
 
Bazzar, All I know is what the sim thinks it's supposed to be doing. I also know that when I have the tail-wheel set to 180, I can use diff braking to get it spinning on one main, then take my hands off everything and the plane stops turning like the back end ran into a wall. It behaves (a little) more realistically when you have virtual steering cables running down to the tail wheel. So for now, that's how I'm running it - I call it a field mod...
 
Tom, I'm not talking about behaviour here. I am referring to the fact that castoring animation does not appear to be supported. Control cables are not for castoring wheels they are for rudder linked tailwheel or what is called a "steerable tailwheel". Castoring tailwheels cannot be controlled or steered. They just follow the rear of the aircraft making it easier to turn. Just like a shopping trolley. The Spitfire has a castoring tailwheel. The Cessna 140 does not, that is a steerable, rudder-linked (via sprung cables) tailwheel which turns when you apply the rudder, even when stationary. Turn the rudder on a Spitfire when stationary and nothing will/should happen to the tailwheel. Start moving forward and the tailwheel should swing to assist with the turn and re-centre when you brake to a stop again. It is this animation/behaviour which is not properly coded in the sim right now.
 
Gotcha. I'd have to reset the 180 bit and re-test. Unfortunately, I'm dead tired, and my oven's telling my my pizza is ready! I'll make a note and test as soon as I can.
 
If you have our Spitfire or our DC-3 in P3D, test the castor wheel there. It works in P3D. If you have our Cessna in P3D you will see the difference between the two quite easily. Have a great Pizza!:engel016:
 
Alan_A said:
It's not torque. The uncommanded leftward excursion is not only independent of crosswind, it's independent of power. You can use a low power setting and a long groundroll, and you'll still get it at 40 knots. As YoYo notes above, it's the result of the rudder suddenly going from zero to 100 percent effectiveness at that speed. In taildraggers it's compounded by the absence of a castoring tailwheel and by persistent ground friction issues - which aren't as bad as they were during the tech alpha, but they're still there.

In other words, it's all about the bugs and has nothing to do with flying technique.
Click to expand...

Very true. I thought the sudden swing might be an attempt to model torque, but you are quite right that power setting doesn't affect it.

I question whether it is about rudder effectiveness though, because the swing happens even if your rudder is at neutral.

August
 
tiger1962 said:
This is correct and can be adjusted in the flight_model.cfg [CONTACT_POINTS], for example here's the Savage Cub:

max_speed_full_steering = 10 ; Defines the speed under which the full angle of steering is available (in feet/second).
max_speed_decreasing_steering = 20 ; Defines the speed above which the angle of steering stops decreasing (in feet/second).

Put a 1 in front of each those numbers and note the difference on take-off:

max_speed_full_steering = 110 ; Defines the speed under which the full angle of steering is available (in feet/second).
max_speed_decreasing_steering = 120 ; Defines the speed above which the angle of steering stops decreasing (in feet/second).
Click to expand...

This is very interesting, but it seems unrelated to the wild swing bug, which is related to rudder effectiveness, not tailwheel steering effectiveness.

August
 
If the majority of stock aircraft exhibit the same behaviour, no amount of fiddling with the steer angles, elasticity tables or any other file entry is going to help. The problem lies in the base flight model of the sim and there it will remain until somebody fixes it.:engel016:
 
bazzar said:
If the majority of stock aircraft exhibit the same behaviour, no amount of fiddling with the steer angles, elasticity tables or any other file entry is going to help. The problem lies in the base flight model of the sim and there it will remain until somebody fixes it.:engel016:
Click to expand...

We know. :/ I think we're just trying to understand the bug better.

Meanwhile, with many aircraft, I don't worry about sloppy takeoffs caused by this; just get the plane in the air somehow and enjoy the flight. And on landings. I may rate my approach and touchdown, but I don't beat myself up if the sim shoves me off the runway on rollout. If I want a plausible start-up to shut-down flying experience, I can still play P3D or FSX. Or FS9, for that matter.

August
 
K5083 said:
We know. :/ I think we're just trying to understand the bug better.

Meanwhile, with many aircraft, I don't worry about sloppy takeoffs caused by this; just get the plane in the air somehow and enjoy the flight. And on landings. I may rate my approach and touchdown, but I don't beat myself up if the sim shoves me off the runway on rollout. If I want a plausible start-up to shut-down flying experience, I can still play P3D or FSX. Or FS9, for that matter.

August
Click to expand...
To me, that is like saying, "While I love my wife, if I want sex I go to..." No self-respecting wife will think well of that activity and no self-respecting flight simulator/game should require someone to think of and worst follow your statement. This NOT a reflection on you. It is a SUPER BAD reflection on MSFS that anything from FS9 can be seen as better. Asobo has their X-Box. As the song from Evita said, "The Money with keep rolling in." Time for them to fix this giant zit on the end of their nose. What happened to physics and 1000 points of vector contact?
 
K5083 said:
This is very interesting, but it seems unrelated to the wild swing bug, which is related to rudder effectiveness, not tailwheel steering effectiveness.

August
Click to expand...

I've tested this adjustment in 90 degree 20 knot crosswinds with gusts up to 25 knots in all the editable taildraggers and the tailwheel steering no longer overpowers the rudder before the tail lifts off the ground.
I'm able to make a smooth takeoff on the runway heading after "a little shimmy" (hem-hem!) as the tail lifts. It may not be the perfect solution but it works for me!

Edit: Just tested them again at ROKR Kerama with Live weather: Thunderstorm and 90-degree 27 knots crosswind. Full throttle used straight away in all the planes.
The Savage Cub takes off in no time with no problems. The X Cub needs more runway to build up speed, but is still controllable and takes off heading the right way.
The Pitts, Extra 330 and Cap10 all need plenty of elevator down trim or they try to lift off before even reaching stall speed. There's a bit of weaving about to say the least (I need a LOT more practice at this!) until they reach take off speed but again, they all take off heading the right way.
At no time was there any loss of rudder control, in fact rudder over-control was entirely my own problem due to lack of practice!
 
Last edited:
OK, I may not understand what you are doing and why you are doing it.

What adjustment did you make? Changing those values from 10 and 20 to 110 and 120? Wouldn't that make the tailwheel steering even stronger, and make the tailwheel steering overpower the rudder even more?

Not that that is a problem. Tailwheel steering should overpower the rudder when the tailwheel is planted, and the main way that I keep my taildraggers straight is to keep that tailwheel planted as long as possible. The rudder, in the 2-point attitude, is just not strong enough to counter the bizarre kick to the side - and again, it's unrelated to crosswinds - that the sim gives you at 40 knots or so. (At least in some planes - I agree the Cubs don't really have big problems - but add-on taildraggers, especially warbirds, are a different story.)

I might try your trick to get more tailwheel steering authority. I'll be especially interested in using it with my port-over warbirds, which have some of the worst swing problems. Those steering commands did not exist in FSX/P3D, so port-overs do not have them in their aircraft.cfgs; I wonder what default values they then take. If I add those to my port-overs, maybe I can fight off the swing a little better while the tail is down.

August
 
K5083 said:
OK, I may not understand what you are doing and why you are doing it.

What adjustment did you make? Changing those values from 10 and 20 to 110 and 120? Wouldn't that make the tailwheel steering even stronger, and make the tailwheel steering overpower the rudder even more?
Click to expand...

Not quite - the adjustment is to the speed (in feet per minute) at which the tailwheel reaches maximum control effectiveness. The values for the taildraggers are identical to the values for tricycle (nosewheel) planes, which is clearly incorrect.
What I've done is to raise the tailwheel maximum effectiveness speed to a level which the aircraft will never reach before it takes off - the tailwheel will never have it's full effectiveness on the ground so the rudder will always be more effective. I hope.
 
Huh, that's almost the opposite of the way I interpret those variables. The way I read it, nose/tailwheel steering should be at maximum effectiveness between zero and max_speed_full_steering, then it should decrease linearly to min_avail_steering_pct as you accelerate from max_speed_full_steering to max_speed_decreasing_steering. Then it should stay at min_available_steering_pct at any higher speed. So your adjustment would give you max steering effectiveness at any speed where the tailwheel is likely to be on the ground.

On a slightly different topic, but related, we talked about crosswinds in this thread. A guy just posted an interesting video on the FS forum where he watched the Developer Mode crosswind component readout while taking off. This may be old news to many of you, but I didn't even know about this readout. It shows that there is never any crosswind when you are stationary, and the sim builds it as you accelerate. The crosswind component that this user programmed (20 kts) didn't fully show up until the aircraft was doing 76 kts.


This is, of course, completely unrealistic and is part, but not all, of our side swing problem. The crosswind builds up as we accelerate instead of being constant as IRL, meanwhile our nose/tailwheel steering effectiveness is going down, and the rudder is no use until it pops in suddenly around 40 kts. There's a span where we have no yaw authority of any kind, depending how the values above are set, and are just at the mercy of any crosswind. And then when the rudder effectiveness kicks in, if we aren't already in the weeds, we have the pedal hard over, and violently overcorrect. What a mess.

August
 
K5083 said:
This is, of course, completely unrealistic and is part, but not all, of our side swing problem. The crosswind builds up as we accelerate instead of being constant as IRL, meanwhile our nose/tailwheel steering effectiveness is going down, and the rudder is no use until it pops in suddenly around 40 kts. There's a span where we have no yaw authority of any kind, depending how the values above are set, and are just at the mercy of any crosswind. And then when the rudder effectiveness kicks in, if we aren't already in the weeds, we have the pedal hard over, and violently overcorrect. What a mess.
Click to expand...

Nice found. Yes it could be also that the rudder works ok, but wind it appears out of nowhere and of varying intensity instead of being constant. This causes a completely unreal experience that you can not overcome with absolutely any technique.
 
Yeah, this helps to partly explain it, but I still don't think we're all the way there.

The MSFS crosswind component builds up gradually, according to the video, between 0 and 80 kts. That is NOT what we experience with the veer in the sim. For one thing, the veer occurs whether there is a crosswind or not. For another, it doesn't build up gradually, it kicks in violently at 40 kts or so. If it built up gradually, we probably could learn to handle it better.

I remain agnostic as to whether it is sudden rudder authority or something else that kicks in at 40 kts and induces the veer. To me it is just an "invisible hand." It does not act like it is related to power setting, to rudder deflection, or to wind.

August
 
K5083 said:
Very true. I thought the sudden swing might be an attempt to model torque, but you are quite right that power setting doesn't affect it.

I question whether it is about rudder effectiveness though, because the swing happens even if your rudder is at neutral.

August
Click to expand...

A good point - it reminded my about this thread from the MSFS forum, one that I've linked to before. Short version - user Alec246 did some extensive tests with the MSFS wind tunnel feature in dev mode, and determined that rudder sensitivity is about 10 times what it ought to be. So that - in combination with the tailwheel issues and the crosswind that increases with aircraft speed - seems to contribute to the mayhem. If your rudder is only slightly deflected, it's going to have an exaggerated effect when it kicks in.

Caveat - this thread is a few months old, and I believe the rudder sensitivity was toned down in one of the previous updates - maybe 3 or 4. So it's not as extreme as described. But it still doesn't seem right.

There's also this, about propwash over the tail. Again, its old - goes back to January - and may not be current. But like the one above, it adds one more factor to consider.
 
You must log in or register to reply here.
Back
Top