Wish I could give a better description but a couple of times recently I've seen something really weird happening while testing the 747 3d model.
With everything synced to the current CVS the YASim fdm fails to start with 747-yasim on my system. It just spews a bunch of "Fail to unbind property" messages and gives up. Flightgear keeps on going however. The scene comes up...everything works, but the fdm is dead. The first time I saw something like this was the other night and it was right after I added some animation stuff to the 747 3D model xml file. There is several lines of "disabled" properties in that file as I borrowed it from the c310 model and have been piece by piece converting the animations to the 747 model. Anyway, I knew for sure that the only thing I had changed was that xml file. It happened right after midnight so I even considered the possibility of a time related bug :-D. So I took out my changes. It worked again. After sputtering a bit and examining the xml until my eyes crossed, I was able to get yasim sucessfully work by putting my stuff back in and deleting a few lines of the disabled xml in that file that I knew I would not be using. Note what I refer to as the "disabled" xml has comments within it...so what I'm actually doing is wrapping the whole of the disabled stuff in a <disabled></disabled> tag. This means they are being loaded but not used. See "Aircraft/747/Models/boeing747-400-jw.xml" to see what I mean. Tonight I was able to get it working by deleting the unused propellor animation definitions. This isn't buggy xml. The problem seems to be quantitative not qualtitative :-). It is very strange though, and indicates a problem maybe in fg_prop.cxx, since there isn't any reason I can think of that the 3d-model code should have an effect on the fdm. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
