20,741
edits
Howto:Troubleshooting Nasal Callbacks: Difference between revisions
Jump to navigation
Jump to search
Howto:Troubleshooting Nasal Callbacks (view source)
Revision as of 13:41, 1 February 2016
, 1 February 2016→Background
| Line 109: | Line 109: | ||
}} | }} | ||
}} | }} | ||
=== Understanding Callbacks === | |||
{{FGCquote | {{FGCquote | ||
| Line 148: | Line 151: | ||
| added = Jan 31st, 2016 | | added = Jan 31st, 2016 | ||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | |||
}} | |||
{{FGCquote | |||
|1= you can patch the C++ code to maintain a list of callbacks invoked via timers/listeners and log everything to the property tree/console by printing out the file/line number where each callback was registered - I previously posted a patch doing this, so you could run a forum search - it would provide you with a list of file names and line numbers, including SGTimeStamp based timing for each running callback. There's another patch identifying repeatedly registered callbacks, too - by checking the address of each Nasal callback against a vector of already known callbacks. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=232018#p232018 | |||
| title = <nowiki>Re: Sometime, with Yasim... frame-rate is slow</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Feb 13th, 2015 | |||
}} | }} | ||
}} | }} | ||