Penalties on some aircraft

Greetings friends:
Some aircraft have issues with the lights:
For example, the A35K displays this error “Taxi Light Off” before initiating pushback, this is in MSFS2020. In Xplane, pushback doesn’t start if you turn on the taxi lights; the pushback operator asks you to turn them off. It used to work fine, but now it displays this error. Taxis should not be turned on in any aircraft until the pushback is complete, but they should be turned on before taxiing.

On the other hand, there is also a TCAS light that I’ve never figured out how to fix. It displays another penalty of “Transponder Off,” when in reality it is operating correctly.

These are the reasons for the penalties that never allow a 100/100 on these aircraft.

If I’m the one making a mistake, please share your recommendation here so we can all fix it.

This thread could be used to report these types of errors, whether with lights or any other aircraft operation.

Thank you very much!

The maximum I can get for 359, 35K is 98, not beyond this. I couldn’t figure out how to correct the TCAS & Transponder too, though.

the “fault” is the need of MODE C (ALT ON) since the parking area before living.

try this

https://www.reddit.com/r/VATSIM/comments/1k41oeg/mode_c_on_a350/

or

Steps to Enable Mode C on the A350 Transponder:

  1. Access the SURV MFD Page: Navigate to the Surveillance (SURV) page on one of the MFDs in the cockpit.

  2. Locate the XPDR Section: Find the section dedicated to the transponder (XPDR) settings.

  3. Set XPDR Mode: Turn the XPDR Mode switch to AUTO.

  4. Enable Altitude Reporting: Set the ALT RPTG knob to the ON position.

  5. Confirm Settings: A confirmation dialog may appear; confirm the selection to apply the settings.

or also enable MODE S, should have ALT included

I have this tool with MSFS2020 , Simwars.exe

C:\MSFS SDK\Samples\VisualStudio\SimvarWatcher\bin\x64\Release\Simvars.exe

it displays many things. you can monitor what you prefer, in this case Transponder State

you need to set it up this way:

When on Ground it will show Value 5, when in Standby Value 1.

I have the A350 set as this way, I suppose you too,

now perhaps what we need to know is that, the liners activate the ALT mode when on take off at least, and this may cause the penalty. I couldn’t confirm a simfly flight because I never used a liner like this one, from cold and dark in order to start a simfly mission, I started a flight on runway so it was already ON. and did the take off. while on runway in fact it gave me Value 5, on Ground , don’t know if this means it gives out info about Altitude while on ground (taxing, etc). So, if you have set it up as I have here from parking, and still gives out penalty, while simvar watcher says first value 5 than after take off (don’t know what altitude turn to value 4), then Simfly needs to do some changing on the penalties. they need to be activated after take off.

1 Like

Thank you very much for this information sharing. :folded_hands:

Wow! This is a bit complex for me, but I’ll still try. Thanks for the info, Antonio!

If you don’t want ti use the software, just tell me if your transponder settings are like in the picture from the parking area. If so, perhaps simfly needs to review the transponder rule penalty.

It’s exactly the same. I’ve even changed the code several times for testing, and SimFly recognizes it perfectly. There must be a simple error in the client’s reading.

well if you confirm the same settings I have, it means that on some aircraft, the MODE C, or ALT is turned ON after take off, that’s why there’s a penalty given, because the actual Simfly rule wants it ON from the parking area also while taxing. But in some airplane, the transponder is set automatically on “GROUND”, and after take off switches to “ALT”. So for now, simfly needs to find a new way or a new rule about transponder MODE C setting. Will keep you updated.

1 Like