Will Dark Screens Be Fixed on 2020 Planes?

[MSFS 2024] Bug Reports
1

Version: 1.XX.XX.X

Frequency: Daytime mode in the sim

Severity: High Blocker
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)

Marketplace package name: LHC Trinidad TB21 GT if applicable

Context: Mounted in Community, MSFS 2020 running in 2024.

Similar MSFS 2020 issue: None, MSFS it runs fine.

Bug description: Dark Screens in the daytime. You can barely see that it is on, but only barely. At night they are fine. I tried doing the day time boost coding in the model XML and that didnt work.

Repro steps: Load a flight in the Trinidad TB21 GT and note the screens in daytime.

Attachments:

Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content

Daytime

Screenshot 2024-11-04 210245
Screenshot 2024-11-04 2102451386×1618 314 KB

Night

Screenshot 2024-11-04 210311
Screenshot 2024-11-04 2103112122×1645 333 KB

My question concerning this is will Asobo be fixing the dark screen issue, or is this up to us. We are just days away from release. It would be good to know now if we need to fix this ourselves, and how to fix it.

Many thanks, Team Aosbo. Hope all is well. Keep up the great work.

Bill
Lionheart Creations

2

@LyonHaart001,

Yes the plan is that this is fixed before release.
To be honest we are having an issue right now with those MSFS 2020 aircraft which did NOT connect their emissive to the sim day/night cycle - would it be the case for the LHC Trinidad TB21 GT?

Best regards,

Eric / Asobo

1 Like
3

Hello,
Same issue described here: Some MSFS2020 displays are way darker in MSFS2024 - #6 by Nick_NZASimulations

@EPellissier What do you mean by “connect their emissive to the sim day/night cycle”?

4

Hello Eric,

It was not on my planes except perhaps one screen on one plane, the newest version G3X. That had it, a recent update. But, I tried entering that into one of my planes, the Trinidad, to bring the screens back, and it didnt work. Raul had shown us a way to put this in, but for some reason, it didnt work.

This is the code I used for some of the screens in the Trinidad;

  	<Component ID="AUTOPILOT_SCREEN_FIX" Node="Autopilot Screen">
  		<UseTemplate Name="ASOBO_GT_Material_Emissive_Code">
                    <EMISSIVE_CODE>
                        (E:TIME OF DAY, Number) 1 == if{ 1.5 } els{ ( 0.5 }
                    </EMISSIVE_CODE>
                </UseTemplate>
        </Component>

Bill
LHC

5

@EPellissier

Eric, does this look correct to you? I wonder if its the Panel Config section that might be causing this. Background color. On one of my instruments in this plane, it has an entry in the panel config for ‘emissive=0’ on the Clock unit. Should these have an emissive entry?

[VCockpit04]
size_mm = 350,190
pixel_size = 350,190
Background_color=0,0,0
size_mm=1024,1024
texture = $AS430_Screen
htmlgauge00=NavSystems/GPS/WT430/WT430.html, 0, 0, 350, 190

[VCockpit05]
size_mm = 320,234
pixel_size = 320,234
Background_color=0,0,0
size_mm=1024,1024
texture = $AS530_Screen
htmlgauge00=NavSystems/GPS/WT530/WT530.html, 0, 0, 320,234

6

Fixed… @SimbolFSReborn found a mistake in the code I was using. That didnt clear it, but then I tried renaming the parts without spaces, putting in underscores, reexported the models, renamed them in the XML, and they worked.

So the day/night code fix is working, and the screens cannot (cannot) have spaces in the names, such as GNS530 Screen.

Bill
LHC

  	<Component ID="GNS530_SCREEN_FIX" Node="GNS530_Screen">
  		<UseTemplate Name="ASOBO_GT_Material_Emissive_Code">
                    <EMISSIVE_CODE>
                        (E:TIME OF DAY, Number) 1 == if{ 1.5 } els{ 0.5 }
                    </EMISSIVE_CODE>
                </UseTemplate>
        </Component>
7

@LyonHaart001,

Is it the Node attribute in the XML Component tag that created issues when including a space? Maybe our exporters replace spaces with underscores - I’ll need to check about this.

Best regards,

Eric / Asobo

8

@EPellissier - I can confirm we have this issue on our MSFS 2020 Blackbird Simulations / Shrike Simulations aircraft; they do not use the day night cycle as part of the emissive logic.

9

I have the issues on my planes. I have no emissive connected to sim day/night cycle

I tried the same xml trick on nodes (with higer values for night) :

  • it works nicely on kap140, com&nav & xpndr Asobo default screens
  • it has an heratic behavior on WT450 by night (like if 2 systems were trying to set the emissive value)

I removed the hack. I think it’s better to have that corrected globaly.
NB. it affects registrations too (Registration/Registration.html)

10

Hello Eric,

My code I had, had a bad character in it. Fixing that helped. Then when I took the space out of the 2 word name of the part, it then worked. Lights Nodes in the System Config do this also. You cannot have a space in the name or the game causes the name not to be fully read by the sim. If you close it, use an underscore, set that into the XML file as well as the part name, and make the entry for the day/night code control, then it all works fine.

Thanks to @SimbolFSReborn for the info and help on this.

Bill
Lionheart Creations

11

@EPellissier, are you refering to the gltf setting “day/night cycle” here in blender :
image

Because if I drop the 152 or the DR400 from msfs2020 in community 2024, both planes have good emissive behavior :

image
image1274×490 57.4 KB

image
image1220×438 41 KB

But they don’t seem to use it at all :

    {
      "name": "$NavCom1_Screens",
      "occlusionTexture": {
        "index": 75
      },
      "emissiveTexture": {
        "index": 76
      },
      "emissiveFactor": [
        1,
        1,
        1
      ],
      "pbrMetallicRoughness": {
        "baseColorTexture": {
          "index": 74
        },
        "metallicRoughnessTexture": {
          "index": 75
        }
      }
    },

They don’t have any specific setting in panel.cfg either

[VCockpit02]
size_mm                         = 512,70
pixel_size                      = 512,70
texture                         = $NavCom1_Screens
htmlgauge00=Generic/Radios/KX155A/KX155A.html?Index=1,          0,  0, 512, 70
12

Hello @bagolu

Negative. This would be an entry you put into the Model Interior XML file. See above. You need to customize it to the name of your screen ‘part name’, and then modify the name of that code block to be similar to what you have. NO spaces in the names.

Bill
LHC