Would anyone object if I tied nasal code specific to scenarios into FG aircraft?
Currently there isn't a way to load nasal code when a scenario is loaded and the only feasible way seems to be to add a check in the aircraft config files and then load a specific nasal script if a scenario is running. In my opinion it's an architectural no-no but at the moment it's the path of least resistance. Reason : I was considering adding training scenarios to FG similar to what can be found in MSFS2004. I either need to lock the scenarios to a specific aircraft like the 172 and dissallow the user from selecting other suitable aircraft like the J3Cub, 182, Cirrus SR20, etc. or I need to modify a whole stack of aircraft and give the user to option of learning in their favourite aircraft. Yay or nay? Paul ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
