On Wednesday 12 March 2008 08:26, Vivian Meazza wrote: > LeeE wrote > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of > > Sent: 11 March 2008 23:19 > > To: FlightGear developers discussions > > Subject: [Flightgear-devel] New problem with submodels > > > > > > Hi, > > > > For a long time now I've been using ballistic submodels for > > trajectory markers. > > > > When using the trajectory markers, a simple inverted 'T' two > > line object is created at the aircraft position once per > > second, aligned with the aircraft roll and pitch axis. The > > submodels have no weight, 0 buoyancy and are unaffected by > > wind, so once created they remain in place and provide a > > representation of the aircraft's flight trajectory. > > > > I just tried using them, having not used them for a while, and > > found that about half of the submodel instances are rolling > > over and spinning around. > > > > The problem seems to be random and about 50-50, with no obvious > > pattern between instances that behave properly and those that > > rotate and spin. > > > > As they're all created from the same config I'm at a bit of a > > loss as to how to fix it. > > > > I noticed that the README.submodels doc doesn't include a > > definition for the <aero-stabilised> tag but it is used in one > > of the examples. I've always used this tag as a bool i.e. > > 'true/false', like the <wind> tag, but in the examples the > > <aero-stablised> value is '0' whereas the <wind> tag values are > > either 'true' or 'false'. Is '0' used in <aero-stabilised> to > > represent a bool or is it now a numeric value? > > In theory nothing has been changed in submodels in a long time, > and <aero-stabilised> remains a bool. However I have been making > changes in AIBallistic, so the problem probably lies there, and > I'm investigating. I can sort of reproduce your bug, but here all > the submodels behave in the same way. If they don't then it is > possible that you haven't enabled AI Models. > > Vivian
Hmm... I have --prop:sim/ai-traffic/enabled=true --prop:sim/ai-traffic/level=3 and --disable-random-objects in my .fgfsrc but they are the only AI related things I specifically set, and disabling the random objects is probably irrelevant here. Actually, I haven't updated from FG cvs since mid February, so this problem dates from before then. I'm also pretty sure the problem wasn't apparent around early/mid December 2008 because I remember using trajectory markers while I was working on the TFA stuff for the BAC-TSR2 and I sent the resulting update to Curt on 2008-12-17. After some more testing last night, I have to revise the ratio of affected instances to ones that show the problem - far more instances _are_ affected than work correctly. I'd now guess that somewhere around nine out of ten instances are showing this strange behaviour, but there still doesn't appear to be a discernible pattern. LeeE ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
