I've just upgraded from FlightGear 0.9.4 to 0.9.6. I am using the Windows distibution executable installation, on a system that used to run 0.9.4 just fine, including my new model for the JPATS (The T-6A Texan II). System is Windows XP, 1.5 Ghz, 16 Meg Rage AGI Ultra video card.
Basic aircraft like C-172 work, but the JPATS T-6A model that I as working
under 0.9.4 on fails to start. I can see the messages
NoLoDs=1 NoGT=499 NoLT=146 No0=0
This seems to be a plib MDL loader problem:
grep NoLoDs */*
ssg/ssgLoadMDL.cxx: printf("NoLoDs = %d\n", (int)noLoDs);But it doesn't look like this is the cause of the problem.
David Culp has a T6-Texan II model for FlightGear 0.9.5 in his hangar: http://home.comcast.net/~davidculp2/hangar/hangar.html
Maybe you could test it and check for any differences?
However, the plots thickens. I've been playing around, trying to figure out
what the problem is. I've copied the c172p-set.xml file from the c172p
directory into my JPATS directory, I can make changes to it okay, and it
works just fine (at least for the limited changes I did).
However, if I change the name of the file from some besides c172p-set.xml,
even just to c172y.xml, it fails to start. Changing it to c172x-set.xml or
c172p-set.xml seems to work, as long as it is the name of something that
already existed....
FlightGear only searches for aircraft startup files that end with -set.xml otherwise it's ignored.
Erik
_______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
