Curtis L. Olson wrote: > Melchior FRANZ writes: > > Curtis L. Olson wrote: > > > YASim has had code changes in the last 2,3,4 days so perhaps > > > something broke? (Hopefully it's not me that's doing something > > > stupid.) :-) > > > > 'Bad' news: Yasim works for me with CVS HEAD from one or two hours > > ago. I just flew the dc3 from LOXL to LOXT (and crashed there > > ;-). I tried the a4 before and it worked, too. > > I wonder if the recent change preferences.xml has broken everything?
Phew. Not my fault this time. :) To address the original subject, those "failed to untie" messages are just benign warnings. What used to happen is that a lot of the FDM output was tied to properties outside the FDM. In particular, the first and second engines would automatically result in property output; but the third and higher ones wouldn't. Rather than write two code paths to deal with the issue, I just threw up my hands, untied the things, and did it all manually. Since then, I believe most of these limitations have gone away, but the fgUntie() calls are still there. When called on untied properties, they generate a warning. I need to take a look and verify that this code can be snipped, and eliminate it. Not a lot of work, just tedious. The relevent unties are in YASim::bind(), if someone wants to, heh, do it for me. :) Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
