RobJC

That really sucks, Ryan. How many days since this was reported are people still being impacted by this?

Sounds like the issues has been addressed, and this cannot impact additional users now. At least I hope that is the case!

That really sucks. Their definition of "escalate" the issue and mine are very different.

Well I don't know exactly what fixed it, but now everything works as intended. CCD 1 is the default (the high frequency cores) and when I load any game it shifts to the CCD 0 (vcache cores). Thanks guys.

A rogue update having any possibility to be pushed out to thousands in and of itself points to big internal problems. If you worked in our industry that would be blatantly obvious.

Funny how you keep editing the like count. Jfc.

The usual apologists are notably absent. Hard to defend the indefensible but i am sure they will try lol.

I guess they can write in any level of incompetence and that makes it okay, but the vast majority of users aren’t buying that argument.

There’s a vocal minority here who feel Asobo can do no wrong. But their ranks are dropping with each cluster @#$&.

Okay getting closer. With your settings the correct cores are being used for MSFS but here's the issue. When I am doing non-gaming stuff it still uses CCD 0. I want CCD 1 to be used, since those are the highest frequency cores. Still, doing better. Thanks for posting this!

Maybe try a third party uninstall program that gets rid of any debris leftover. Something like Revo uninstaller. You can use the free trial.

Sounds like they are getting closer.

You are right, things can be broken in a beta. But this rogue update that smoked people’s settings and “community” content really isn’t a new “bug”. There’s no way to really spin this into “it’s our fault for joining the beta.” Glad i only run a stock setup for 24 and don’t have anything in my community folder. I will get back in the beta once the coast is clear, but having Steam helps. Not a fan of the MS Store. Steam is way more robust.

When i set cppc to cache it does use the correct ccd but still not optimal.

I know! It is really shocking. Anyone in this business knows that these type things just don't accidentally happen. For something like this to happen there are serious flaws in Asobo's process. This is one of those issues where you can't just overlook a mistake like this. You can't just explain it away. The software guys at MS are going to be asking questions, because this isn't just one mistake. It points to a complete failure on a bunch of levels. To release anything to production, you need to go through multiple levels. 1. Preliminary evaluation of the current dev build. Call it a smoke test. Assuming this passes it goes to another team to review. 2. Merge the code to a stage environment, notify QA and have the test cases ready to run. These test cases (probably many hundreds, if not thousands) will incorporate the standard tests plus any new ones impacted by the most recent changes. BTW, the guy merging this code is a senior member of the team, so you are severely limiting who can do this step. 3. QA runs their tests and reports back with lots of bugs. 4. Development fixes those and prepares a new build. This cycle repeats until a solid build is ready. 5. Then you notify the appropriate people that a deployment to production is happening. There are sign offs for this. You need QA to sign off. You may have a handful of senior testers who also sign off. Then it gets delivered to the deployment team. Access to this final step is very limited. Bottom line: A rogue update like this should never happen unless the process Asobo is using is very loose. Remember, you can be a really talented software developer working on a big team, but that doesn't mean the process you are a part of is professional in any way. But again, look at how FS24 was released. They need to get their act together. None of these things are rocket science.