20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
No edit summary |
mNo edit summary |
||
| Line 24: | Line 24: | ||
|author=<nowiki>zakalawe</nowiki> | |author=<nowiki>zakalawe</nowiki> | ||
|date=<nowiki>Sun Oct 27</nowiki> | |date=<nowiki>Sun Oct 27</nowiki> | ||
}} | |||
}} | |||
{{FGCquote | |||
|The old ‘reset’, which does *not* restart Nasal, is now stripped down to the bare minimum of systems needed for repositioning (tele-porting). Since many aircraft Nasal scripts rely on /sim/signals/reinit to do work on being teleported, that behaviour was also retained. | |||
In an ideal world, there would be a better API to inform aircraft and Nasal modules about a teleport, but for the meantime, the property you mentioned is the one. Eg, really we should have an API to distinguish on-ground vs in-air starts, and adjust the initial state of properties accordingly. | |||
BTW, for the new reset process, the subsystem, including Nasal, is actually destroyed and re-created. This is intentionally to make it almost certain the behaviour after a reset is the same as after the first launch of the sim. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33135215/ | |||
|title=<nowiki>Re: [Flightgear-devel] Expected behavior on "reinit"</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2014-12-10</nowiki> | |||
}} | }} | ||
}} | }} | ||