Like everyone else, I have the same error here. Only works in most airports since the latest WU patch when ini set to 1.
And again, that's precisely the reason why I took time to test the report, trying to reproduce the problem, and make a video showing it doesn't happen here. That clearly proves every report, even the most "exuberant" ( which is a way to say it was rude but no, users are never rude, aren't they ? ), is taken seriously and it's being investigated on.
Fact that, according to your report, is fixed when GSX is not using the Navdata, might indicate a problem with the data obtained from the Navdata API, which can be due to many reasons:
- You might have a scenery conflict. When GSX is using the Navdata, is inheriting every scenery conflict which before might have not, because it only reads one .BGL at a time, so it might have been able to recognize conflicts on its own. Now, with Navdata, if you have two conflicting sceneries, GSX will get all the data, good and bad, because it no longer knows where it's coming from. It's your responsibility to be sure you don't have conflicts, but that would be true regardless if GSX is used or not: you don't want conflicting scenery in any case!
- A scenery conflict might be introduced by simply forgetting to Disable the GSX Jetway replacements for an airport you have a 3rd party add-on, something you should always do. If you use MOSTLY 3rd party add-on, you might consider Disabling all GSX Jetway replacements at once, so you won't have to remember to exclude a new one when you install a new airport.
- Simconnect might just started to behave erratically, due to the simulator having reached the maximum number of Simobject allowed in a scenery ( officially documented to be 1000 ). When this happens, Simconnect either starts to respond with bad data, or not at all, and since GSX depends on Simconnect entirely from almost everything it does, if it's getting bad data or not at all from an airport because Simconnect started to act out, it will affect GSX and there's just nothing we can do about it, other than hoping Asobo will raise the object limit.
As discussed several times, the easiest way to reach the limit is to use AI traffic, especially with AI Injection. But it IS possible to reach it even without it, if the airport is detailed enough.
What you CAN do from GSX to mitigate the problem ( not fixing it, only Asobo can really fix it, by allowing more than 1000 Simobject in a scene ), is:
- Disable the "Ground Clutter" option in GSX. This will only be effective for default airports that had their jetways replaced by GSX.
- Lower the Passenger Density slider in GSX. This will reduce the number of passengers visible at any given time, which will affect the overall number of Simobjects in a scene.
But the most effective way to deal with the Simobject limit, is reducing the AI Density. If the AI traffic product has an option to disable Ground Services for AI, that's the most effective way, because each AI could generate extra 5-6 objects as ground services so, 100 AI airplanes could add 500-600 Simbojects and, if you add the airport objects, and the Jetways, it's very easy to surpass the max Simobject limit.
The real questions are: why not allow the option for navdata to be unselected so that now when I install a new airport, i open your installer, exclude 3rd party, you set it back to 0, I navigate to roaming folders, change to 1 and only after use GSX.
Because while these specific problems are less common, by disabling the Navdata, you can be SURE you'll add an entire new class of problems, which plagued GSX in previous versions, which users could easily mistakenly assume to be GSX "bugs", when in fact it was the very lack of data that couldn't be obtained in any other way. This is what will happen if you Disable the Navdata:
- GSX won't work with Marketplace airports and Asobo Premium Handcrafted airports anymore, because their .BGL are encrypted, and the only way to obtain data about the airport, is the Navdata.
- GSX won't be able to reliably identify jetways anymore, because the Navdata provided with crucial information about their location and their status, which will be lacking without it, resulting in issues like floating passengers, because the jetway wasn't correctly associated to the parking spot and there's no way to know if it even docked, all info supplied only with the SU12 Navdata.
Since the normal user doesn't have any idea about these issues, we must be sure the Navdata is not Disabled unintentionally. And those Disabling intentionally, should know what other problems they'll run into if they do, that's why the option is only accessible from the .INI and it's reset back to default with the updater, because IT IS the best choice to keep it on.
