On 07/20/2011 11:45 AM, Hal V. Engel wrote: > These appear to be in the scenery: > > # grep "terminal_2" */*/*/*/*.xml > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_D.xml: > <object-name>terminal_2</object-name> > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_D.xml: > <object-name>terminal_2</object-name> > > # grep "terminal_2" Scenery/Objects/w130n30/w123n37/*.ac > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_D.ac:name "terminal_2.001" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_D.ac:terminal_2.001 > > grep "Mesh61" */*/*/*/*.xml > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.xml:<object-name>Mesh61 > Model_2</object-name> > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.xml:Mesh61 Model_4 > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.xml:<object-name>Mesh61 > Model_2</object-name> > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.xml:<object-name>Mesh61 > Model_4</object-name> > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.xml:<object-name>Mesh61 > Model_4</object-name> > > # grep "Mesh61" Scenery/Objects/w130n30/w123n37/*.ac > > Scenery/Objects/w130n30/w123n37/KSFO_AirTrain_track.ac:name "Mesh61 > Component_1_46" > > Scenery/Objects/w130n30/w123n37/KSFO_AirTrain_track.ac:name "Mesh61 > Component_1_46_0" > > Scenery/Objects/w130n30/w123n37/KSFO_AirTrain_track.ac:Mesh61 Component_1_46 > > Scenery/Objects/w130n30/w123n37/KSFO_AirTrain_track.ac:name "Mesh61 > Component_1_46_1" > > Scenery/Objects/w130n30/w123n37/KSFO_AirTrain_track.ac:Mesh61 Component_1_46 > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61.005" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61.005" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:Mesh61 Model.005 > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:Mesh61 Model > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61.001" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:Mesh61 Model.001 > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61.002" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:Mesh61 Model.002 > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61.003" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:Mesh61 Model.003 > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:name "Mesh61.004" > > Scenery/Objects/w130n30/w123n37/KSFO_terminal_F.ac:Mesh61 Model.004 > > So it appears that the object names in the KSFO_terminal_F.ac somehow > changed and are out of sync with the xml code. Should not be hard to fix. > > Don perhaps you could open a bug report on this in the bug tracker so > that this can get fixed before the release. > > http://code.google.com/p/flightgear-bugs > > Hal > > > On Wednesday, July 20, 2011 07:26:54 AM Donn Washburn wrote: > > > Could not find at least one of the following objects for animation: > > > terminal_2 > > > Could not find at least one of the following objects for animation: > > > terminal_2 > > > Could not find at least one of the following objects for animation: > > > Mesh66 Model_1 > > > Could not find at least one of the following objects for animation: > > To let you folks know fgdata 2.5.0 (last night download) is missing these > > OpenSuSE 12.1 M2 fgfs of yesterday. What might cause this? {seen in a > > > konsole on a C172P} > > > Mesh66 Model_1 > > > Could not find at least one of the following objects for animation: > > > Mesh67 Model_ > > > Mesh68 Model_1 > > > Could not find at least one of the following objects for animation: > > > Mesh67 Model_ > > > Mesh68 Model_1 > > > Could not find at least one of the following objects for animation: > > > Mesh61 Model_2 > > > Could not find at least one of the following objects for animation: > > > Mesh61 Model_2 > > > Could not find at least one of the following objects for animation: > > > Mesh61 Model_4 > > > Could not find at least one of the following objects for animation: > > > Mesh61 Model_4 > > > Initializing Nasal Electrical System power up > > A fresh download of fgdata works but seems to still do the same thing. I also looked in "terminal_2" in Scenery/Objects/w130n30/" for the files mentioned and they are there. It seem like the problem is in Aircraft/C172P. Because I also fly others that seem not have this problem>
-- 73 de Donn Washburn 307 Savoy Street Email:" n5...@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5...@arrl.net " VoIP via Skype:n5xwbg BMWMOA #:4146 Ambassador " http://counter.li.org " #279316 ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Flightgear-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users