Kinda surprised this wasn’t noticed at all. Well, not really… Why not get some more testers (you have test keys on Steam) so people can help. And if you noticed, why release it anyway?
2 Likes
Can Asobo tell us in today’s dev blog updates if they are planning to fix it soon? It super annoying to break things on every update !
3 Likes
“Ho my God, it’s full of stars” 
That is so sad that ASOBO brakes the sim EVERY TIME! But hey, lets make some more and more world updates. I think they should focus on the basic Sim stuff to get this finally work! It could not be the goal to make the sim even worse with every update! e.g. the new size of the airport signs… they state in the changelog, that they “adjust the signs”… hey, did they ever go to an airport and measure those signs? that is just an example, guys!
COME ON, ASOBO°!
3 Likes
any news from Asobo on this?
Bump
Asobo usually not comments on bugs introduced by the updates, unless is’t a CTD inducing bug. Fixing terrain spikes introduced by December update took them 1.5 months, so… don’t be hasty. Try to like this blue light shows.
2 Likes
While some bugs like terrain spikes have nothing to do with 3rd-party add-ons/airports, this new bug definitely affects many 3rd-party products, and of course, selling of their products.
Many users are not happy with that and they are upset with Asobo and the developers. The developers cannot do much to fix this, and when their selling is affected, they will make pressure on Asobo, I believed that. And yes, the longer and the more bugs like this will make them tired and not really ready to join with their full potentials in an unstable platform.
6 Likes
it seems the problem is still being ignored … no message from asobo about it on the development update …
Yep can confirm. Tried third party LVFR KSAN, FSDreamTeam KEYW. Very severe. Taxiway lights sprinkled all over the runway and elsewhere. Weird cause in some other airports such as Digital Design EGGP such issue doesn’t exist at all.
I have found today that the light row tool now works correctly and you can set distance between the lights or you can use the snap to vertex option, Light row object works well now. Didn’t take pics as was working on a project that may be uploaded and would be under NDA. But after loading in sim no more taxi lights misplaced and looks much better. ill fix them at an older airport I done on Flightsim.to will get a screenshot tomorrow.
1 Like
is it fixed already?
I didn’t see any problems at Flighbeam’s DEN or IAD either. I guess they do lighting differently over there. What a mess- I hope the developers don’t have to go in and manually fix all of this. There are also plenty of default airports that are plagued with blue dots- so I really hope someone is working hard into the night over at Flightsimulator Central to fix this. Meanwhile, maybe this is a good time to do some seaplane flying 
3 Likes
yeah, thats what i am doing too, going back to basics and bush flying.
They came into the forums yesterday- they’re aware of it and looking into it.
I’m just happy they listen and respond. Can you imagine how long we’d have to wait for fixes in P3D and X-plane too? At least here things get put in the queue. What amazes me however is the total lack of good quality control and beta testing before releases. How hard is it to give a new version to a sizeable pool of users to fly around and report back?
1 Like
Seaplane flying is a good idea, I really don’t feel like doing a land to land flying after seeing those infested airpots, haven’t since run my sim. I hope a workaround by the MS/Asobo dev team will arrive any time soon. Or am I too optimistic ?
Some clarifications needed here:
Q) Why the Light Row bug happens on many 3rd party airports ( and some default too ), but not on all of them ?
A) Because the issue is ONLY with the “Light Row” command of the Scenery Editor. That’s not the only way you can have taxiway lights. If you use a Taxiway with side lights, the problem won’t appear. Most of default airports use this method, and I guess some add-on sceneries use it too. The “Light Row” method is more flexible, because it decouples the taxiway path from the lights, meaning you can usually have more control over were you place a light. Some developers might have placed individual taxiway lights using custom models, so they won’t be affected by this. Of course, this last method if far less efficient.
The “Light Row” command has been improved dramatically in this update, allowing to place lights exactly where you want and use custom models too, so I anticipate everybody will use it from now on, but the unfortunate side effect of this improvement, is the update failed to maintain compatibility with existing sceneries using the Light Row feature.
Q) Why if I open the editor, the Lights gets fixed ?
A) Because if you open an existing project and Rebuild it, the new compiler will create a new .BGL using the improved “Light Row” command, and it WILL WORK
Q) So it’s enough to just recompile the scenery to be fixed ? Why don’t all developers do this ? We want our fixes and we want them now!!
A) Not so easy. There’s ANOTHER bug in the current release, that results in sceneries using the “Projected Mesh” feature not being compiled correctly, if the airport used more than one. The Projected Mesh is a very important feature that allows to do custom background for aprons, markings, etc. so a scenery using Projected Mesh cannot be recompiled, to the fix the light problems, until the Projected Mesh bug will be fixed too. We expect both issues will fixed in the next update.
Q) Why developer XX has already released a fix for the light problem and developer YY hasn’t ?
A) Developer XX might have not used Projected Mesh in the scenery, so he can just recompile and fix the lights without having most of its ground texture disappearing.
In addition to that, even for airports that COULD be recompiled now, distributing a fix might not be the easiest solution, consider all the ones sold on the MS Marketplace, what if every developer ( those that could ) sent a patch to the MS Marketplace, and they all did at the same time ? The MS Marketplace queue will just end up stuck, because each scenery will have to go through the approval again, and this might take weeks, and will also likely slow down new releases as well. And users that bought the airport on the MS Marketplace would be frustrated for having to wait, compared to those that bought on the developer site, that could potentially get the patch immediately.
That’s why, it’s best to wait for a proper fix, in the sim, because it’s not as we used an undocumented feature or a hack or some legacy method from FSX: we used a fully documented feature of the MSFS SDK, which happened to be broken by this update.
11 Likes
The problems are just there. Do you know whether one of the major payware designers has already corrected the error in its sceneries?
I hope the 3rd party developers will make a lot pressure at Asobo about this. They have to fix it asap, but i don’t expect anything after the last couple of weeks and updates. Sorry for all the great developer studios out there, but I wouldnt buy any scenery until this mess is fixed.
1 Like
There’s no error in any developer sceneries, they are fully compliant .BGLs made with the latest official version of the SDK that was current until the update got out and, due to a bug in the update, are no longer compatible, but they will automatically work again when the sim will be patched to fix this.
And, what about the fact it also happens in some default airports from Asobo , which is the reason why this very thread has been renamed adding the “(and default)” words ?
As I’ve said:
-
SOME sceneries could be fixed by recompiling with the new SDK, provided they don’t use ANY Projected Mesh (because of ANOTHER problem with the update), which excludes the vast majority of the better payware products out there.
-
Even those that didn’t use any Projected Mesh, so they could fix the light by simply recompile them with the current SDK, will still have to be distributed to users, and if they are sold on the MS Markeplace, it might easily take more time to do that than for MS/Asobo to release an Hotfix.
2 Likes