Howto:Disable Nasal entirely: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 68: Line 68:
   }}
   }}
}}
}}
|status-body=updated/rebased patch
|status-body=
{{FGCquote
|1= in its current form it cannot be committed "as is", because it does not deal with scenery/tile related Nasal hooks, i.e. those using NasalModelData* - which is primarily the scenery/tile manager code, AIBase and the CanvasMgr stuff.
Those are the locations that would need to also use a FGNasalSys NULL pointer check and skip the execution of the corresponding portions of the code.
I never ran into this because I used the minimal startup profile (as per the wiki) to do the corresponding troubleshooting, with AI and scenery/terrain stuff also disabled entirely.
Like I said, it wasn't really intended to be used "as is" - you definitely need to know what you're doing. Apart from that, someone using this "mode" would obviously also understand where a FGNasalSys related segfaults come from with Nasal disabled
|2= {{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=277291#p277291
  | title  = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki>
  | author = <nowiki>Hooray</nowiki>
  | date  = Feb 23rd, 2016
  | added  = Feb 23rd, 2016
  | script_version = 0.25
  }}
}}
 
}}
}}


Navigation menu