Confirmation, we have found that all of our light rows which have custom AIRPORT - LIGHT PRESET no longer show the lights. This affects our hold short, taxiway end and custom beacon lights at all of our airports.
Using the pre-defined runway edge and runway center lights with a light row do appear to work correctly.
@FlyingRaccoon Also don’t know if your aware of this, if not i can make a report. But the Sim container passenger characters don’t always show up, sometime theyr’e invisible or show the red error man.
Also most vegetation from the scenery tab also just show a wireframe.
PHKO, PTPN, NZWR, NTTM, NTTB and WAHQ from WU Oceania are all using the same setup unless they haven’t been upgraded in the background (they’re currently not visible unless copied over from MSFS2020).
What bothers me is that the light presets have been setup in conformity with the SDK and now they are broken. And there were hands down the best and to my knowledge most performance friendly way to individually place custom taxilights that both look realistic and allow directional heading (e.g. varying colors for rwy exists depending from which side you approach them).
Update regarding 1.0.84.0:
Wireframes for attached meshes seems to be gone now but they’re not displayed at all anymore.
Light presets themselves are too faint compared to MSFS2020:
Did you have a look at @WombiiActual bug reports?
Do they cover all the issues you spotted as well?
There is an ongoing effort to fix those issues. The only one we don’t know how to tackle is the one about transformations no longer being applied on each light as this feature now relies on mass instancing to improve performances even more.
@SLH Yes, please file dedicated bug reports if not done already.
@FlyingRaccoon Issue still persist, Fs20 Packages Light globes from the light presets are still barely existent. and the Light nodes from blender/Max are still not working.
Phew, I actually think it’s still a number of problems:
The lights themselves are somewhat faint and often not visible that I could imagine that only the first vertice light gets shown (if snapToVertices=“TRUE” is active for accurate placement). I assume that’s what you mean with transformations?
My in-pavement centerlight models are of type “FakeTerrain”. For these only the wireframes are drawn:
My edge lights are a different matter. They seem to suffer from LOD bounding box limitations (or is that the transformations you mean?) and only become visible with forced LOD viewing (otherwise they’re not visible at all): LOD0-1 (parts missing):
For all these observation feel free to check out the EDDB addon mentioned above. I’m afraid I will be out of office for a week so won’t be of additional help during that time.
I can confirm that light presets have a brightness and mesh rotation issue.
I have 2 presets:
One makes use of the default RUNWAY_ApproachLight object. This one is incorrectlyoriented in the foreground of the screenshot.
The second makes use of the default ApproachLight_01_white object. This one is correctly oriented in the background (barely visible).
Orientation is still a problem in 1.0.88.0 but the meshes themselves seem to work now. Also lights are much better than before - if not even 1:1 to MSFS2020.
