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

Common Mission Mistakes

jimkeir

jimkeir

Resource contributor
Messages
93
Country
unitedkingdom
Hi,

Simple question; what do people think are the most common mistakes that make FSX barf when loading a mission?

Cheers,
Jim
 
Hi Folks

Jim -
These are the more common errors I'm seeing,
not nescessarily things that make FSX barf.

Your starter for 10

Multiplayer Missions

Triggers -
ObjectFilter is set to User
but OnEnterFilter or OnExitFilter is set to 1 or more players.

PylonRacePoint -
PenaltyHeight must be > 0.



General

Cameras -
ObjectReference has no reference.

Thermals -
Model Category is not set.
AirObjectModelGuid is not set.

Triggers -
Everything. :banghead:



HTH
ATB
Paul
 
Last edited:
Proably the single most common mistake:

Proximity Trigger with no Area defined.

Second most common:

Deleting anything (resulting in dependency issues porking the sim).
 
Ditto on the trigger and forget the defined area. There must be a few others, but I have never figured out what I did wrong :)

I just learned to add as few things as possible, then save and reset to see if the mission still works. If I try to do to much without testing it NEVER works :)

Gunner
 
Property trigger with no action - good one. Sometimes, I'll throw in a bunch of triggers and forget to add an action to one of them - crash. Sorry - barf! :D

I'd have a whole different list though, as most of my missions are written in xml when I'm away from FSX. Things like dialog action GUID doesn't match the one the property trigger calls for, etc. D'OH!
 
Good stuff, keep 'em coming! Hopefully this will be useful to people.

Paul, I didn't know that the AirObjectModelGuid of a thermal was compulsory?

Thanks,
Jim
 
Hi Folks

jimkeir said:
I didn't know that the AirObjectModelGuid of a thermal was compulsory?
Click to expand...
Jim -
It might not be.
It's just one of the common errors I'd seen recently
when assisting others with their non-working missions.

ATB
Paul
 
Last edited:
Now this one is quite tricky:

ProxTrigger with Condition, later deleting the condition - leaves a blank condition entry in the xml, which has to be deleted manually if you want the mission to load at all. :D
Took me about 2hrs of worktime to find that error...
 
Okay, here we go.

I made a huge XML manually and it didn't show up in the missions list. So, I split each trigger section into it's own XML and then tried each one individually. After about 3 of the 18 I had split it into, I decided to look through the file in detail. As each one dealt with Adjust Payload Actions, I noticed that I had failed to include a station index for each of them!

That was enough to keep the mission from functioning at all.

GOOD! :D
 
You must log in or register to reply here.
Back
Top