> >
> >Detlef Faber wrote:
> >
> > >> when using aircraft models in AI scenarios...what is the best file to
> >use (
> > >> some like Aircraft/Spitfire/spitfireIIa.xml actually stop FG from
> >loading
> > >> (098a/win Me)
> >
> >Not necessarily, if the animations are properly references this
> >shouldn't happen. The main reason for this behavior is that all
> >properties are perpended with a slash '/', after removing the first
> >slash (making the properties relative) this behavior should go away.
> >
> >Erik
> >
>
>Just glancing through the files, the pattern seems to be that if the .ac
>file reference is not in the xml file pointed at for the AI-Model then
>there
>will be problems. ie if the xml files are nested (as most are) and the .ac
>file is not in the root file but in a branch file.
>
>I will certainly check out the leading slashes though.. thanks for the
>suggestion.. will report back any further observations. It would be handy
>to
>get this checked out in 09.10/cvs as if it is specific to 098a and doesn't
>occur in 09.10/cvs then its not strictly a "devel" topic and I'll implement
>a work-a-round for my own 098a.
>
I checked the Aircraft/Spitfire/spitfireIIa-set.xml and there were no
leading "/" on any of the other file references I could find.
I did find that by deleting the sections in the
Aircraft/Spitfire/Models/spitfire_model.xml that relate to making certain
parts of the invisible when the view is "0"
<!-- hide all of the model not visible from the cockpit -->
<animation>
<type>select</type>
<object-name>Hull</object-name>
<object-name>Hull-Aft</object-name>
<object-name>Stub-Wing-R</object-name>
<object-name>Stub-Wing-L</object-name>
<object-name>Flap-Inner-R</object-name>
<object-name>Flap-Inner-L</object-name>
<object-name>Flap-Outer-R</object-name>
<object-name>Flap-Outer-L</object-name>
<object-name>Cover-Lower-M</object-name>
<object-name>Cover-Lower-F</object-name>
<object-name>Cover-Lower-A</object-name>
<object-name>Cover-Engine-Side-L</object-name>
<object-name>Cover-Engine-Side-R</object-name>
<object-name>UC-Main-L</object-name>
<object-name>UC-Main-R</object-name>
<condition>
<not>
<equals>
<property>/sim/current-view/view-number</property>
<value>0</value>
</equals>
</not>
</condition>
</animation>
that the "missing" parts of the aircraft re-appeared.... I suspect that
(atleast under 098a) a separate [aircraft]-model-AI.xml is needed for some
of the aircraft that have these sort of conditional entries.
ie something that caters for;
gear-up/gear-down
flaps-up/flaps-down
tail-up/tail-down (for tail-draggers)
engine-running/engine-stopped
possibily;
canopy-open/canopy-shut
etc....
I hope this helps people that might want to be populating their fav airfield
with static models. Thanks for the replies Detlef & Eric
Cheers
:-D ene
_________________________________________________________________
Need more speed? Get Xtra Broadband @
http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
