Getting Gigged on Transition Level/Altitude

[sandman72nd]

Aircraft FSL-A321
Active Sky P3D

Getting gigged on setting the transition level.
Typical Procedure is when reaching Transition Altitude in the USA 18,000 the call is transition and then you set standards and same going down with the BAR/ALT.
By the time you make the call and set the alt to 29.92/1013 or the current Baro you have gone a hundred or so feet past.

I set STD at 18,100 and it still gigged me red.

Outside of the USA as you know they will have a Transition Alt say 13,000 and a Transition Level of maybe 15,000.  This gives you a zone to set the altimeter.  This would require a Database of this information which i'm not sure if your program has it or not.

Either way when the system finally went red was at your upper buffer and it remained red.

In the FSL A321 you pull to set STD and push to get the QNH/ALT setting.

I have the CA/FO synced so setting one sets both and then there is the ISIS (standby instrument).

All 3 were set before 18,300 and 18,000 was yellow.

Something not syncing or being recognized here.

FYI

[Travis]

Hi Sandman!

For several years, FSCaptain has used a (semi-accurate for most large FlightSim airports) Transition Altitude database - which for the past few years has been up-dateable with a new "NavData" subscription.

So FSCaptain should know each Airbus-flyable airport's TA level.  If not, please send the FCDU and FSCaptain logs for this flight.

I wish my browser had a macro for that last clause....

It sounds as if we are not getting the correct signal to indicate what your aircraft's correct system of setting all altimeters is.

So the first thing you should do in all of your Override Configuration files, is to check the Altimeter INOP checkbox and save that change.

Again, since it seems our interface with this FSL does not have a path to indicate the aircraft's altimeter, so we default to the FS9/FSX/P3D Aircraft value for the altimeter.  And since we're apparently not seeing what you're doing, let's have your system ignore that for now.  (There are no benefits from hitting your targets on the TA setting - only a demerit if you don't let us know you've made the correct attempt to go STD.)

Now I don't have the FSL aircraft, so I need to put some feelers out to look for any other way for us to know what's occurring here.

There are plans to have an FSCaptain Service Pack within a week or so.  It's just a series of odds and ends of fixes and changes to existing things.  I could certainly add a interface for this system if I find any LVARs and values....

Best,

[Travis]

Sandman,

I've asked an FSL owner to check if he can find an LVAR being used to indicate the altimeter setting or if it's simply STD or not.

Give him a few days to check.

Best,

[peter]

Hello Sandman,

I don't have the A321, but I analyzed the FSL A320 altimeter functions, which should be fairly similar. Unfortunately, FSL has implemented the altimeters in such a way that FSCaptain cannot access the settings. In technical terms, there are Lvars (variables that FSCaptain can read) for the rotational state of the altimeter knob, but not for the actual pressure value. The rotational state is not of much use if you don't know where the pressure is initially.

The bottom line is: FSCaptain is not able to monitor FSL altimeter settings. You should set Baro Altimeter to INOP for the A321 in the Administrator under "Aircraft Characteristics".

Best regards,
Peter