Artichoke

I had the same problem appear recently; it went away after disabling GSX. It's a new issue so I assume it will be fixed.

Great update. Can't wait for the F70/100!

It was more like anti-gravity or Wingardium Leviosa; the jetways lifted up slowly and started dancing around 😂. I haven't seen it happen again.

I have a similar problem with persistently low-res ground textures. It doesn't matter how long I wait or fly around; the ground will never increase in resolution. This has happened to me all over the world. Either something is wrong, or the streaming system is designed to maintain the best continuous level of quality and won't actually cache your surroundings. Preventing caching doesn't make sense to me though, so I think it is a bug. In MSFS2020, the system works fine on the same connection (and I am flying with third-party airports and aircraft in 2024, so those objects are not being streamed).

Just finished my first full flight; lots of improvements in the core engine (e.g. lighting, handling, etc.)! Unfortunately, we'll definitely need updates. Here I am departing KATL: Laser beams: After departure: Loading times are much better now, but in-game the situation is still poor. I am currently using a 30Mb/s connection, which has worked perfectly fine in 2020 for years. So, either the servers are still struggling to deliver, or my connection speed will not suffice for the increased network load.

Still haven't been able to even start downloading. The launch issues, dev issues, and in-game bugs are unfortunate because, based on the Tech Alpha, there is great potential for 2024. I do agree, however, that moving so much to the cloud causes more problems than it solves. Obviously, it is not feasible to have worldwide scenery locally, but most other things you can. There were already issues in 2020, let alone with the increased demand in 2024. I think it would have been better to keep core content local, but instead of installing everything and then having the option to remove it via the content manager, it should ask at initial launch which packages you want (similar to when you install Visual Studio or MATLAB). This would both allow users to only install what they want and reduce server load as people opt-out of downloadable content. Or, for a hybrid approach, they should ask at initial launch (not after!) what packages you want, and whether or not you want them stored locally or cached from the cloud. To end on a positive note, I certainly do not think this will kill MSFS. Eventually, we will all be enjoying it with our favorite third-party content.

Yes, from what I remember, Seb explained that they quantified the accuracy of the model and went from ~80% (I think) to >90% accuracy. Of course, we know neither what variables they used, nor which in-dev FM was used. The data itself also matters. There could be lots of data from normal flying and the model could be overfitting, so it will look good in typical scenario, but really mess up in specific other scenarios. Personally, from a "feel" perspective, I thought it felt better and more reminiscent of my own experiences flying the C172. It's the only plane I've flown, so I won't comment on any of the other ones. For more non-standard stuff, I tested stalls (not the ones I showed in the video from my other thread), and the MSFS2024 version snapped the nose down in a very characteristic way, whereas I couldn't get the MSFS2020 version to do it the same. IRL, I remember that in many of the stalls I did there was this snapping effect if the stall developed fast enough. This is but one scenario of a million, though. Ultimately, we all perceive even real life experience differently, so not everyone will agree on the feel side.