Baron 58P - AP altitude captures pressure alt instead "indicated" one
-
Hi,
currently Baron's AP captures pressure altitude after flight (shown i.e. at Transponder) not altitude from main baro altitude.
Standard flight, at destination I set current QNH (999 hPa), then I set 1013 hPa after TA. AP maintains FL190. At descent I set 3000 ft and destination QNH (1001 hPa).
AP descent to pressure altitude FL030, but it's 2720 ft at 1001 hPa altimeter setting.
AP altitude logic should use "indicated" value (at baro altitude) as input for calculations.
-
Answer from the dev for you...
I've seen more than a few reports of this, but have been unable to reproduce the problem. It may be an issue with only the PMS50 supplied WTT Mode package, if you are using it. Either way, please delete this single line in the two systems.cfg files (one for the normally aspirated, one for the pressurized) aircraft:
altimeter_indicator = 2
Please let us know if that fixed the problem so that it can be included in the next update. If not, we will continue searching for the problem. Thank you!
Please reply here to this one, once tested. Thank you.
-
@voice-of-reason Sorry. What’s the pathway to those files.
-
@voice-of-reason said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:
altimeter_indicator = 2
First try - it works :)
I will try another flight tomorow to proof that solution.@ftrdoc said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:
@voice-of-reason Sorry. What’s the pathway to those files.
..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaron
and
..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaronturbo\ -
@voice-of-reason thanks for the reply. I had the problem with the TDS GTNXi too, but I'll give it a try today.
-
I have the PMS50 installed but am using the TDS GTNXi but I can confirm, after deleting the line the AP now captures the correct height.
-
As a note, I have heard of an issue similar to this. I think it was in the base sim, not sure if it was fixed. Back then the developer also said they couldn't replicate it. Turns out the reason for this was that the developer was pressing B to set the altimeter. This also did other things in the background that fixed the discrepancy. Not sure if this is the same issue here, but if anyone is trying to replicate this, try to do it without hitting B and by setting the altimeter by hand.
