• 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 Visual Model Origin (VMO)

Messages
217
Country
azerbaijan
I have attached two images showing wire-frame views of default C172, and C182Q by Carenado. Both snapshots are taken from ModelConverterX. No further operation applied to models other than import to MDLCX; i.e., the original locations of models on MDLCX grid area are preserved.

Am I right in thinking that the crossing point of red grid lines marked with red dot is Visual Model Origin (VMO)?!? I guess so since for C172 the crossing point of grid lines seems to rest just on 1/4 distance from the root chord as specified by FSX SDK (even though for Carenado model this point is moved to the center of the chord).

Thank you!
 

Attachments

  • c172_default.jpg
    c172_default.jpg
    193.8 KB · Views: 828
  • c182q_carenado.jpg
    c182q_carenado.jpg
    200.8 KB · Views: 734
Yes, that red dot at the intersection of the grid lines is the VMO point.

One of the most misunderstood things in FS development is the way that the aircraft.cfg parameters are actually supposed to be used.

Most people (strangely enough including ACES!) opt out for the simple approach and simply set the VMO in the model to be congruent with the 1/4 chord MAC position, then leave these two parameters at (0,0,0):

reference_datum_position = 0.0, 0, 0 // (feet) distance from FlightSim Reference position: (1/4 chord, centerline, waterline)
empty_weight_CG_position = 0.0, 0, 0 // (feet) longitudinal, lateral, vertical distance from specified datum

NOTE: FlightSim Reference position = VMO point, not the 1/4 chord, centerline, waterline. That is only true for the lazy modeler, and is very misleading!

However, it does not have to be this way! In fact, with some airframes it simply doesn't work out at all. You see, the sim's Spot View camera uses the VMO point as it's anchor reference. In the case of a very long airframe with a 1/4 chord MAC point too far forward, the tail of the fuselage/vert stab will be off-screen entirely from side views. IOW, it appears off-center from the Left/Right camera's POV.

This is why when developing a new model, it's important to set the VMO point to a position that is 1/2 the total length of the aircraft's side profile view...

...then use the above parameters to adjust the reference_datum_position and empty_weight_CG_position correctly!

The "key" is reading the description of the e_w_CG_p description. It is referenced as an offset from the ref_datum_pos.

So, set the ref_datum_pos to wherever you like (it's an arbitrary point). I usually pick the nose of the a/c for jets and the tip of the spinner for single engine GA, then set the e_w_CG_pos as an offset back to the 1/4 chord MAC position.

Note carefully that all other x,y,z points are also offsets from the ref_datum_pos as well, so all y values are now negative numbers!
 
Last edited:
Thank you, Bill!!!

One more question for clarity sense... If I understood you correctly, if VMO = FS Reference (a.k.a "Center") Position, then basically the following assumptions are true (pls refer to below example and attachment):

# RDP is 4.67 feet forward (positive) of VMO
# Station Load (SL) is 3.18 feet aft (negative) of RDP since all aircraft components and weight distributions in aircraft.cfg are (quote from SDK) "offset relative to datum reference point". IOW, the particular station load is offset from VMO by RDP - SL = 4.67 - 3.18 = 1.49 feet forward. {Although scaling is NOT observed on the attached image} :)

reference_datum_position = 4.67, 0, 0
...
...
station_load.0 = 218.4, -3.18, -0.82, 0

Correct?!?
 

Attachments

  • c182q_carenado_update.jpg
    c182q_carenado_update.jpg
    208.3 KB · Views: 675
Last edited:
That is correct. I mistyped in my post "positive" when I meant "negative." I was distracted while posting by a IM conversation...

I've now corrected my mistake so as not to mislead anyone else.

Note that Carenado could have moved the RDP to the tip of the prop spinner, instead of the leading edge of the wing.

If we are lucky enough to have actual prints from the manufacturer, we would find that in actual practice their reference datum point is hovering in space some feet ahead of the airframe entirely! As I said, it is a completely arbitrary point from which all dimensional measurements are referenced.
 
Last edited:
Thanks again!

Does FS flight model has a capability to calculate ("adjust" is a better term, I guess) its reference position in case of developer's "failure" to do so?

On a side note, I absolutely agree: we - poor souls - are mostly unaware of what's happening behind the curtains... And there is no recourse but to hope that a developer is wise enough to follow the "rules of the game", to say the least. :)

Cheers,
 
Last edited:
Unfortunately, no. If the model's VMO is incorrect, there's nothing ordinary users can do about that.

Luckily however, the rest is fixable via the config file parameters.
 
Using GMax I normally position the aircraft so it looks OK relative to the GMax origin (0, 0, 0) - approximately 1/4 chord for an unswept wing.

I experimented some time ago by moving the aircraft model 10m aft from the GMax origin and exporting it. I left the .cfg file unchanged.

In flight the aircraft pitched about the GMax origin - a point 10m ahead of the model. It was very obvious visually.
 
Bill,

If what you say is true, the 'empty weight' location is then the actual CG, center of gravity/mass. Is this so?

I had been working on the assumption that the reference datum was actual CG. :S



Bill
 
The "empty weight" location is the CG, and even that is a moving target.

The reference datum position on a real aircraft has, generally, nothing to do with the "CG". In some cases it's not a real solid "point".

For an Aviat/Pitts S-1S, the Datum point is "65.06 inches forward of lower wing leading edge" (Per FAA Type Data Sheet N0. A8SO)

C.G. Range is at "+67 at 970 pounds or less" ; +65 to +66 at 1150 pounds...

For convenience sake, many of us do place the reference datum position at the 1/4 chord position, and call that the "empty weight" and C.G. position.




Bill,

If what you say is true, the 'empty weight' location is then the actual CG, center of gravity/mass. Is this so?

I had been working on the assumption that the reference datum was actual CG. :S



Bill
 
The CG is based off the pilot/passenger location, fuel tank location, engine location, wings/tail location and the CG entry. So it based off of everything just like in the real world.

I usually place the CG at something like 0.3 and -0.3 empty or 0.5 and 0.0 empty. Then just place the aircraft location in Gmax to the real world CG near the leading edge of the main wing. This works good for camera positioning as Bill mentioned.

My 2 cents!:stirthepo
 
Last edited:
The precise hierarchy of the various x,y,z coordinate parameters is very rigidly defined by FS, but really very simple:

Code:
VMO (model's visual center 0,0,0)
|___ Reference_datum_position (arbitrary x,y.z as an offset [U]from[/U] VMO)
     |___ Empty_weight_CG_position (defined as an offset from reference_datum)
     |___ All [U]other[/U] x,y,z coordinates (defined as an offset from reference_datum)

As I mentioned previously, it is obvious that if the modeler leaves the reference_datum_position defined as congruent with the VMO, then it appears as though the empty_weight_CG_position is defined by the VMO, but it really is not!
 
Back
Top