MSFS 2020 airplanes - Custom EFBs objects clickable from behind problems

[SimbolFSReborn]

Version: 1.0.72.0

Frequency: Consistently

Severity: Blocker

Context: TL3000 and FSR500? mounted from Community? in flight?

Bug description:
in MSFS 2020 In order to prevent objects behind a screen being clickable, in this case our EFBs, we use the template ASOBO_GT_Interaction_NoInteraction on the EFB screen. This is to prevent users clicking unintentionally circuit breakers and other objects behind the tablets

Unfortunately in MSFS 2024 this results in the screen becoming non touchable or losing the hand cursor (which concerns mean as this could me it would not work with XBOX Consoles clicks, etc.).

Repro steps:

Load TL3000 or FSR500 in community folder and see how the EFBs are non operational.

[erasam]

Same here for my EFB (using the same template) no hand cursor is shown

[FlyingRaccoon]

Hello @SimbolFSReborn @erasam

Do you still have the issue with version 1.0.77.0?
I checked on the FSR500 and I cannot click the breakers through the EFB.

Regards,
Sylvain

[SimbolFSReborn]

Hi Sylvain,

I put the ASOBO_GT_Interaction_NoInteraction on the EFB screen directly now and things works preventing things going behind, however the EFB is missing the “hand icon” for touch screen handling. Making it a bit difficult to click certain things sometimes.

This is the bug remaining, the lack of the “hand icon” when we use this template in order to avoid things clickable from behind.

The version you have of FSR500 now has a custom template for this (similar to the NoInteraction) and the behaviour is the same… no hand icon despite the EFB screen is set as a colision and touchable. Removing the NonInteraction or the custom template brings back the hands icon and great click capability, but then the CBs are clickable from behind.

The custom template has this:

<Template Name = "FSReborn_GT_Interaction_NoInteraction">
        <DefaultTemplateParameters>
            <MOUSEFLAGS/>
            <DISABLE_INTERACTION_LOCK>True</DISABLE_INTERACTION_LOCK>
            <DISABLE_MOUSERECT>True</DISABLE_MOUSERECT>
        </DefaultTemplateParameters>
        <UseTemplate Name="ASOBO_GT_MouseRect">
            <CALLBACKCODE>0</CALLBACKCODE>
        </UseTemplate>
    </Template>

For the record in MSFS 2020 the same template and aircraft package is working fine and we have the hand icon interaction.

Best,
Raul

[erasam]

I confirm the same result as reported by @SimbolFSReborn

Now you cannot interact with things behind but no hand cursor is shown

[some1]

We’re still observing similar issue in our aircraft in the 1.0.84 version.

Apart from the cursor appearing as a regular arrow and not a hand icon like it used to in FS2020, there’s also an intermittent problem with mouse clicks not being registered by the gauge screen.

I’ve replaced our tablet gauge with “MouseWasmModule” sample from the SDK. Most of the time it looks like this, which is a correct working state (except for lack of hand icon), and the mouse clicks are registered:

But sometimes the red circle under the cursor starts flickering several times a second or disappears completely, the reported “position cursor” becomes (-1,-1) and the gauge does not register new mouse click events in this state.

I suspect it’s related to animated tablet shakes and vibrations. It seems that if the gauge object is moving, the gauge is loosing cursor.

[some1]

Turns out our issue is caused by the camera movement, and not object movement. I’ve created a separate bug report as I’m not sure if it is related to problems discussed in the first post or not. 2020 plane - gauge is loosing cursor when camera moves away from it

[SimbolFSReborn]

for what is worth, when I remove the template usage ASOBO_GT_Interaction_NoInteraction and the hand icon comes back, the clicks work fine… however you can click behind the gauges / html controls, in this case my EFB.

So the it seems the click behaviour is more related to the hand icon integrations.

Best,
Raul