Howto:Disable Nasal entirely: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 9: Line 9:


|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 Nasal related issues may contribute to masking such issues - so far, it's been impossible to easily disable Nasal 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, and understanding FlightGear issues (resource leaks, performance issues etc).
|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 Nasal related issues may contribute to masking such issues - so far, it's been impossible to easily disable Nasal 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, and understanding FlightGear issues (resource leaks, performance issues etc).
{{FGCquote
|1= Instead of adding just-another-feature we need to strip it down to getting a fast and constand fps rendering engine. Everything else needs to run outside the main loop and has to interact with the core by, say HLA/RTI or whatever IPC we have.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34793778/
  | title  = <nowiki>Re: [Flightgear-devel] A FGPythonSys implementation: The embedded
Python interpreter as a FlightGear subsystem.</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Jan 25th, 2016
  | added  = Jan 25th, 2016
  | script_version = 0.25
  }}
}}
{{FGCquote
|1= I'd just recommend to not do it but to focus on detangling the subsystems and creating a distributes simulation instead. That's my vision.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34793948/
  | title  = <nowiki>Re: [Flightgear-devel] A FGPythonSys implementation: The embedded
Python interpreter as a FlightGear subsystem.</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Jan 25th, 2016
  | added  = Jan 25th, 2016
  | script_version = 0.25
  }}
}}
|objective-body=disable Nasal scripting
|objective-body=disable Nasal scripting
|background-body=
|background-body=

Navigation menu