• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX Winglet data

Messages
77
Country
unitedkingdom
Hi all,

A quick question. I've been told by a source that various wing lets lines can be added to the [airplane_geometry] section of the aircraft.cfg file.

I've looked through the SDK documentation and cannot find any reference to them, even done a Google trawl and looked at the ESP online SDK docs too. Am I being lead up the proverbial garden path?
 
Last edited:
Even if you could enter them I doubt they'd have any effect. The FSX SDK .cfg file section states:

[airplane_geometry]

This section has been added mainly for reference. Although you can edit these values by hand here in the aircraft.cfg file, modification of some of these variables will have little to no effect on airplane performance, as the flight model aerodynamic coefficients are all located in the .air file.
 
Even if you could enter them I doubt they'd have any effect. The FSX SDK .cfg file section states:

Mgh,

You should learn to take all of the documentation with a grain of salt and test test test everything on your own.

[airplane geometry] entries absolutely OVERRIDE the air file entries. Are they needed? No, but you could say they never were needed. There always has been more than one entry for any given item.

That being said, I recall an Avsim post where you claimed your testing revealed that CG changes and wing apex changes had no affect in the sim. Be careful to understand how things work before making those kinds of assumptions. Had you known that wing_apex only changes aspect ratio and Center of Lift offset is attached to CG until it is changed in the airfile, your results would have been different.


orb505,

I doubt they work, but the only way to be sure is to test test test thoroughly! I've never heard of them before. Regardless, induced drag is not correct in the sim anyway due to the wave drag bug and the silly Cdi formula. I think you would be better off tuning overall Cdi to match your aircraft without using the winglets flag.
 
Mgh,

You should learn to take all of the documentation with a grain of salt and test test test everything on your own.

I have experimented and reported my results in these forums and others have confirmed them. In FSX many of the [aircraft-geometry] variables have absolutlely no effect for the reasons given in the SDK
 
That post proves the point I was making. Incorrect assumptions that don't take everything into consideration are pretty useless.

First and foremost, all references to a given value must be removed from the airfile before removal from the config file, or the results will not be as expected. All variables in the airfile are backwards compatible! FSX reads every table that ever existed from FS2002 through P3D.

Second, one must understand that MSFS flight models are modular, and your assumptions about what something should do should keep this in mind before determining something as ineffective. Modular means that if elevator lift is zero, but elevator moment is 1000, you will still have elevator response and your assumptions about any test results will be wrong. If wing_apex is moved, which changes wing shape and rightfully, CG% MAC, that doesn't automatically mean the wing pitch moment will change. The relationship between CG position (which can only be changed through weight) and Wing Center of Lift need to change for aerodynamic effects to be seen.


We must understand the inter-dependencies before assuming a valid test!!!!!!!!



For example:

mgh said:
I carried out a test to try to understand which values in aircraft.cfg are used and their defaults. I took the default FSX C172 and commented out the entrries in [geometry] from wing_dihedral to vtail_pos_vert inclusive.
I compared times and speed to take-off and to 2000 ft with the original .cfg file and the modified one. There were no significant differences.

See above. Zero out all control moments, then set CL_xx values as appropriate (default FDEs are no where near appropriate. You will have to do the math to find the lift pounds that will create the desired moment at FULL deflection, then set this coefficient accordingly. I believe there is a simplified formula floating around for that...). Now set the geometry correctly in one test case and incorrectly in another. You will see a difference. Be sure you have removed all control surface, geometry, and moments from the airfile; however do not zero out the deflection tables such as 517-519 or equivalent. They affect the deflection of the surface itself, and without deflection you will only produce a constant (uncontrollable) lift force from each surface.

As for the wing_xxxx variables, they mostly affect computational things, not actual wing dynamics.

Those variables, (wing: chord, area, sweep, and apex) are used to find aspect ratio that is applied to find induced drag. There is no aerodynamic effect seen on the wing coefficients other than lift and induced drag. They do affect the calculation of wing center of lift in the absence of table 1534, but I highly recommend setting this manually.

Wing: chord, area, sweep, dihedral, and apex also affect the calculated CG MAC position. They don't affect CG lift balance, because that is controlled by the Center of Lift to empty CG relationship. What affects the pitching moment of a wing is the Center of Lift distance from CG set in 1534. In a properly designed airfile, the CG distance from the static Center of Lift for a given CG%MAC charted on the real aircraft, will match the MSFS CoL to CG distance at the same FS indicated CG%MAC.

