Black wasm screen in msfs2024 after updating from msfs2020

[CoffeeCorn12816]

I’ve changed the background color but only the epic display work. my wasm screens are black:

[VCockpit05]
size_mm = 800,600
pixel_size = 800,600
texture = $SCREEN_5
background_color = 42,42,40
htmlgauge00 = NavSystems/Epic2v2/Tsc/Epic2Tsc.html, 0, 0, 800 ,600

[Vcockpit06]
size_mm=1024,768
pixel_size=1024,768
texture=$SCREEN_6
background_color=42,42,40
htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=test.wasm&wasm_gauge=test, 0,0,1024,768

debug screen is fine and recompiled for 2024 sdk. thanks

[EPellissier]

@CoffeeCorn12816,

There’s nothing we can do to help without more information.

• Have you tried the SDK Samples? If they work, then most probably the issue is within your package setup.
• If that’s the case, the easiest way for us to help is to get either the built package or the package sources through the Private Content section.
• Have you checked the sim’s Console for error messages?
• Have you checked the WASM Debug Window for potential information?

Best regards,

Eric / Asobo

[CoffeeCorn12816]

this is a MSFS2020 Gauge is mentioned in the debug window. What do I need to change? Many thanks.

[EPellissier]

I can’t tell you what needs to be changed if I don’t know what’s there in the first place.

• Does the WASM Debug Window tell you that the module is in a Dirty state or not?
• Can you take a screenshot of the window on both versions?

The documentation on how to use this window is available here:

• MSFS 2020: WASM Debug
• MSFS 2024: WASM Debug

Best regards,

Eric / Asobo

[CoffeeCorn12816]

Dirty? Only saw that it’s a msfs2020. Does it need some panel.cfg vodoo? For the Epic screens I only found by coincidence, that it needed a different background color…

[CoffeeCorn12816]

ok must be a panel.cfg problem. If I put it at first:

[VCockpit01]
size_mm = 1024,768
pixel_size = 1024,768
texture = $SCREEN_1
background_color = 42,42,40
htmlgauge00 = WasmInstrument/WasmInstrument.html?wasm_module=test.wasm&wasm_gauge=test, 0,0,1024,768

it works fine. How to setup 5 screens? Many thanks

[Arzop]

Hi,

The order is not important in the panel.cfg file, so I assume you made something wrong in it. Can you share with us the all file so we can try to find the mistake?

If possible, can you send us the all package because it is much more easier to investigate, following this page : How to report a bug or crash.

Best Regards
Maxime / Asobo

[CoffeeCorn12816]

A new 2024 restriction? I can’t get more than 4 screens.

[VCockpit01]
size_mm=1024,768
pixel_size=1024,768
texture=$SCREEN_6
background_color=42,42,40
htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=test.wasm&wasm_gauge=test, 0,0,1024,768

[VCockpit02]
size_mm = 1024,768
pixel_size = 1024,768
texture = $SCREEN_1
background_color = 42,42,40
htmlgauge00 = NavSystems/Epic2v2/PFD/Epic2Pfd.html?Index=1, 0,0,1024,768

[VCockpit03]
size_mm = 1024,768
pixel_size = 1024,768
texture = $SCREEN_2
background_color = 42,42,40
htmlgauge00 = NavSystems/Epic2v2/MFD/UpperMFD/Epic2UpperMfd.html?Index=2, 0,0,1024,768

[VCockpit04]
size_mm = 1024,768
pixel_size = 1024,768
texture = $SCREEN_3
background_color = 42,42,40
htmlgauge00 = NavSystems/Epic2v2/MFD/LowerMFD/Epic2LowerMfd.html?Index=3, 0,0,1024,768

[VCockpit05]
size_mm = 1024,768
pixel_size = 1024,768
texture = $SCREEN_4
background_color = 42,42,40
htmlgauge00 = NavSystems/Epic2v2/PFD/Epic2Pfd.html?Index=4, 0,0,1024,768

[VCockpit06]
size_mm = 800,600
pixel_size = 800,600
texture = $SCREEN_5
background_color = 42,42,40
htmlgauge00 = NavSystems/Epic2v2/Tsc/Epic2Tsc.html, 0, 0, 800 ,600

[SimbolFSReborn]

Be aware if you converted the screens materials from MSFS 2020 material to MSFS 2024 material the new emissive values need to be adjusted or the screens will remain black!

