Do we have an estimate on timing of the new data rollout?
Just give us the world locally again. I guarantee this is all because it’s streaming. Storage space is cheap. If nothing else, at least give us the option to download everything and those that can’t can stream it. I tried to do a visual approach this morning and it cant be done. I was on top of the airport before I could even see the runway. Absolutely untenable. Make Flight Sim Local Again!
This:
Ah yes. that explains them using the ground from FS98.
Maybe just maybe, if you play a session for 10 - Max 20 minutes, 2024 can kinda look as good as 2020 at the beginning. In 2020 then came su5, where they had to dumb everything down. Pre the 3rd fix for 2024 before Christmas it was kinda like this, if you had the hardware the thing could render well, if not well then your f’d.
Since that date, for users that have the recommended/ideal hardware it runs worse than dog ■■■■.
We haven’t had the world locally since FSX. 2020 streamed the world and it was fine. Just that 2024 also streams airports and aircraft as well as all of the activities
The textures in 2020 are much sharper. The colorgrading in some areas is much better in 2020, especially in the Alps.
The first picture in each case is 2024:
Alps
Glasgow
Do you have 750 4TB drives to spare?
No, it’s not. In 2020, the world has also been streamed. The planes and WUs were stored locally and we’re talking about PB of storage for the world textures.
But if the planes and standard textures and objects were saved locally, then there would be a lot less streaming. I think that would improve the situation significantly.
Nothing to indicate this is a bandwidth issue. if it were, texture resolution would continue to improve if left over time, which it does not. And users are reporting bandwidth well in excess of maximum requirements.
Low resolution topology, short draw distances, low resolution textures, suggest this is either a LOD (level of detail) issue or a limitation in the quality of assets being sent to the user. Perhaps a bug, perhaps a requirement imposed by the developer to meet performance targets. It’s hard to say without more feedback from the dev team.