Wing_dihedral affects the MAC height. Dihedral + wing_vertical_position is how the sim finds the MAC height, and if needed the CoL height.



mgh said:
Incidentally, I've done a further experiment when I eliminated everything in the aircraft.cfg file from wing_root_chord to rudder_area inclusive. FSX calculated wing_root_chord as wing-area divided by wing_span, set control surface areas to zero, and set other default values as before. Despite this the C172 still flies and manoeuvres!


You can (and I have) designed an MSFS/P3D aircraft with NO CONTROL MOMENTS, that is controlled by lift only and vice versa---100% moments, 0% lift. This will absolutely affect your test results. You don't even need the surfaces if moments are set.

Remember I said it's all modular? Well, moments affect moments (trim position etc), but not AoA, while lift affects AoA but not moments. Lift and Moments are summed onto the airplane.


mgh said:
Given that FSX creates returns these default values, I shall need hard evidence to convince me that it also uses another set of default values internally.

You are correct, it doesn't use default values. It will either read the legacy tables (they all work for backwards compatibility), or if not present, produce ZEROS. Zeros are a valid parameter in the sim. If you set your CL table to 0 it wont fly. But if you set your control surfaces to zero without first zeroing out your moments, it will still respond to control inputs.


Again,

We must understand the inter-dependencies before assuming a valid test!!!!!!!!


But let's add,

We must understand the proper way to achieve the desired results!!!!!


There's always been a ton of debate about things like wing_sweep having no aerodynamic effect. Why would it be needed? The aero effect of a swept wing is modeled in the lift table, cm versus mach table, cm versus AoA table, and the wave drag versus mach table. The actual wing_sweep variable only affects induced drag. It has no effect on the wings performance.



I would say this point brings me back to the original post here. Do those variables have any effect? Without testing, who knows....but who really cares. Everything you need to custom model winglets is already provided in a modular format.
 
It's really quite straightforward. The coefficients in the FSX .air are for the complete aircraft. All that's required to calculate forces and moments is one reference area and one reference length. There's simply no need for any other dimensions such as htail_area, htail_span, htail_pos_log, etc.
 
Surely an easier way would be to simply adjust drag coefficient. As that is all winglets actually do. They don't "create" lift as many people think. They jst reduce drag.
vololiberista
 
As that is all winglets actually do. They don't "create" lift as many people think. They jst reduce drag
You're correct and they only act on induced drag. The only parameter in the aircraft.cfg file that seems to fire this CDi decrease is [wing_winglets_flag=1]
Yves Guillaume found out from SIM1.DLL analysis how to calculate the amount of decrease of CDi related to this flag. I presume Yves will include it in his next revision of his review of FS dynamics internals. Note that from the tests I performed wing_sweep has no measurable effect on induced drag (at least in FS9 & FSX); the same is true for other airplane_geometry parameters I investigated, apart Oswald and calculated aspect ratio.
 
One way to approximate the effects on induced drag would be to calculate a new aspect ratio on the winglet increases wing area by its own area and wing span by its own span then change the Oswald factor in proportion
 
One way to approximate the effects on induced drag would be to calculate a new aspect ratio on the winglet increases wing area by its own area and wing span by its own span then change the Oswald factor in proportion


This is the best way. Don't use the winglets flag... All winglets perform differently. However I would suggest looking at the change to the drag polar and starting your calculations from there.

It is a pointless discussion however, because of the huge Cdi bug. Why they haven't corrected this is beyond me. The math is only about three easy steps to calculate true Cdi for any installed wing. They coded about three steps for a method that is only accurate at one speed. How many aircraft out there fly at only one speed???
 
It is a pointless discussion however, because of the huge Cdi bug.

Is there a workaround for this? I've had to manually tune my CDi calculation, but it still doesn't match exactly what is shown in AFSD.
I wonder how it's calculated in AFSD...
 
I wonder how it's calculated in AFSD...

Depends on the version you use..Since a long time, the way FS calculates CDi was unknown. More recently, it was cleared up by YG (see his document and the use of LinCLAlpha and ZeroLiftAlpha in Appendix). Effect of winglets was more recently modelized. So, by now, AFSD provides 2 values for CDi

