Hmmmm, interesting! I wonder how OlyRick is making out. Frankly I've never heard of this as an issue without it being controller calibration or those same Realism settings we've suggested here. Rick?

Surely the weather-vane stablily is determined by Cn-beta (yawing moment due to sideslip) in the .air file. The balancing rudder effect is determined by Cn_dr (yawing moment due to rudder deflection)? Changing their ratio should enable sideslide to be held.The real problem is that there isn't Cd-beta (change of drag with sideslip) in the .air file. The reason for this, I suspect, is simply lack of data. Values just just aren't generally available.

To be brutally honest, I think most pilots would agree that FS is pretty poor at depicting a slip, sure you can cross the controls, but there is nowhere near the same spin risk when doing it in FS, nor does an FS aeroplane lose anywhere near the amount of altitude a real slip produces.Al

To be brutally honest, I think most pilots would agree that FS is pretty poor at depicting a slip, sure you can cross the controls, but there is nowhere near the same spin risk when doing it in FS, nor does an FS aeroplane lose anywhere near the amount of altitude a real slip produces.Al

looking into the .air file there aren't the necessary varables to model a spin properly. But, as I just said, I doubt that data is available.

Hmmmm, interesting! I wonder how OlyRick is making out. Frankly I've never heard of this as an issue without it being controller calibration or those same Realism settings we've suggested here. Rick?

I have tried all of the suggestions re: calibration and realism settings that have been offered in this thread without success. As noted, I am flying the A2A Cub, which is reputed to model the slip accurately in FSX. It is really frustrating to see the rudder and rudder pedals move through the full range of motion without being able to stop the turn in the direction of the bank and maintain the forward slip.I wonder if the problem could be with a corrupted file in FSX. Since I cannot get sufficient rudder with either the CH pedals or the keyboard, I would think that this points to a software problem, not a hardware problem. This is why I did a complete uninstall and subsequent clean reinstall of FSX. Is it possible that I may have missed deleting a file, or could there be a problem in the registry? Perhaps Rob can offer some insight, since he is well-known for designing FSX aircraft that can forward slip.I am open to any suggestions on this. I am anxious to get back to flying the A2A Cub and following the course of instruction in, Microsoft Flight Simulator for Pilots: Real World Training.OlyRick

The default FSX Piper Cub has:Cn_beta = 0.03417Cn_dr = 0.02343You could use an airfile editor to change Cn_dr to increase rudder effectiveness: perhaps doubling it the first case to see what happens.

To be brutally honest, I think most pilots would agree that FS is pretty poor at depicting a slip, sure you can cross the controls, but there is nowhere near the same spin risk when doing it in FS, nor does an FS aeroplane lose anywhere near the amount of altitude a real slip produces.

Agreed... as far as forward-slipping goes.On that topic, a side-slip can be visualized as a method for transistioning from a crab on final(a crab is not a slip). All things being stable, a side-slip is an approach where you're aircraft is not only on a runway track, but on runway heading too... with the upwind wing lowered for the duration of the approach. It's a prefered method for x-wind landing, IMO (as opposed to "kicking" the nose into alignment before touchdown), because you land with the ailerons already set "into" the wind for the roll-out.Side-slip realism too, is a bit unrealistic in FSX.. but I can get past that, because it's a dynamic event. I don't stop to think if the rudder/aileron crossing proportions are realistic.. I just use the old rule.. ailerons to keep on runway track, rudder to maintian runway heading... It's just in FSX, you cannot initiate a side-slip as far out as you can in the real-world.. you run out of either, or both, control delfections.. :( The forward-slip is horrible in FSX (prob for the same reasons you cannot hold a long side-slip). Sometimes, it even feels like a forward-slip LENGTHENS your approach :( I think this calls for an XML gauge that reads throttle-posistion, and the proportion of control-crossing, and deploys something like an invisble, proportional speed-brake. That would eliminate the compromises in air-file/cfg-file tweaking..

but with a, say 020deg wind on rwy 36, then we might simply crab - rt rudder (into the breeze), a touch of left aileron, and simply slip down the glideslope

A crab is simply a heading needed so that the track equals the course... no different on an approach, than in level flight. Once you apply countering control surfaces, it becomes a slip...

OlyRDid you happen to ask Bob Church about the problem?This is quite an interesting discussion: http://forum.avsim.net/topic/58747-side-slipping-in-fsx/It might be worth trying the procedure with a realair plane! :( RegardsPeterH

..just to add to the discussion, re slips.. there are skids out there, too, and as mgh rightly asked (in his original reply) - "What do you mean by a 'forward slip'?" and noting Brett's "a side-slip is an approach where you're aircraft is not only on a runway track, but on runway heading too... with the upwind wing lowered for the duration of the approach" - while correct in this context, it is only one part of a whole slew of turn coordination practices - and malpractices. One of the most unusual exercises to try is a flat, 360 deg. turn. I haven't tried it in the A2A Cub - it should do it - there's not a lot of dihedral, and (like RealAir) A2A has got the rudder to actually do something to the yaw axis. Anyway - here's a pretty detailed real-world account of what one can achieve by pushing pedals, and why! :(

The default FSX Piper Cub has:Cn_beta = 0.03417Cn_dr = 0.02343You could use an airfile editor to change Cn_dr to increase rudder effectiveness: perhaps doubling it the first case to see what happens.

This might be worth a try if it is not too complicated as I don't think it will solve the root cause of the problem. Please recommend an airfile editor. What is the name of the file that contains this information for the FSX Cub?OlyRick

OlyRDid you happen to ask Bob Church about the problem?This is quite an interesting discussion: http://forum.avsim.n...lipping-in-fsx/It might be worth trying the procedure with a realair plane! :( RegardsPeterH

I sent Bob Church an email but have not yet heard back from him. I am having trouble posting to the CH Hangar Forum and am waiting to hear back from the forum admin.I would like to buy a RealAir plane but don't want to do so until I have a better handle on the problem.I appreciate your keeping attention on my problem.OlyRick

You can use a free editor called "Air Update", Oly, which produces a text file, or you could purchase the GUI version called "Air Wrench", by Gary Beckwith. Get either here.

In my opinion ther best airfile editor by far, and the easiest to use, is Aircraft Airfile Manager. It's free and available here http://hsors.pagespe.../fsairfile.htmlThe root cause of the problem is that FSX does not have a variable that relates sideslip to drag (Cd_beta?) The main reason for this is that there's no real-world data available relating to what value it should have. The same problem applies to spining. A light aircraft in a in a fully developed spin can have an angle of attack of 43 + 2 ^o sideslip of 3 + 11 ^o, and be rotating at 152 + 32 ^o/sec about an axis 4.9 ft from the centre-line. (Page 27 of http://ntrs.nasa.gov..._1987007382.pdf) Aerodynamic data to model that situation is not, repeat not, available.

In my opinion ther best airfile editor by far, and the easiest to use, is Aircraft Airfile Manager. It's free and available here http://hsors.pagespe.../fsairfile.html

Many thanks for the AAM links, mgh. I think you're right - at first glance it looks to be very comprehensive, and will take some study effort (I'm not too quick).