Engine Option Settings

From Planimate Knowledge Base
Jump to navigation Jump to search

Settings - Engine

Animate Messages/BCasts
If selected, the objects which send and receive messages and broadcasts will get an animation effect shown if they are visible when the receive or send a message or broadcast.


Check For Pauses During BCasts
This option determines if the modeller is able to pause the model while it is processing a broadcast and the immediate events it triggers. It should normally be off so the broadcasts are processed completely before the user gets a chance to interact with the model.


Do Not Defer Stat Updates.
Normally Planimate avoids updating attribute views too frequently by only updating them as simulation time passes. Turning this option on prevents the updates being deferred. It may slow down the model's display if an attribute the model is updating heavily in a routine has a visible view. Turning this option on is useful for models that run everything in "zero time" or for debugging.


Enable Fine TImer Tick BCasts
Turning this option on enables a separate timing mechanism which generates a timing broadcast at a fixed real time interval. The model can set the timing interval. This is useful for performing animations and effects even while the model is otherwise "paused" from the user's point of view. The modeller must take extreme care in the use of this feature as it creates concurrency issues.


Fastforward When No Animation
If this option is selected, Planimate will rapidly advance time during periods where no items are moving on the current panel being displayed. With this option off, update interval events will all take the same (real) time whether an item is animating or not. This gives a smooth effect to the flow of some models but may introduce long waits in other models (eg: while a train is waiting at a mine). This option affects models which have spatial link/track networks and an Update Interval set.


Mouse Clicks While Running
With this option selected, the user can click on buttons while the model is in run/simulate mode. Normally clicks in this mode do not get processed but rather cause the model to pause.




idkbase note 10080