It seems to work fine here without any additional changes , but I only have one aircraft in that folder at the moment
On Wed, Dec 1, 2010 at 2:36 AM, James Turner <zakal...@mac.com> wrote: > > On 1 Dec 2010, at 08:45, James Turner wrote: > >> This is supposed to be automatic - I updated the code in Nasal that sets up >> the IORules, so each additional aircraft directions should be on the >> read-allowed list. Of course, it's entirely possible I didn't get this 100% >> correct - it's awkward logic to test. If you can, please investigate a bit >> further, especially the code that sets up Nasal security (startup.nas?) and >> see if your aircraft dir path is getting processed. > > Apologies, io.nas is the file to look at. Add some print statements to see > what's going on, if you can. > > James > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
