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?
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.
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:
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
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.
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.
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?