I tried with a Fast Light in SU1 and SU2 and it works well.
You can send us a blender and a sample project that reproduce the issue, I will make some test on it.
Hi @Boris
Ok we need to re do some test because we are using blender lights like for MSFS20 that worked before (aera ; spot ; point )
I will try with new MSFS24 light types…
Can you also please help with emmissive day night cycle not working please
This is not a duplicate post sorry, one is about spot light, the other we are talking about emmissive textures that can’t be set at day time with usual day / night cycle
Please explain why the day night cycle isn’t working for emmissive textures in MSFS24
If set to false , emmissive are of day and night.
Blender’s default lights objects are not compatible with MSFS2024, you’ll need to use Microsoft Flight Simulator 2024 Lights from the menu as shown in my screenshot above.
You can also convert your blender scenery to a 2024 one using the convert scenery function (see the documentation available in the blender plugin folder).
I got mixed up
I will answer you on the other post once I’ve finished investigating it.
Are you 100% sure you are using the spot from the Advanced Light / Fast Light ?
It seems to me you are still using the default blender light object.
You should have a tab called “MSFS2024 Light Parameters” where you can set the Intensity (cd) etc…
I’m sorry, but I couldn’t reproduce any of the issues you’re experiencing.
It may be caused by something specific in your project, though I’m not entirely sure.
I even modified the GLTF you sent to enable the Day/Night Cycle, and it worked as expected (built using the Project Editor).
I also used your Blender sample to create a Spot type MSFS2024 light, and it’s working just fine.
As for Spot Light support in the Scenery Editor, it’s not currently planned.
However, in SU2, you can create lights in SimPropContainers.
A cycle is, by definition, something that starts and stops repeatedly so in your case, I think the better term to use would be “permanent” illumination.
Hi @Boris ,
Yes for unknow reason it has worked 2 days after the last post here.
You’re right , i will talk about permanent illumination.
Note the fact is the balance between night and day emmissive factor isn’t the same as FS20 .
In FS20 it was perfect , an emmisive factor of 1 give us a emmissive texture perfect at night and if day night cycle of (so permanent illumination) under a cloudy day , we can see the emissive rellay clearly.
But in MSFS24 , when the emmisive factor set t 100 (goog result at night) on a cloudy day , the emmissive effect it to light , we can almost not see it .
And if put the emmissive factor more that 100 , it will be over bloomed at night.
Hi @Boris ,
to me it isn’t fixed sorry …
There is a bad emmisive rendering . So yes the day night cycle is working , but no, to us it isn’t really fixed.
ref previous post , and after many test and discussions with other devs , FS24 as a bad “day” emmissive rendering.
In FS20 when you set emmissive factor with a great rendering at night (not to strong) if set daynight cycle = false , you will have a great rendering at day , inside a building or on cloudy days. Now in FS24 it is really bad , you have to put a strong factor that makes the emmisive at night really to strong , and at day it is almost invisible.
Please do something , take any objet you can test , set day night cycle = false , test it in FS20 / convert it for FS24 , change emmisive factor as needed and check in FS24.
In MSFS2020, a mesh with an emissive value set to 1 is exported with that same value (1) in the GLTF file. However, in MSFS2024, the equivalent emissive value is now 1000, not 1.
As shown here, the GLTF on the left was exported using the MSFS2020 exporter for use in MSFS2020, while the one on the right was exported using the MSFS2024 exporter. .
Note that you can also apply a quick fix by opening your 2020 GLTF files in an editor and multiplying the emissiveFactor values by 1000.
Hi @Boris ,
I am really grateful you takes time to answer me .
But no i am sorry , it seems there is a denial on this issue .
We’ve made hundreds test and the issue don’t come from a setting or a convertion.
Yes we tried convert objets , yes we tried multuply X 1000 , yes also made native FS24 objects to test.
The result is still the same = bad rendering at day (interior or cloudy day)
It was working great in MSFS20.
Then when set the emissive factor to 1000 (= convert to FS24 )
At night it is absolutely to strong and still light at day.
So yes we can say it is working but really not as expected.
If you want we can provide any object test you need but i am sure you can compare from your side between the rendering at day of an emmissive in MSFS20 and MSFS24 , you will see the problem.
I don’t believe I’m in denial. The truth is, I’m genuinely having a hard time understanding the exact issues you’re facing and I’m here, still trying.
A few weeks ago, you mentioned:
This makes it difficult for us to follow what’s actually resolved and what isn’t.
Your initial description mentioned a custom spotlight that wouldn’t cast light on the ground, and that the day/night option wasn’t working.
Now you’re talking about emissive intensity.
Let’s clarify things: what exactly is not working right now?
Is the only issue that the emissive lighting isn’t as bright as it was in MSFS2020?
Have you already converted your project to MSFS2024?
Please consider sharing screenshots from both MSFS2020 and MSFS2024 showing the differences. A short video could also help us better understand the problem.
Additionally, if possible, provide a simple sample project (an emissive cube and a spot for example) (not a complex scenery) that we can use to easily reproduce the issue.
Hey @Boris ,
I am sure you’re not , i know what you mean.
When saying that , it isn’t pointed you but the FS24 rendering conception.
now , i am preparing the screens , i see that everthing is working finally as it should be..
I am lost , 2 weeks ago when working on LFBD Native FS24 , i stillf facing this issue and now ,the rendering is correct for the first time..
I didn’t compiled or change anything.
Maybe last WIN11 update did the thing , or maybe you did some backgrounfd fixes ( my computer is brand new and everthing up to date)
So please accept my apologies and from now we can consider it as solved.
I have no idea why because after SU2 , the same problem was there , but today , everthing looks like it should for the first time in FS24.
Thanks for your patience , next time i will use the report bug and send you many more screens and test objects
Once again thank you for your support .
All the best