1) an experimental one (labelled as true measured CDi from EOM) that is derived from true total CD calculation from aerodynamical equations derived from Roskam (Airplane Flight Dynamics and Automatic Flight Controls, Part I, that FS uses - see Zyskowski paper and references) from which all other drag components are subtracted (parasitic drag, wave mach drag, flaps, gear also taking into account possible aircraft.cfg scalars). Should be the standard reference value

2) a "theoretical" one (labeled in AFSD as FS CDi estimation) calculated from YG equations that are
CLc = (AoA - ZeroLiftAlpha)*LinCLAlpha + CLflaps
CDi = [CLc*CLc/CDiK] - WingletsEffect
with CDiK = AR*Oswald*Pi

During my recent tests (since AFSD version 4.10) both values fit well (within 0.00005) except in some unsteady situations
 
Is there a workaround for this? I've had to manually tune my CDi calculation, but it still doesn't match exactly what is shown in AFSD.
I wonder how it's calculated in AFSD...

Yes and no.



I wonder how it's calculated in AFSD...

Hervesors is correct about AFSD.

If you need to know how FS works, there are three valid ways to calculate FS CDi as long as all the inputs are correct in the airfile.


1) by linear CL: [(Current AoA - 0CL AoA) / (1.0CL AoA - 0CL AoA)]^2 * (FS CDi constant/65536)


2) by CDi constant: [(Current AoA - 0CL AoA) * (1 / (1.0CL AoA - 0CL AoA) )]^2 * (FS CDi constant/65536)


3) by pi*AR formula: [(Current AoA - 0CL AoA) / (1.0CL AoA - 0CL AoA)]^2 / (pi*AR*e) <<<< EDIT: See next 2 posts for clarification.


FS uses #3. They all yield the same results unless FS CDi constant as set in the airfile does not exactly match 1 / (pi*AR*e) including decimal rounding errors from shortening pi, e, or AR (which the airfile will shorten to some preset number of decimals).

Also, there are some misconceptions that FS draws an extended linear line to find CDi AoA. It doesn't. It is much simpler. (Current AoA - 0CL AoA) / (1.0CL AoA - 0CL AoA) yields a percentage. FS simply applies that percentage to the CL 1.0 CDi constant value used in the CDi formula.


The live FS process is:

- Figure percentage of CL 1.0 to CL 0 AoA range
- Apply percentage^2 to CDi formula
- Apply result directly to CDi

*Flaps just simply change both the positions of CL 1.0 and CL 0. The result will usually cause the percentage to be much higher.


The problem with this method is it will only output accurate CDi at exactly one Mach speed. A real aircraft produces higher CL at lower AoA with higher Mach (and hence will stall at much lower AoA). Scaling the CL factor versus Mach table does not change the alignment of properly. It factors everything up/down by multiplication. A real CL chart slides down and steepens. To compound the problem, the changes in CL aren't added to the CDi calculations, and CL 1.0 is not reduced (like it is with flaps) to realign the percentages. Normally, CDi will increase as the CL increases.




The third bug in the calculation is the fact the the Mach drag table only adds to CD parasite. It should be added to both in order to account for the trim load on the wing. So not only does the CL increase with mach, but there is an additional load imposed on the wing (which requires even more CL) due to the need for Mach trim. This could have been best modeled in a CDi versus Mach table. Either way, it is presently unaccounted for.





Is there a workaround for this?

The model pitch needs to be animated to reduce pitch with Mach, while the CL Factor versus mach table MUST remain at 1.0. If the CL chart, and all the CDi inputs are correct, the sim will produce very close to real CDi.
 
Last edited:
Also, there are some misconceptions that FS draws an extended linear line to find CDi AoA. It doesn't. It is much simpler. (Current AoA - 0CL AoA) / (1.0CL AoA - 0CL AoA) yields a percentage. FS simply applies that percentage to the CL 1.0 CDi constant value.

Not sure about that Jx_..seems FS LinearCL alpha is indeed build from CL at AoA=10° to CL at AoA=0
By chance here, we can check that by
1) Calculating it from the CL vs AoA table
2) And comparing it to the LINEAR CL ALPHA SimConnect variable
They are always the same when this range is used, even for highly non linear tables. However I will try your suggestion (CL1 to CL0) and let you know the results of the comparison unless you already have experimental measured data

