Version: SU4 & SU5
Frequency: On some users
Severity: High
Marketplace package name: Kodiak 100 FS2024 2.1.7
Context: Community/Marketplace
Some customers report that the landing lights point in the wrong direction -ie. up -, or point forward but don’t illuminate terrain. No developer or tester has been able to reproduce it internally.
Here is a shot of correct lighting:
And here is a customer video showing the broken behavior:
What could be causing it?
Just adding that it looks like the same issue that happens for some people with some default aircraft (I have also not been able to reproduce): Landing Lights not shining on the ground anymore - Bug Reporting Hub / Aircraft & Systems - Microsoft Flight Simulator Forums
Did you set local position and local rotation in all your light defs?
Building for marketplace now flags these as being mandatory in it’s warnings.
Even if helpers are used, you still have to set these with 0,0,0
If only a few are set then light defs will start bleeding into each other ( you could see this in the old user lights tool as rotation and positions using the exact numbers from a previous def)
You can also see this happen on 2020 aircraft used in 2024. They would work perfectly in 2020 but in 2024. Fix is the same, add the position and rotation.
Yep, position and rotation are present, 42/42. Here are my left landing lights as an example.
lightdef.9=Type:5#Index:1#LocalPosition:-5.213000,-20.959000,3.371000#LocalRotation:6.000000,0.000000,-4.000000#EffectFile:LIGHT_SWS_Kodiak_Landing#PotentiometerIndex:1#EmMesh:l_landing_light
lightdef.10=Type:5#Index:1#LocalPosition:-5.213000,-20.959000,3.371000#LocalRotation:6.000000,0.000000,-4.000000#EffectFile:LIGHT_SWS_Kodiak_LandingOuter#PotentiometerIndex:1#EmMesh:l_landing_light
lightdef.11=Type:5#Index:1#LocalPosition:-5.213000,-20.959000,3.371000#LocalRotation:6.000000,0.000000,-4.000000#EffectFile:LIGHT_SWS_Kodiak_LandingAmbient#PotentiometerIndex:1#EmMesh:l_landing_light
Tell them to clean their community folder.. most likely an add-on has overriden default effects.
I got tired of this behavior, and stopped using any default lights effects in MSFS, I build my own always now, avoiding this issues..
R.
I thoight about that, but ours are custom too.
could be also something is overriding those.. your Kodiak is very famous.. and you will be surprised how modders put these effects out there to try to make things “better”.
A simple VFS inspection would confirm.
R,
I could see indeed that Alex (@SWS-AlexVletsas) is calling his own effects just checking on the CFG code shared above, but yes as Raul (@SimbolFSReborn), there unfortunately are modders who want to “improve” the overall work but this causes breakages as reported, regardless of whether the aircraft implements default or custom FX. I am not against modders’ work but it is something I audit a lot on my development because of such incidents. A VFS inspection as Raul suggests is the only way to find that out.
Regards,
Carlos Daniel González Gómez
NextGen Simulations
We will rename all the effects to “_v2” in case there is a conflict with the 2020 ones, but we won’t know if this works until the update is released.
If anyone has another pointer, I am happy to try it!
Some claim a sacrifice to the Gods can do wonders.. 