On Wednesday, July 20, 2011 03:37:00 PM Donn Washburn wrote:
> 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>
No this shows up on other aircraft as well. It is a scenery problem for sure.
It is not fixed in GIT yet. I opened a bug report and it has been assigned a
very high priority because it is a very noticable error in the console. But
it does not seem to have much impact on the actual sim. In any case it will
likely take a few days to get a fix into GIT when the person responsible for
this gets to it.
The tracker item for this is:
http://code.google.com/p/flightgear-
bugs/issues/detail?id=383&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20Milestone
This will be updated when the issue is fixed. You can also subsribe to this
and get automatic updates.
Hal
------------------------------------------------------------------------------
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC can
improve internal communications as well as offer faster, more efficient ways
to interact with customers and streamline customer service. Learn more!
http://www.accelacomm.com/jaw/sfnl/114/51426253/
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users
