CPU TEMPS?

In 2020 cpu temp rarely gets into the 80s. In 2024 it is always in the low 80s, about 6 to 8 degrees hotter. Did anybody else notice this while using 2024?

Edited November 20, 20241 yr by Fielder

Yet, I'm still not able to get in 🙄.

2 minutes ago, Peter Z KCLE_EDDN said:

Yet, I'm still not able to get in 🙄.

Because they're slowly letting people in. The service is working as intended.

It does appear they resolved the issue. No wait waiting. Activated the packs, main menu and flying. 

 

Edit: I take that back. I relaunched it to see the true loading times and... Queue. 

Edited November 20, 20241 yr by styckx

5 minutes ago, Fielder said:

CPU TEMPS?

In 2020 cpu temp rarely gets into the 80s. In 2024 it is always in the low 80s, about 6 to 8 degrees hotter. Did anybody else notice this while using 2024?

Great-that should definitely be happening with greater use of your CPU via better multithreading.  

23 minutes ago, Ricardo41 said:

The problem isn't just with Asobo and /or Microsoft. 

It's also with customers who actually expected that a game that is being concurrently downloaded by millions of gamers is actually going to work from day one. 

 

They own Azure, they are literally in the business of setting theses types of high-load scenarios up, this has nothing to do with download speed, it's service related. It's network threading and poor throttling code, as it almost always is. They are going to need to check the threading and disperse the load across more servers, too many threads is the issue, not bandwidth. It's not throttling correctly, so instead they just limit the # of people as a temporary fix, pretty lame.

It's not just a game, it's Flight Simulator, if it were just a game I doubt people would spend > $10k on this thing and have holes cut in their roofs to drop a 737 cockpit in their living room. If all that weren't true, then you could call it a game.

 

Edited November 20, 20241 yr by Alpine Scenery

1 minute ago, styckx said:

It does appear they resolved the issue. No wait waiting. Activated the packs, main menu and flying. 

I'm still getting a queue when launching.

Got in finally. Cranked up the a320 and promptly fell though scenery and had to restart the flight. Now its hanging on that and I may end up getting kicked out. It was like a bridge in Munich while taxing. So very odd.

Edited November 20, 20241 yr by Lotharen

Just now, Tuskin38 said:

I'm still getting a queue when launching.

Same 😞

And I'm kind of worn out cause I didn't sleep well last night, kept dreaming about flying in a life-like scenario over a river in WA state as I kept aiming at the birds trying to bounce them off the windshield, but after I woke up, sigh.... Only but a dream, and will always remain a dream.

5 minutes ago, Tuskin38 said:

I'm still getting a queue when launching.

Me too. Pretty disappointing launch if you ask me. I am not piling on them I can see they are not too happy either, but all the same...

I've been in a queue for close to 30 minutes, and nothing, still in the queue. I wouldn't exactly call this working as intended, that's a bit of a stretch.

 

All of a sudden the loading times of 2020 don't seem so bad huh

Oh man. I have my copilot handling the coms and what fantastic animation of his face and mouth articulating the instructions.  

The fact it started in an airport I had purchased in the market is great.

I am having troubles with the thrustmaster controls to get them properly set up. But just walking the airport with the grass and trees blowing in the wind this is already a significant step up from 2020 all around. In 4k ultra it's glorious.

 

15 minutes ago, Alpine Scenery said:

They own Azure, they are literally in the business of setting theses types of high-load scenarios up, this has nothing to do with download speed, it's service related. It's network threading and poor throttling code, as it almost always is. They are going to need to check the threading and disperse the load across more servers, too many threads is the issue, not bandwidth. It's not throttling correctly, so instead they just limit the # of people as a temporary fix, pretty lame.

Will need to wait until they give more details, but more so than this being a general server-side resource allocation issue it appears to be all down to a specific endpoint (i.e. microservice API) that streams or serves specific content to the sim, and its server-side cache was not big enough to handle the load. The key though, this endpoint is in a common/critical path to various sim functionality so that caused all the delays and users being placed in queues etc.

Even so, they should have ensured all services and their programmatic or other configurations would be able to handle a load which they should've overestimated rather than underestimated. But anyways, hope they get this properly resolved in a matter of hours or a day or two max and then give us a detailed post-mortem.

As very large and complex software systems get more and more cloud centric (and MSFS 2024 is unprecedented in that sense), these kinds of teething issues are bound to occur I suppose.
 

Edited November 20, 20241 yr by lwt1971

A properly written service can easily scale a load, when all other factors are taken into account. What it cannot do is handle a ridiculous number of threads, in that case you have to disperse the load better. I mean that's the issue in this type of stuff 90% of the time, and they already said it was related to a resource location or service, so same basic thing. All it has to do is throttle down the requests. but not totally stop them. This is a hack for a poorly written module that wasn't threaded correctly, nothing more and nothing less.

 

Edited November 20, 20241 yr by Alpine Scenery