Re: [Flightgear-devel] C172p KAP140 textranslate issue

2010-10-09 Thread James Turner
On 6 Oct 2010, at 08:42, Erik Hofman wrote: >> Does anyone have the necessary fu with an XML-grep tool, to find all >> instances of less-than and greater-than in data/Aircraft, where a >> tag is the first child? That should find all the likely problem cases. I just did some testing with an XP

Re: [Flightgear-devel] C172p KAP140 textranslate issue

2010-10-06 Thread Erik Hofman
On Tue, 2010-10-05 at 23:16 +0100, James Turner wrote: > This is my fault, I changed the SGCondition logic to be order dependant, > instead of the previous 'property is always take as the LHS, even if appears > on the RHS' behaviour. At the time I did some greps of data/Aircraft to see > if anyo

Re: [Flightgear-devel] C172p KAP140 textranslate issue

2010-10-05 Thread James Turner
On 5 Oct 2010, at 21:55, Stuart Buchanan wrote: > I've now fixed this. The problem was that > > > >0 >/autopilot/KAP140/settings/target-pressure-rate > > > > is no longer the same as > > > >/autopilot/KAP140/settings/target-pressure-rate >

Re: [Flightgear-devel] C172p KAP140 textranslate issue

2010-10-05 Thread Stuart Buchanan
I wrote: > I've started seeing strange animation behaviour on the C172p KAP140 autopilot. > > Specifically, the values displayed when in VS mode seem to be > incorrect. Going into VS mode an pressing UP gives a VS readout of > -9000 fpm. AFAICT the autopilot behaves correct, setting an > appropriat

Re: [Flightgear-devel] C172p KAP140 textranslate issue

2010-10-03 Thread Victhor
Yes, I've been having that issue for quite a while. > Hi All, > > I've started seeing strange animation behaviour on the C172p KAP140 autopilot. > > Specifically, the values displayed when in VS mode seem to be > incorrect. Going into VS mode an pressing UP gives a VS readout of > -9000 fpm. AFAI

[Flightgear-devel] C172p KAP140 textranslate issue

2010-10-03 Thread Stuart Buchanan
Hi All, I've started seeing strange animation behaviour on the C172p KAP140 autopilot. Specifically, the values displayed when in VS mode seem to be incorrect. Going into VS mode an pressing UP gives a VS readout of -9000 fpm. AFAICT the autopilot behaves correct, setting an appropriate target pr