• 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.

Asm2Air param's in AAM

D

dmaher

Messages
141
Country
canada
I realize we can’t use Asm2Air.exe without ESP.
And with AAM we don’t really need it.

But, looking at the Asm2Air sample data file in the ESP SDK, I’m wondering if we can ignore all these extra parameters listed in AAM.
The Asm2Air sample data file is fairly concise.

It seems to me AAM.ini could be edited (for FSX) to reflect the stripped down Asm2Air data sample.
I’d like to see what a complied version of Asm2Air’s data sample looks like in AAM.
Even better, would be a build with all parameters set to 1, let’s say.
Then we could comment out all the extraneous data.
Is anyone here using Asm2Air.exe?

I’m not that familiar with this stuff, but I’d definitely put some time into making an AAM.ini that reflects the ESP sample.


Danny
 
Last edited:
I've used AsmToAir.exe, but I never previously messed with .air files, so I don't know much about the compiled differences. From what I gather, people who've looked at .air files created with AsmToAir in the usual airfile editting tools have gotten confused quite quickly.

Si
 
dmaher said:
I realize we can’t use Asm2Air.exe without ESP.
And with AAM we don’t really need it.

But, looking at the Asm2Air sample data file in the ESP SDK, I’m wondering if we can ignore all these extra parameters listed in AAM.
The Asm2Air sample data file is fairly concise....

Danny
Click to expand...

This is correct. AAM.ini is full with old and no more needed sections. And yes, it would be easyl possible to stripe it down to the FSX or ESP standard.
Otherwise AAM is aimed to all FS and CFS versions since FS98 and needs all this old stuff.
But this don't really matter. If you open a true and clean FSX air file (like the stock aircraft), you see and can edit only the FSX sections. AAM don't show the sections that are not included in the specific AIR file.
 
Thanks Sergio, I see what you mean.
And, I’m using the FSX Mooney_Bravo.air as a template.
I can see how the important sections correspond to PistonSample.asm
So, there’s no difficulty proceeding.

There are certainly a few extra empty fields in Mooney_Bravo.air, labeled FS2002 and so on.

Like:
1101 Primary Aerodynamics / Flaps Cycle Time - It’s clearly labeled as FS2002.

In the AAM edit UI, I cannot delete an individual empty parameter (Flaps Cycle Time)… only an entire section (1101)
This makes sense…the address is still part of the table – even if it’s not used. (?)

For my own purposes I think I’d like to start stripping the comments for empty pre-FSX fields.
- Making an FSX only ini.

Like:
Code: 
7=0C,double,Flaps Cycle Time (sec)
7h=Since FS2002 defined in AIRCRAFT.CFG, section [flaps.#]

To:
Code: 
7=###
7h=###

Would doing this cause an error in the new airfile once it’s saved?
I’ve tried it and it seems to work…but I’m not certain the new airfile is working 100%

Danny
 
Just to follow up, I did compare ESP/PistonSample.asm and FSX’s Mooney_Bravo.air in AAM.
Nearly everything corresponds – as Sergio pointed out.
There are just a few extra fields in record 1101 Primary Aerodynamics.
(and 1199 PID controllers for AI – which I ignored - looks like a total mystery to me )

So I removed all empty AAM fields that didn’t exist in ESP’s sample.
And reordered the rest to reflect PistonSample.asm
There were three fields that that contained data in Mooney_Bravo.air but weren’t listed in ESP’s SDK - So, I left them.

-Airframe Type,
-Fuselage AoA at Min Induced Drag,
-Cn_? Yaw Moment - ??,

Editing the ini certainly wasn’t necessary, and may cause some major problems, but at least I can see how this stuff corresponds to ESP which is the only official info MS published (AFAIK). Mostly it’s just an exercise to get my head around a lot of stuff I don’t understand ;)
 
Last edited:
You must log in or register to reply here.
Back
Top