Multiple Event
For more details and practical examples, you can load the hangar30 and hangar31 macro files examples.
This is a new powerful tool in version 1.4. The main purpose of this tool is to allow you to make dynamic transitions and moves of objects or parts of them in a smooth movement. For example, you can program a hangar door to open or close in a period of 20 seconds and make the door move a meter every second, producing an smooth move effect.
In order to give you still much more flexibility, the moving or dynamic parts are made of structures previously made and integrated in the macro using this tool. The structures may have from a single sign object to a much more complicated structure, ie, a dynamic finger gate section.
Event types:
The event type or activation method can be triggered using:
- The Distance: You will indicate here the distance from the object to the aircraft. In the example, the dynamic section of the object will be activated when the aircraft remains at a distance of 150 meters.
- By Frequency: The dynamic section of the object will be activated at the selected frequency by the NAV1 or NAV2 option. In the example, the object will be activated when the NAV1 frequency 108.00 is selected.
Movement types
Constant move: You can make move or displace an structure in any direction a given number of meters and for a given period of seconds or times.
In the example, the structure file hang30m1 will be moved 1 meter along the X axis and for a period of 20 seconds, or if you want, you will make move that structure 20 meters to the right in 20 seconds, 1 meter every second.
This example can applied for example, to a hangar with the door closed, this is the initial position, that will open to the right when the aircraft is close to it.
Mirror structure:
In the case where you have a hangar with 2 doors for example, you will maybe also need to do the same type of move, but with the left door, so you will use another structure that will move 1 meter to the left and for 20 seconds as well.
The graphic explains this type of dynamic move, and following this example, the blue right hangar door will be save as the hang30m1, while the red left hangar door will be save in the hang30m2 structure.
You can see in this graphic the initial and final position of the doors.The program will generate the code, not only to perform the activation steps, in our case example, to open the hangar doors, but also it will produce the reverse code, that is when the aircraft is out of the active distance or another frequency is tuned.
In other words, when active, the hangar will open the doors, once is deactivated, the hangar will automatically close the doors again.
Controlled by structures
This option will show:
- All available file structures in your system, and
- The structures making part of the event, and its order.
To add an structure to the event list, click on the left list over the desired structure name.
To remove an structure from the event list, click over the right file list name.The even will be processed in the order shown in the active file list. From the list, the first structure will also indicates the inactive structure to be used, that is, this is the file that will tell show when the event is inactive, as on the example, it will be hang30m1.
On the other hand, the last structure will remain active until the event is deactivated, in the example, the file hang30m8 will remain active and visible all the time, until the event is deactivated.An structure will be displayed every second, so from our example, the event will take 8 seconds to perform the entire event, as much as structures on the list.
Variables used
This is a very important data in the event tool. This list of 5 variables are used to control the status of an event. For this reason, you should not use the same variable from the list for 2 or more different events, or the event dynamics will become out of control and uncoordinated. These variables list are defined in the Microsoft SDK as 'user variables" , and I have not tested them all. I have observed that variable 314 doesn't works always at 100%, I don't have any clues why this happens.