308
edits
Nasal optimisation: Difference between revisions
Jump to navigation
Jump to search
m
added explanation about using the built in performance monitor
m (Gijs moved page Nasal Optimisation to Nasal optimisation: Per FlightGear_ wiki:Manual of Style#Article titles) |
m (added explanation about using the built in performance monitor) |
||
| Line 24: | Line 24: | ||
Generally using props.UpdateManager (with the FrameNotification hash) can be generally used to perform OnChange processing that is more efficient than the property listeners - however property listeners should still be used to perform occasional actions (rather than per frame actions) | Generally using props.UpdateManager (with the FrameNotification hash) can be generally used to perform OnChange processing that is more efficient than the property listeners - however property listeners should still be used to perform occasional actions (rather than per frame actions) | ||
== Using the built in performance monitor == | |||
You can do this from the debug menu '''Monitor System Performance''' and currently the GUI only shows the top level. | |||
When the performance monitor is active either by having the GUI on display or because <code>/sim/performance-monitor/enabled</code>is true overruns will be logged.at ALRT level. An overrun is defined as exceeding<code>/sim/performance-monitor/max-time-per-frame-ms</code>). | |||
Setting <code>/sim/performance-monitor/dump-stats</code> to non-zero will cause detailed performance info will be output to the log. | |||
== fdm-initialized listener == | == fdm-initialized listener == | ||