That’s precisely what happened to me too.
I don’t think it is mandatory to install Japan WU if you are only flying in the USA.
Zendesk it then !!! lol
Why? It a well known issue reported numerous times before that they cannot sort out, I am not wasting my time with Zendesk when they are already well aware of the update looping issue. Just re-starting the sim sorted it out.
maybe not Mandatory, but I have experienced situations, where Addon Mods for locations within the USA, are using resources “borrowed” from non USA World update.,
ie A VOR at KDCA being added, by using a VOR resource from the Japan Update.
This obviously cause an issue, in that if you do not have japan installed, you do not see that VOR rendered in the MOD, in teh USA…
NAUGHTY MODDER ( smack)
I know lol – maybe Just an excuse to post my Zendesk pic
Sometime a Picture is worth 1000 words.
1 Like
At some point there were terrain spikes at Innsbruck which where only there if you didn’t install the (unrelated) world update, can’t remember which one it was.
2 Likes
Somewhere here I read that this turbulence issue has been solved…but I am clearly missing something because I have been through all the posts but I havent seen anything about a solution…can some one please point me to the so called solution please?..
What do you mean by “turbulence issue”?
It is probably being caused by a butterfly in Brazil 
If a Butterfly Flutters It’s Wings… - Ron Mayhew (ronmayhewphotography.com)
1 Like
It is not turbulence it is a special bumpy-ness operation.
2 Likes
And it is not targeting passengers.
1 Like
One thing that crossed my mind last night…all of us who are affected by the excessive turbulence we are hellbend on saying that this is a “baked in”…and “hard coded” effect that Asobo explicitly implemented in SU9…but here is the thing…is there not a list somewhere that shows and highlights exactly what is added and fixed in each update?..isnt that the “Release notes”. ?..
Because I have gone through the latest release notes and nowhere I can see the implementation of turbulence…unless of course there are things that they implement but don’t put them in the release notes…
I mean we keep saying that this is baked in…but do we have actual proof?..we only deduce that it is baked in because of the fact that there seems to be nothing at the moment that we can do to get rid of it.
I mean…what if…something else is at play here?..take for example the fact that some are affected and others not at all…
The other reason that we “think” that it is a baked in effect is because it all started after SU9…which according to our “logic”…makes us conclude that Asobo implemented it in SU9.
I guess the only one that can truly answer this million dollar question is Asobo themselves…I wonder when the next Q&A is…
There are many instances of things being added / changed / deleted with their updates that are never mentioned in the release notes. When they are questioned about it in the Q&A, it’s like a deer in the headlights.
All I know is that something changed with SU9 in regards to the turbulence / gusts / wind in the game.
The release notes are a very simplified list of changes to appease the community – and does not detail so many of the changes actually made, (That drive developers crazy, when they are changed)
This is very bad…how can we then ever know for sure if the turbulence has been added in the update or not?..
We cant, along with many other things. Oh well.
When the release notes don’t list all the new features added it shows that the development process is close to chaotic.
Maybe listing all the changes made, in enough detail to be meaningful, has already becomes an excessively large task… and would only be of any real benefit to a small number of developers. ?
Ref: Programming complexity - Wikipedia
Programming complexity (or software complexity) is a term that includes many properties of a piece of software, all of which affect internal interactions.
According to several commentators, there is a distinction between the terms complex and complicated. Complicated implies being difficult to understand but with time and effort, ultimately knowable. Complex, on the other hand, describes the interactions between a number of entities.
As the number of entities increases, the number of interactions between them would increase exponentially, and it would get to a point where it would be impossible to know and understand all of them.
Similarly, higher levels of complexity in software increase the risk of unintentionally interfering with interactions and so increases the chance of introducing defects when making changes. In more extreme cases, it can make modifying the software virtually impossible.
The idea of linking software complexity to the maintainability of the software has been explored extensively by Professor Manny Lehman, who developed his Laws of Software Evolution from his research.
He and his co-Author Les Belady explored numerous possible Software Metrics in their oft-cited book,[1] that could be used to measure the state of the software, eventually reaching the conclusion that the only practical solution would be to use one that uses deterministic complexity models.
I sure Sébastien actually said at one of their developer blogs that they had implemented turbulence into SU9.