Version: 1.0.72.0
Frequency: Consistently on MSFS2020 airplanes imported in MSF2024
Severity: Low
Context: Apparently all displays in which the emissive propriety was just set in the 3D model material.
Bug description: Displays are much darker than in MSFS2020, unless the material propriety is overridden in the model behaviors (in which case brightness seems OK).
Repro steps: LONG-EZ (but actually any aircraft like this) - radio displays, autopilot and GPS are way too dark.
Emissive is not working at all during the day properly, even though I’m using textures that are emissive all day in 2020, they now have day/night cycle forced by the looks. Doesn’t really work now for scenery interiors for lighting and displays.
As far as I can see, for cockpits, if the Emissive propriety is overridden in the model behaviors (through the Material section) it works. But otherwise it does not.
@Scimmia1974 @Nick_NZASimulations - are you using MSFS2020 packages put in your 2024 Community folder or have you built MSFS2024 packages with your MSFS2020 assets?
In the first case then it’s a bug. In the second case this result is expected because lighting is calculated differently in 2024 - unfortunately we haven’t had time to finalize the migration page we wanted to add in the documentation that would explain this.
NOTE: an MSFS2020 package put in the MSFS2024 Community folder should have better lighting than that shown on the screenshot because we would detect that it comes from 2020 and adjust lighting calculations.
Best regards,
Eric / Asobo
@EPellissier apologies for not having said it explicitly. In my case I have seen this happening on MSFS2020 content imported in MSFS2024 (drag & drop in the community folder).
In general, NONE of our MSFS2020 works flawlessly in this build ATM.
Yes these are 2020 packages in 2024.
First is a non textured material from blender just using RGB values.
2020:
Next is a textured material.
2020:
2024:
From this you can see a 2020 package in 2024 acts different.
GLTF settings. No Day/Night Cycles.
Blender Material:
{
"doubleSided" : true,
"emissiveFactor" : [
3,
2.4600000381469727,
1.8899999856948853
],
"name" : "LED_Emmisive_ON",
"pbrMetallicRoughness" : {
"baseColorFactor" : [
0.4000000059604645,
0.4000000059604645,
0.4000000059604645,
1
],
"metallicFactor" : 0,
"roughnessFactor" : 0.10000000149011612
}
},
Textured:
{
"emissiveFactor" : [
1,
1,
1
],
"emissiveTexture" : {
"index" : 147,
"texCoord" : 0
},
"name" : "CeilingObjects",
"normalTexture" : {
"index" : 148,
"texCoord" : 0
},
"occlusionTexture" : {
"index" : 149,
"texCoord" : 0
},
"pbrMetallicRoughness" : {
"baseColorFactor" : [
1,
1,
1,
1
],
"baseColorTexture" : {
"index" : 150,
"texCoord" : 0
},
"metallicRoughnessTexture" : {
"index" : 149,
"texCoord" : 0
}
}
}
Hello,
I can confirm we have the same issue on our side.
All default avionics (GNS 430, GTX 335) have a correct luminosity on MFS 2020, but not on MFS 2024 (with aircraft package simply put in MFS 2024 Community folder).
Can you please specify which packages you have used that exhibit this issue?
Best regards,
Eric / Asobo
This is AzurPoly TB-30 Epsilon (sending you a download link via MP).
The two screens you see here are declared in panel.cfg like the following:
[VCockpit06]
size_mm=440,100
pixel_size=440,100
texture=$GTX330_Screen
htmlgauge00=Generic/Transponders/AS330/AS330.html, 0, 0, 440, 100
...
[VCockpit10]
size_mm=350,190
pixel_size=350,190
texture=$GNS430_Screen
htmlgauge00=NavSystems/GPS/WT430/WT430.html, 0, 0, 350, 190
And we use the associated XML templates (ASOBO_AS330_Template and ASOBO_AS430_Template).
Kind regards,
Romain
