After last night's SU3 Beta update, many systems on my new release are broken

[MSFS 2024] Bug Reports Aircraft
1

Hello,

We are just releasing a product today (MH60 Helicopter, native FS24), and following last night’s SU3 Update (1.5.21.0), we have noticed a number of issues:

  • Many of our switches no longer work correctly. Their interactions work fine, and animation plays out, but they do not conserve emmissive or position correctly.
    For example, we have a number of pushbuttons for autopilot functions. Pressing the button once will correctly illuminate and enable the function. However, further button presses will not change the state of the emmissive (driven by LVAR), though lvar is changing.
    It also seems that once you “lock” the emmissive on one, many switches of the same type will stop functioning correctly with it.

  • Map gauge crashes at random. Sometimes it renders fine, sometimes renders only one MFD map, sometimes none. A reload of the flight is generally enough to get things up and running again.

Neither of this issues exist on Stable SU2, nor we recall seeing them on previous Betas of SU3.
@FlyingRaccoon @EPellissier

1 Like
2

Update - potentially related to this?

  1. Fixed some emissive flashing issues when disabling an interaction highlight

It is possible that the highlight is freezing the state of the emmissive

3

Hello @vantech

We are tracking an emissive issue on other aircraft that looks like what you describe.
The blue emissive when hovering a knob conflicts with the actual knob emissive and it no longer reflects the actual state of the button.
However, this should just be an emissive issue and should not have impact on the knob’s “position”.
Can you show a video demonstrating the position problem?

Regarding the MFDs, the WASM gauge are dirty with an “illegal instruction”.
We are trying to track what causes this, but it would help us if you could replicate this with a debugger attached and track down which call triggers this exception. (or let us know if this does not happen in the dev environment maybe)

Regards,
Sylvain

4

hello @FlyingRaccoon

Upon further investigation, you are right - only the emissive is affected. Underlying function remains to work correctly. However, it is not only knobs that are affected. pushbuttons with emmisisves are also affected. Seems that any template with an emissive setup.

as for the map, our map isn’t directly being rendered by WASM, but we have a WASM module on the aircraft. It seems as if the loading of the map gauge in particular was interrupted in the process. Ill continue investigating with the debuggers.

1 Like
5

Hi @FlyingRaccoon

Here is a video showing the issue. I found that the emissive turns on after you click it and stays on as long as you remain hovering (holding the click is not required) and the blue highlight flashes. Once you leave it’s gone.

You guys fixed the blue highlight issue a while back that i reported and maybe that is now having some new type of conflict. The issue was that the highlight would not show the emissive when you were hovering. So it seems that its backwards where it now shows when hovering and fails when no hovering.

6

Hi @Flysimware

If this is just an issue with the emissive, a fix is already on the way.

Regards,
Sylvain

2 Likes
7

Yes it’s only an emissive issue as there is no function issues with our autopilot. Thanks for getting back to this. This needs to be fixed before SU3 comes out.

8

Hello @vantech @Flysimware

Can you confirm this is resolved for you in the latest SU3 version?

Regards,
Sylvain

9

Yes the buttons with the emissive issue are fixed in the official SU3. Thanks.

1 Like
10

All resolved, can confirm.

1 Like