Here's a list of "gotchas" from fsxmissionshangar.com. Check it out for many more tips.
- Unlike Property Triggers, conditions associated with a Proximity trigger are STATIC. i.e. If conditions are NOT met when entering Area Definition, then trigger does NOT fire, even though conditions are met later while still in the Area.
- When reverse engineering Trigger Conditions, ALWAYS check your ObjectReference in the XML file FIRST! If you open the Condition Editor, your ObjectReference will ALWAYS automatically change to USER. Thus IF a triggering object, other than USER, was specified, then you will never know it, assuming you do a "Save" after closing the window!
- If you have 2 PxTs (1shot) associated with the same RA and set for different conditions, either trigger firing will disable the other. This can be rectified by reactivating BOTH PxTs AND the RA, with the firing trigger. Setting both triggers for multi-fire will also solve this problem.
- Take particular care with PxTs AFTER they are written. Entering the window panes to inspect "Conditions" or "Actions", will write "empty" header and trailer to your xml file. IF you then save your mission, these empty header/trailers are saved, which WILL prevent your xml mission file from loading.
To correct, simply delete:
<OnExitActions>
</OnExitActions>
and your problem is solved!
- Entering a RA, whose PxT is deactive, will trigger firing when PxT is reactivated, IF object is inside the RA.
- However, the opposite does NOT occur...Exiting a RA, whose PxT is deactive, will NOT trigger firing when PxT is reactivated, even though object remains outside of the RA.
- When referring to an AI Object in the Condition Editor as a String, make sure your string is EXACTLY as specified in the title on the SimObjects\folder\sim.cfg file. It IS case-sensitive!
- Note also that Setting an AI Object as the ObjectFilter works fine, provided that AI Object is NOT the SimpleObject type!
- To trigger a PxT with a SimpleObject (e.g. A droppable Object), you MUST set the ObjectFilter to "Anything", then denote the ObjectName as String for "Trigger" and NOT "User" in the Condition Editor! Also RHS ObjectType must be "String".
- Note also that a PxT will NOT fire IF you are already INSIDE the RA when you drop the object. Thus consider the RAs height and the Players altitude when using the "On Enter" condition.
- Each Proximity Trigger is associated with an Area Definition, aka Rectangular Area (RA). This RA may either be fixed to a location or attached to an object.
When attached to an object, you may specify an offset from the object (in meters) defined by X, Y, and Z axis; where X is Port- to Starboard+, Y is Bottom- to Top+ and Z is Aft- to Forward+. Two of these Axes centers intersect with the aircraft's center of gravity (COG), the 0 position for x and z ONLY. 0 for y,(or height), IS 1/2 the y distance ABOVE the COG. To center the y axis with x and z, you must specify an offset = to -0.5 multiplied by the RA's y distance.
Note also that when attaching the RA to an Object, it should be rotated (heading) 90*. This will align x axis with lateral (wingtip to wingtip) and z axis with longitudinal (tail to nose). This will avoid a lot of confusion when using offsets or SimVar's WPT commands.
Likewise, when fixed to a location by Latitude, Longitude and Altitude (LLA), note that the Altitude of the AreaDef corresponds to the lower plane. Thus if you wish to center the altitude of the AreaDef with the Latitudinal and Longitudinal centers, you must offset its altitude by an amount equal -0.5 times the height of the AreaDef.
e.g. Let's assume you are flying at an altitude of 1000' msl and you wish to detect User entering the AreaDef. Assume you also wish to give him a tolerance of 100' above or below the center of the AreaDef. You would set the AreaDefs height to 200' and the AreaDefs altitude to 1000 - 1/2 times 200 or 900' msl.
- Be observant when placing a RA on unlevel ground...your triggering object may actually travel below the RA when on the ground and NOT fire the trigger In this case, either bank or pitch the RA to coincide with the ground level or increase height and set elevation below ground level. I have also found that simply deleting the RA, then adding back will solve the problem with it's PxT not firing....go figure!
- A Proximity Trigger, set for multi-shot, is actually two independent triggers in one, associated with the same Area. The entry filters and conditions apply ONLY to the entering actions. The exit filters and conditions apply ONLY to the exiting actions. Thus one trigger can fire WITHOUT the other! If deactivated upon entry, exit actions will NOT fire, and vice versa.
e.g. Trigger conditions are set at <80 knots (entering) and at <100 knots (exiting). Flying through the area at 90 knots, will trigger ONLY the exiting actions, since entry condition was NOT satisfied.
- If you wish to trigger an action based on both entry and exit parameters, then you must set up 3 separate (1 shot) triggers associated with the same area. PxT1 = 1st parameter met. PxT2 = 2nd parameter met. and PxT2a=2nd parameter NOT met. Only PxT1 is active. If PxT1 is satisfied, then PxT2 & PxT2a are activated. If PxT2 is satisfied, then positive actions are executed and PxT2a is deactivated. If PxT2a is satisfied, then negative actions are executed, PxT2 is deactivated, and PxT1 is reactivated.
