On Wed, 5 Sep 2012, Alasdair wrote:
> I have narrowed this problem down further.
>
> Comment out:
> <instrumentation n="0">
> <path>Aircraft/c172p/Systems/instrumentation.xml</path>
> </instrumentation>
> in c172p-set.xml
>
> Similarly
> <instrumentation>
> <path>Aircraft/b1900d/Systems/instrumentation.xml</path>
> </instrumentation> -->
> in b1900d-set.xml
>
> and in the case of the SenecaII
> <instrumentation>
> <path>Aircraft/SenecaII/Systems/SenecaII-instruments.xml</path>
> </instrumentation>
> in SenecaII-base.xml
>
> The Calalyst view port problem disappears and the problem planes behave
> beautifully. Can someone with this problem confirm?
That would make the aircraft use the generic instrumentation file that
includes the wxradar instrument (which usually or, maybe, always masks the
problem).
You could also try adding
<radar>
<name>wxradar</name>
<number>0</number>
</radar>
in the aircraft's own instrumentation file.
This, however, is just a work-around, not a solution.
Cheers,
Anders
--
---------------------------------------------------------------------------
Anders Gidenstam
WWW: http://gitorious.org/anders-hangar
http://www.gidenstam.org/FlightGear/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
