I made my own 3D EFB model and it is not clickable

[MSFS 2024] Questions & Community Discussions HTML/JS
1

Hi fellow chaps,
Instead of attaching the stock EFB Tablet model, I create my own 3D model and I display the stock EFB (with my additional app) on its screen. The problem is the screen is not clickable, no hand icon which I get when / if I attach the stock EFB model. If I pop up the EFB with the TAB key everything is fine - clickable that is.
If I use the same 3D polygon to display my app as a html/js instrument it is clickable.
In the panel.cfg I tried to use the texture entry with and without $ sign, with no luck. What else should I do / add? Any behaviours or so?

regards
ROB

2

Is it set up as a collision material?

3

Do you mean the $ sign as a prefix of the material name and then in the “texture” entry in [EFB] section of the panel.cfg file? Yes, it is.

4

In the material.

image
image500Ă—745 90.9 KB

5

Yes, I set this as well

6

The $ in the material name is legacy and not needed anymore if you set the collision flag on your material.

7

I did try all the combinations with - without.

8

Yeah, sorry, that was a side-point, and either way works. I think the EFB may only work in it’s specific view but the SDK team can confirm.

9

When I look into the stock EFB 3D model “package” (in VFSProjection/…/ simattachments/) and compare, it seems the only thing that I miss is the behaviour. I mean I use my own behaviour to add the emissive material but maybe I need something more for example to get the hand cursor which is surprisigly present on stock EFB. It is present only in the 3D, not in the pop up window so it comes from 3D.

10

for clues, perhaps to confirm “EFB issue” vs “model issue” you could map a different html/js gauge to that surface and check that. E.g. panel.cfg:

htmlgauge00 = NavSystems/Aera/Aera.html, 0,0,1280,800

The PC I’m sending this from is just 2020 so not sure about that example in 2024…

11

I have a version of my app as a htmlgauge and if I use it on this polygon it is clickable.

How about this: I displayed the stock EFB on every clickable tablet / gps / mfd I could find in the sim and it’s not clickable.

12

EFB in 2024 is not a regular html gauge. It is added to the cockpit through a new [EFB] section in panel.cfg.

It is possible to display EFB on any existing gauge surface in the cockpit by modifying panel.cfg, and it’s pretty straightforward. But the EFB never becomes clickable, even if the surface was clickable with another gauge placed there. It would be great if somebody from Asobo chimed in here, as it seems we are missing something important to make it work.

The documentation clearly states that EFB can use a custom model, but it does not give instructions how to set it up, only how to attach the existing tablet model: Adding An EFB

13

To summarize: I follow the SDK, these words to be more specific:

In Microsoft Flight Simulator 2024, aircraft are now all equipped with an Electronic Flight Pad (EFB). This device can either be a custom model or one of the default devices, and it can run “default” apps that are available to all EFB’s in the simulation, or it can run custom apps that have been created for use in an EFB device.

I create a custom model and I want to run “default” apps and custom apps as well.

I add the “default” EFB via panel.cfg:

[DynamicParameters]
param.0 = "EFB_orientation,vertical"

[EFB]
size_mm			= 558,831
pixel_size		= 558,831	
orientation		= [EFB_orientation]
texture			= Screen

It displays and works correctly as the 2D pop up but in the 3D it’s not clickable. The 3D polygon I use is proven to be clickable if I use classic html/js instrument.

Can someone from Asobo take a look at this?

regards
ROB

14

Hello @UniformCarp3294

Check this bug report: 2024 EFB not clickable in the cockpit - [MSFS 2024] Bug Reports / Aircraft - MSFS DevSupport

EFB needs to be a dedicated SimAttachment at the moment for it to be clickable.
(That’s a bug we plan to address in a future update.)
Is this your case?

Regards,
Sylvain

15

Yes, this is my case.
I made it as the SimAttachment - which is a logical solution as I can reuse it later - and it is clickable now.
Thx Sylvian.

regards
ROB

1 Like