Page Comparison

Switch Driver Seat: If a vehicle has multiple seats (such as the Mobile Crane), then the user can apply that vehicle to this action, and when triggered, the driver will switch from driver seat to operator seat. This is handy for determining how safe it is to operate a crane by seeing exactly what the operator will see as objects are being lifted/lowered by the crane, as an example.

This is meant to be used hand-in-hand with the Mount Camera to Vehicle trigger which will allow you to get a PoV experience as the operator attempts to lift objects with the crane. Of course, it’s not limited to mobile cranes, and users may find other uses for this feature.

Toggle Object On/Off Path: Once some event has occurred (like the above 2 events) you can perform this action, which either sets, resets, or stops an object from moving on a path.

• Have a pedestrian or vehicle path made

• Place an object in the scene (something you want to add to a path after some event occurs, like a pedestrian after they’ve reached a certain point, or on a certain date)

• Select the path and use the Choose Selected to add the path to the trigger

• Select the object and Add Selected to add it as well

• Set on path - either true, false, or toggle

  • False: If your object is not already on the path, false trigger does nothing because the object is not being influenced by the path yet, otherwise it stops the object on the path

  • True: Will set the vehicle to animate from the beginning of the path

  • Toggle: Will swap between false and true depending on what it was before

This action is designed to work with either of the two new trigger events, Object-Point Proximity and Object Reached End of Path. One example of how these work together would be you have a pedestrian on a path, they reach the end of the path where there’s a dangerous drop in elevation. Fuzor can detect when they reach the end of the path and allow you to trigger another event, such as a Pedestrian Animation to show the pedestrian falling due to unsafe conditions.

Affected Triggers:

• Animation Sequence: Snap to Key Frame.

• Control Animation.

• Flythrough Playback.

• Play Custom Object Animation.

• Set Pedestrian Animation.

• Play Construction Timeline.

• Action Delay.

What does this mean?

If you have more than one action in a trigger, then in the past all of those trigger actions would play at once, not waiting for the previous action to finish. This made triggers harder to use and forced users to create delays in order to simulate sequential trigger actions, where one action waits for the previous one to function.

It affects the actions that happen over time, such as animations or Flythrough playback.

In the example on the right, an event will trigger the driver to swap seats, play an animation, and activate a saved view. In the past, the saved view would activate as soon as the animation started. Now, the saved view will not activate until the animation has finished.

Image Added