I did fall for this trap last night, and after 5 hours of not having avionics at all, I decided inspected the GLTF for the TBM Asobo plane and Xcub and noticed their screens emissive factor was set to 3500. Where in MSFS 2020 this was set to 1.

@Boris I think is important to put this somewhere in the SDK documentation, in the past we could see how to configure the screen textures for avionics with the DA62 sample, unfortunately because now the G1000 were done as an attachment, and the attachment is compiled, etc. we are unable to inspect:

• How to create the screen texture properly for MSFS 2024, for example the emissive factor, textures for occlusion to optimise reflections, and others parameters.

• What to include in the .xml behaviours for G1000 and G3000, I am still trying to figure out the G3000..

• How to program the dials, buttons, animations, etc.

We had all these available via the DA62 example for MSFS 2020, and in MSFS 2024 now is gone.. totally blind.. Although I appreciate we could just do the G1000 as an attachment, the reality is, with airplanes being so different from one to another, that, we need in many occasions do our own in order to integrate things properly, from AO, Texturing, Avionics behaviours, etc.

Best,
Raul

[CoffeeCorn12816]

I’ve wasted two days with this mess. I’ll do other things now and hope this gets fixed in the next weeks!

[CoffeeCorn12816]

what to do with such? it’s not even sent automatically?

[EPellissier]

@CoffeeCorn12816

A new 2024 restriction? I can’t get more than 4 screens.

There’s no such restriction in MSFS 2024 - there must be something wrong with your aircraft setup.

@CoffeeCorn12816

I’ve wasted two days with this mess. I’ll do other things now and hope this gets fixed in the next weeks!

When you provide more information about your issue we might try to help.

@CoffeeCorn12816

what to do with such? it’s not even sent automatically?

No they’re not, please upload them somewhere as instructed in section 3 of How to report a bug or crash

Best regards,

Eric / Asobo

[EPellissier]

@SimbolFSReborn

unfortunately because now the G1000 were done as an attachment, and the attachment is compiled, etc. we are unable to inspect:

Can’t you use the VFSProjector to browse to SimAttachments\Instruments\Asobo_MPA_G1000_Autopilot_NoYawDamper\model\GRM1000_AutoPilot_NoYawDamper_LOD00.gltf?

In there you should see:

            "emissiveFactor": [
                3500.0,
                3500.0,
                3500.0
            ],
            "name": "GRM1000_Screen",
            "extensions": {
                "ASOBO_occlusion_strength": {
                    "strength": 1.2
                },
                "ASOBO_tags": {
                    "tags": [
                        "Collision"
                    ]
                }
            }
        },

That being said, and as discussed in another thread, it would be better to have a migration guide with all these required steps described.

Best regards,

Eric / Asobo

[SimbolFSReborn]

Yea this is exactly what I did at the end, opened a GLTF to see what it had before giving up and it is how I discovered the emission factor of 3500.

If I didn’t, I would still probably trying to work out why my G3000 avionics were black lol.. I knew the avionics were alive because coherent inspector showed them as “turn on” in the console.. so, at the end it was the emission factor.

My point is, most people would open the DA62 example and try to work out how to setup screens, but now those are not part of the 3D art you see. So yea, if we have a guide or something for new developers it would be great.

This emission factor of 3500 is no writing anywhere in the documentation, so is pretty easy to be missed for any avionics, etc.

Best,
R.

[CoffeeCorn12816]

@EPellissier

            "emissiveFactor": [
                3500.0,

What are you using now? thanks

[SimbolFSReborn]

This is how you set the screens textures emissive inside your 3D art.

In MSFS 2020, you set the emissive colour to white, and emissive factor to 1.

In MSFS 2024, you have to set the emissive colour to white, and the emissive factor to at least 3500.

I do this in 3DMax, the 3DMAx materials documentation tell you where to do it. I have no idea how to do it on Blender, because I only work with 3DS.

Best,
Raul

[CoffeeCorn12816]

Thanks with changes to my panel.cfg it works. Also changed to 3500

[frasenci]

Thank you Sir. Powerfull Tool you made me discover. I landed here in the quest of finding a valid Texture = $… sentence in panel.cfg to make a custom wasm gauge to show up in a variant of bell407 I finnally managed to create. My custom wasm module loads ok ( wasm debugger window ) … just can not make it show visible feedback inside the cockpit. Initially , I am using an modified wasm code adapted frpom wasm aircraft sample vars and events ( lcd screen ) which works ok when mounted into wasm aircraft example. I would be very thankfull if you can guide me find the right texture …