Howto:Disable Nasal entirely: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 8: Line 8:
| developers=Hooray
| developers=Hooray


|motivation-body=Nasal, and particularly its garbage collector (GC), is known for having a certain impact on the frame rate, and frame spacing - however, there are performance issues other than [[Nasal]] code, and some Nasal related issues (e.g. poorly-written code) may contribute to masking such issues - so far, it's been impossible to easily disable Nasal (the subsystem) entirely - the following patch makes it possible to disable Nasal completely, so that it can be eliminated from the equation altogether. This startup mode will obviously only be of interest to developers and power-users, i.e. those interested in doing regression testing (imagine running fgfs in a gdb/valgrind or [[Built-in Profiler]] session or even just viewing the [[OSG on screen stats]] without any scripting overhead), and understanding FlightGear issues (resource leaks, performance issues etc).
|motivation-body=Nasal, and particularly its garbage collector ([[How the Nasal GC works|GC]]), is known for having a certain impact on the frame rate, and frame spacing - however, there are performance issues other than [[Nasal]] code, and some Nasal related issues (e.g. poorly-written code) may contribute to masking such issues - so far, it's been impossible to easily disable Nasal (the subsystem) entirely - the following patch makes it possible to disable Nasal completely, so that it can be eliminated from the equation altogether. This startup mode will obviously only be of interest to developers and power-users, i.e. those interested in doing regression testing (imagine running fgfs in a gdb/valgrind or [[Built-in Profiler]] session or even just viewing the [[OSG on screen stats]] without any scripting overhead), and understanding FlightGear issues (resource leaks, performance issues etc).


{{FGCquote
{{FGCquote

Navigation menu