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

And then it aborts, sometimes with other mesages. I couldn't find any
information around on how to interprete errors codes, or possible solutions.
I also couldn't find a way to pipe these messages to an output file, so I
had to run it several times to write these down.

I looked at the Change Log, trying to establish what had changed in the last
two revs, and didn't see anything that jumps right out at me.

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....
 
........  Oh, wait. Now c172x-set.xml doesn't work, but c172r-set.xml works.
 
I didn't see anything in the archives, although I only quickly scanned them.

Suggestions?  

Thanks,
Bill




_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to