I am using Drwzeiki Design RJAA Narita and noticed that at night there are way too many blue lights. Does anyone else have this?

Known bug. It's happening at a lot of payware airports.

https://forums.flightsimulator.com/t/most-addon-airports-have-taxiway-lights-posts-on-runways-after-uk-update/366409/18

Edited February 17, 20215 yr by DJJose

Thanks

Same here...

I'm assuming that this is an Asobo related issue and that they need to issue a fix?

Let's hope they publish a fix soon and not waiting until March or April for the sim update 😅

 

Edit: It is breaking all 3PD airports. Why do they have to break something on every update 🥴

Edited February 17, 20215 yr by omarsmak30

This sucks. I won't fly at night until this is fixed and I hope it won't take long either.

Asobo really needs to push their updates to 3PD's and testers 1 week prior to release. Just push all release dates ahead 1 week and use it as a "test for bugs" period.

We are not a test team, but Asobo keeps using us as one.

9 hours ago, captain420 said:

This sucks. I won't fly at night until this is fixed and I hope it won't take long either.

Depends on the addon count you have, I guess every single addon showing this bug needs to be recompiled completely new...

Can perhaps @virtuali verify this if we need an update from 3PD or if we need an update from Asobo? Because it happens as well in all FSDT airports that I have.

2 minutes ago, omarsmak30 said:

Can perhaps @virtuali verify this if we need an update from 3PD or if we need an update from Asobo? Because it happens as well in all FSDT airports that I have.

We have been posting and explaining this all over:

it's a simulator bug that likely came out with enhancement that has been made to the "Light Row" feature of the Scenery Editor, which are not backward compatible at the binary level with sceneries that used it, which is not by design, Asobo has confirmed to us .BGL files should always be backward compatible so yes, it's a bug,.

And no, it doesn't affect only 3rd party airports. You might mislead it does, because default airports seldom use this feature, but sometimes they do, so they are affected as well, up to the point the relevant thread on the Flight Simulator forum that was originally titled with only the "addons" word, has now been renamed to include "(and default)"

https://forums.flightsimulator.com/t/many-addon-and-default-airports-have-taxiway-lights-posts-on-runways-and-other-airport-locations-after-uk-update/366409/44

And yes, Asobo is looking into it right now.

11 hours ago, WestAir said:

Asobo really needs to push their updates to 3PD's and testers 1 week prior to release. Just push all release dates ahead 1 week and use it as a "test for bugs" period.

We are not a test team, but Asobo keeps using us as one.

They're working on it.

We released a fix right now, just run the FSDT Live Update to get it.

This will only work for FSDT and Simmarket customers. If you bought the scenery on the MS Marketplace, you'll have to wait for it to be approved for release, we don't know exactly how much time it will take ( I guess many other developers are sending their patches now ), but we sent the update to the MS Marketplace right now.

Now, before anyone asks "why FSDT is releasing a patch, when they keep saying it's a bug in the sim and it's MS/Asobo that should fix it ?", I'll explain exactly what's really happening here:

It's very well know that it's enough to just recompile the scenery with the latest simulator/SDK to fix the taxiway lights problem, we found this hours after the update came out and I've explained it on the SDK section of the official MSFS forum too, so that's hardly news.

However, not all sceneries can be patched this way, because of ANOTHER BUG in the scenery compiler: if a scenery contains more than one Projected Mesh ( custom ground textures/markings/etc. ) it's not possible to compile it with the new SDK, because the resulting scenery won't show up all the ground textures correctly. It's clearly a new bug, because the same scenery compiled with the old SDK works just fine, but with messed up taxiway lights. This bug happens only if the scenery has at least TWO Projected Mesh elements.

The messed up lights affects ALL our airport EXCEPT Quiberon ( because it's a day only airport with no lights ), but Key West contained only ONE Projected Mesh, so it's the only one we could recompile without losing any ground textures/markings.

So, we fixed what we could from our side, that is KEYW, but for the others, we must wait for a real fix in the sim.

Edited February 19, 20215 yr by virtuali

44 minutes ago, virtuali said:

We released a fix right now, just run the FSDT Live Update to get it.

This will only work for FSDT and Simmarket customers. If you bought the scenery on the MS Marketplace, you'll have to wait for it to be approved for release, we don't know exactly how much time it will take ( I guess many other developers are sending their patches now ), but we sent the update to the MS Marketplace right now.

Now, before anyone asks "why FSDT is releasing a patch, when they keep saying it's a bug in the sim and it's MS/Asobo that should fix it ?", I'll explain exactly what's really happening here:

It's very well know that it's enough to just recompile the scenery with the latest simulator/SDK to fix the taxiway lights problem, we found this hours after the update came out and I've explained it on the SDK section of the official MSFS forum too, so that's hardly news.

However, not all sceneries can be patched this way, because of ANOTHER BUG in the scenery compiler: if a scenery contains more than one Projected Mesh ( custom ground textures/markings/etc. ) it's not possible to compile it with the new SDK, because the resulting scenery won't show up all the ground textures correctly. It's clearly a new bug, because the same scenery compiled with the old SDK works just fine, but with messed up taxiway lights. This bug happens only if the scenery has at least TWO Projected Mesh elements.

The messed up lights affects ALL our airport EXCEPT Quiberon ( because it's a day only airport with no lights ), but Key West contained only ONE Projected Mesh, so it's the only one we could recompile without losing any ground textures/markings.

So, we fixed what we could from our side, that is KEYW, but for the others, we must wait for a real fix in the sim.

If we choose to wait, are you confident that ASOBO will release a fix that will get us back to where we were before the patch?

Edited February 20, 20215 yr by DJJose

33 minutes ago, DJJose said:

If we choose to weight, are you confident that ASOBO will release a fix that will get us back to where we were before the patch?

Absolutely, the only thing we don't know it's when and how ( as an hotfix, or part of the upcoming Sim update ), but there's no doubt they'll fix it.

Edited February 20, 20215 yr by virtuali