The table 1101 entry is there to account for whether your lift charting method includes wing incidence or not

I couldn't see any influence of any parameter of 1101 record on "measured" CDi..here I'm speaking of "experimental" measured CDi. Do you have experimental data regarding that ?
 
Not sure about that Jx_..seems FS LinearCL alpha is indeed build from CL at AoA=10° to CL at AoA=0

Looking through my notes, there is a discrepancy in the post. Thank you for pointing it out.

AoA0 to AoA10 is used to find the linear slope (rate of change) but 0 CL to 1.0 CL is used from the linearized line. It's the same formula, but I failed to make that really important point clear.

So it is the virtual 0CL to virtual 1.0 CL, not table 404 CL0 to CL1.0. Upon checking the math in your post, they appear to be mathematically the same or close, just different methods. I'm not sure if rounding errors will be better with one or the other.


Amend the steps in formula #3 as:

[(FS AoA - AoA at Linear Zero CL) / ( AoA at Linear One CL )]^2 / (pi*AR*e)


So in practice this looks like:

CL at AoA 10 = 1.05
CL at AoA 0 = 0.15
difference = 0.90
Linear alpha rate per degree = difference / 10 = 0.09

AoA at Linear One CL = CL1.0 / Linear alpha rate per degree = 1 / 0.09 = 11.1111111

AoA at Linear Zero CL = CL at AoA 0 / linear alpha rate = 0.15 / 0.09 /-/ = -1.66667


As you can see in this case, the range is 12.7777 degrees, and FS would apply the percentage^2. ( N degrees / 12.7777 )^2

It would have been much easier if they would have just used CL^2....


Table 1101 and 1204 discussed above apply to the FS nav log and minimum_drag speed gauge variables.


Here is the CDi formula above in excel format. It usually remains accurate when the experimental value in AFSD gets confused:

=( (B11 - (B17 / ((B18-B17)/-10) ) ) / ( 1 / ((B18-B17)/10) ) )^2 / (PI()*B12*B13)

B11=Current AoA
B17=CL@AoA0
B18=CL@AoA10
B12=AR
B13=e


hervesors said:
I couldn't see any influence of any parameter of 1101 record on "measured" CDi..here I'm speaking of "experimental" measured CDi. Do you have experimental data regarding that ?

The CDi constant in table 1204 and min induced drag value in 1101 gives the value used in the nav log and gauge drag variable calculations. That shouldn't have been included in this CDi discussion. My mistake. I've bolded or corrected those mix ups.
 
1204 is marked as OBSOLETE_AIR_WING_SPECS... in case anyone's wondering why they're not in any FSX aircraft.
 
1) an experimental one...

2) a "theoretical" one (labeled in AFSD as FS CDi estimation) calculated from YG equations...

During my recent tests (since AFSD version 4.10) both values fit well (within 0.00005) except in some unsteady situations

Thanks for the reply Hervé -

I'm seeing two very different values in AFSD for CDi between the "experimental" and the "theoretical" estimated CDi. The latter, using YG's methods I've been able to calculate - and it gives me the same numbers that AFSD shows for estimated FSX CDi. I wonder why the two values are so different.
 
Thanks for the reply Hervé -

I'm seeing two very different values in AFSD for CDi between the "experimental" and the "theoretical" estimated CDi. The latter, using YG's methods I've been able to calculate - and it gives me the same numbers that AFSD shows for estimated FSX CDi. I wonder why the two values are so different.

Maybe the second model that doesn't match your calculation is based on CLwing directly, or CL total that includes elevator lift too. All these CL are different and could lead to signficant difference of CDi
 
I'm seeing two very different values in AFSD for CDi between the "experimental" and the "theoretical" estimated CDi. The latter, using YG's methods I've been able to calculate - and it gives me the same numbers that AFSD shows for estimated FSX CDi. I wonder why the two values are so different.
Humm..unusual. Could be related to the model and will require further investigation. Will contact you privately for performing some tests with you

Maybe the second model that doesn't match your calculation is based on CLwing directly, or CL total that includes elevator lift too. All these CL are different and could lead to signficant difference of CDi
It is based on linearized wing CL alone as described in the equation
 
Back
Top