737 MAX8 Transponder still cannot be set

ISSUE DESCRIPTION

Description of the issue:
The transponder buttons now have animations however, transponder code still cannot be set manually. numbers on digital display do not change
Did you experience this issue before you joined the Beta?
Yes

If applicable, which aircraft is experiencing this issue:
737 MAX8

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time I spawn in it

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1.Spawn in 737 MAX8
2.Connect power
3.attempt to change Transponder code

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
N/A

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC Only] What GPU (Graphics Card) do you use?
RTX 4080

[PC Only] What other relevant PC specs can you share?
N/A

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

Apologies for the mistake with closing this topic! I have re-opened it to allow others the opportunity to test and confirm whether this is a regression within the SU2 Beta and hasn’t been fixed as per the patch notes:

1 Like

Thanks boss :+1:

Weird, I switched to SU2 beta yesterday only because of changes in 737 Max and the transponder was working fine. I mean, I was able to change the code.

Transponder was working fine for me. I can set it via the number pad no problem.

Could this be due to differences in addons / WASM? Someone who had it bugged before and didn’t clear 737 max 8 WASM might still have issues, whereas someone who either reinstalled or cleared WASM might have a working XPDR?
Something is deffo messing it up though

I cleared my rolling cache before using SU2. Not sure it makes a difference, but when using 737 for first time it all got loaded in right in front of me on the first flight, so something was cleared.

The 737 MAX 8 is a Javascript aircraft, and not a WASM/C++ aircraft, so this would not apply here.

Ah, fair enough.
Either way, something’s definitely impacting whether or not it’s broken for people, it’s still broken for me, but for others it works

That is very strange. I cleared all my cache folders including the rolling cache, deleted streamedpackages folder, cleared my WASMs (ik 737 isnt wasm but did it anyway) and still having issues with it. really strange

I’ve since reverted back to SU1. Ill wait for an update or two to SU2 beta then hop back on it

Are you seeing the all new numeric display for squawk code or is it still the original one?

Uhh im not sure. I havent seen what the new one is supposed to look like so I have nothing to compare it to

yes transponder working correctly now

So I reinstalled 2024 from a clean install, brought it up to SU2 beta and transponder is good now

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.