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

Acceleration compatibility

Ripcord

Ripcord

Messages
735
Country
us-texas
I am using Jim Keir's FSX Mission Editor, in case that is relevant to my question.

I create a mission for the EH101 helo, for FSX Acceleration, and I set the compatibility of the mission to FSX Acceleration. I save it. I fly it. Everything is fine. I see something want to edit, so I go back to edit something in FSXME. I save it, but then I notice that again my mission is set to RTM compatibility -- and it doesn't show up in FSX mission menu.

No errors detected by FSX ME by the way.

What causes this? Is this just a big pain the backside that cannot be avoided? Why can't I simply set the compatibility to FSX A and leave it?

Can anybody shed some light on this for me?

Ripcord

EDIT: I think I will go post this over on Jim's FSX ME forum - I am thinking now that ME is reviewing my mission, not finding any 'FSX Acceleration ONLY' commands or content, and then downgrading it. That's my theory anyway.

EDIT #2 -- why are all the forums locked over at fsaddon.eu?
 
Last edited:
I think your theory is correct. If the content is RTM compatible the mission shows this compatibility tag.
 
OK thanks.

I tried to further test my theory by placing FSX Acceleration objects in my mission, and this seemed to help a little (suddenly my LHA ship was moving at the start of the mission), but did it did not solve the problem of the mission compatibility as expected.

I guess there are some other features in FSX Acceleration that need to be utilized in the mission. Wish I had a list of them, but looking on the FSX A wiki here probably will provide some clues.
 
Checking Compatibility
With the Acceleration Pack for FSX, there are several new types of actions
and triggers available for use in a mission. Of course, these won't work if they
are used with standard FSX. When you create a new mission, it will have a
compatibility level set to the highest supported version of FSX that it can find; if you have the FSX X-Pack installed, it will assume you want to create missions for X-Pack. You can choose to create missions for older versions of FSX by using the “Mission®Set Compatibility” menus.

If you reduce the compatibility level, it is possible for some data to be lost.
For example, if you have used some of the Race triggers provided with X-Pack, or set the “TargetPlayer” attribute which has been added to several actions, and then decide to reduce the compatibility level of the mission then those triggers and attributes would no longer be available. You will see a warning that some things are going to be deleted and, if you accept, any attributes or nodes which require a newer version of FSX than the one you have chosen will be removed from the mission.

When a mission is loaded, the compatibility level is calculated from the
types of nodes and attributes it uses. So, even if you had the compatibility level set to “XPack” when doing some work on a mission, it may show compatibility as being “RTM” when it is reloaded if you haven't used any XPack-specific features. You can always increase the level again by using the “Mission®Set Compatibility” menus.

------------------------------------------------------------------

The above is out of the FSX Mission Editor Manual -- sorry Jim, forgot to RTFM first.

Of course now this does beg the question: which features and attributes truly require FSX Acceleration (eg, X Pack)...?
 
Last edited:
If you have the FSX Acceleration SDK installed on your computer, go to the Mission Creation page and look for the text in red.
 
Brilliant, thank you for posting that. Now I see a handful of items I can add into just about any mission that will make it FSX acceleration compatible and keep it that way.

One would think that since my mission is written for the EH101, which is an FSX-A aircraft, that would be sufficient for requiring that level of compability but there isn't really anything in the mission XML file that specifies which aircraft -- that's in the FLT file, I think. So this helps me resolve the disappearing mission problem, which is a real nuisance.

Ripcord
 
Last edited:
You must log in or register to reply here.
Back
Top