hahahanoobs
Posts: 5,583 +3,367
I'm over 30 and that mindset is still annoying and lazy.History repeats itself, INTEL will be INTEL. Anyone under the age of 30 won't probably understand my comment.
I'm over 30 and that mindset is still annoying and lazy.History repeats itself, INTEL will be INTEL. Anyone under the age of 30 won't probably understand my comment.
Same for me on R5 3600 + 5600XT. Updated from 10 to 11 dev on July and it had some performance issues but now it just working as it should be. VBS was disabled by default.Rolled the dice and upgraded to Win 11 on my 5800x/Aorus Xtreme based gaming rig. Haven't seen any loss in performance. Yeah, yeah, I know - anecdotal. But seriously... my Aida64 scores are the same as they were on Win 10. So there has to be more to the story...
VBS was already disabled on my system.
MS is the who decides which updates get pushed to users.I know MS and AMD are working together on both issues, so couldn't this be both there faults? Or AMD's? I only say that, because after it was revealed that Zen 1000 series didn't have W11 support, I didn't hear any complaints from AMD.
Let's not exaggerate there. Bathesda is still the king of bugs.Have you played it recently? CP2077 on v1.31 is still a buggy trainwreck. I know because I've played this version start to finish, naively expecting the game to be more polished at this point. I heard quite a few new bugs were also introduced since v1.3. Nearly one year and several patches later, CP2077 is still buggier than a Bethesda open world RPG on launch day.
Let's get the thin foil hat on for fun: wouldn't it be pretty convenient for intel if Microsoft just didn't have time to fix a performance regression on Windows 11 big enough to get Alder Lake a great first impression on the reviews cycle, then later on when it turns out it's just basically the same than Zen3 without the unfortunate yet perfectly timed issues Microsoft is throwing at AMD well, reviews are out, orders are made and people's mind are not going to move from the "intel indeed is back!" mentality.
Now getting off that conspiracy theory I think it's just a simple case of AMD being a second-class citizen to Microsoft still: They didn't work with AMD for the initial Ryzen launch, the initial threadrippers had even more problems on Windows than Ryzen 1 and now it seems like it's the same story: intel probably gets a dedicated team of Microsoft employees working around the clock to tune in performance while AMD might get some white papers in an email several weeks too late to react in a "here you go, figure this out yourselves" kind of attitude.
Let's not exaggerate there. Bathesda is still the king of bugs.![]()
Now getting off that conspiracy theory I think it's just a simple case of AMD being a second-class citizen to Microsoft still: They didn't work with AMD for the initial Ryzen launch, the initial threadrippers had even more problems on Windows than Ryzen 1 and now it seems like it's the same story: intel probably gets a dedicated team of Microsoft employees working around the clock to tune in performance while AMD might get some white papers in an email several weeks too late to react in a "here you go, figure this out yourselves" kind of attitude.
I did with Skirim and we have a newer title we can use for comparison, right? Falout 76...Not anymore. I'm being serious. I have played Oblivion, Fallout 3 and Skyrim on launch, they were buggy of course, but I didn't experience as many glitches and bugs (including progression breaking ones) as I did with CP2077...
They didn't "lose" them, they replaced them with ignorant, incompetent Insiders.They lost their QA team about the same time they replaced all their competent UX developers with Junior Concept Artist work experience interns...
They didn't "lose" them, they replaced them with ignorant, incompetent Insiders.
I did with Skirim and we have a newer title we can use for comparison, right? Falout 76...
I think this Internet Historian video kinda sums things up rather well:
I wonder how much cash Intel gave M$ for this.
I see Microsoft is once again finding a way to help the other half of Wintel again. Every time AMD outdoes Intel,k Microsoft finds a screw them up started on socket 7 with 350 and 500 processors and continues on to this day.
Let's get the thin foil hat on for fun: wouldn't it be pretty convenient for intel if Microsoft just didn't have time to fix a performance regression on Windows 11 big enough to get Alder Lake a great first impression on the reviews cycle, then later on when it turns out it's just basically the same than Zen3 without the unfortunate yet perfectly timed issues Microsoft is throwing at AMD well, reviews are out, orders are made and people's mind are not going to move from the "intel indeed is back!" mentality.
Now getting off that conspiracy theory I think it's just a simple case of AMD being a second-class citizen to Microsoft still: They didn't work with AMD for the initial Ryzen launch, the initial threadrippers had even more problems on Windows than Ryzen 1 and now it seems like it's the same story: intel probably gets a dedicated team of Microsoft employees working around the clock to tune in performance while AMD might get some white papers in an email several weeks too late to react in a "here you go, figure this out yourselves" kind of attitude.
One would assume the MS would iron out these core/serious issues before releasing a new OS. I wonder what they were working on as a priority, visuals?
Let's get the thin foil hat on for fun: wouldn't it be pretty convenient for intel if Microsoft just didn't have time to fix a performance regression on Windows 11 big enough to get Alder Lake a great first impression on the reviews cycle, then later on when it turns out it's just basically the same than Zen3 without the unfortunate yet perfectly timed issues Microsoft is throwing at AMD well, reviews are out, orders are made and people's mind are not going to move from the "intel indeed is back!" mentality.
Now getting off that conspiracy theory I think it's just a simple case of AMD being a second-class citizen to Microsoft still: They didn't work with AMD for the initial Ryzen launch, the initial threadrippers had even more problems on Windows than Ryzen 1 and now it seems like it's the same story: intel probably gets a dedicated team of Microsoft employees working around the clock to tune in performance while AMD might get some white papers in an email several weeks too late to react in a "here you go, figure this out yourselves" kind of attitude.
Intel working with MS on the scheduler is something that actually happened. They helped each other for both the windows software scheduler and the on chip scheduler.Why not both ?
As for dedicated teams - afaik Intel has so far contributed code to every Windows version, so actual Intel coders (employees) working on the scheduler is very well possible.
So zero surprise about the ‚side effects‚ then. Seems like some things never change….Intel working with MS on the scheduler is something that actually happened. They helped each other for both the windows software scheduler and the on chip scheduler.
Intel working with MS on the scheduler is something that actually happened. They helped each other for both the windows software scheduler and the on chip scheduler.
I doubt that we'll see such things since AMD should have access to and be able to audit the compilers. If they are ever found to intentionally gimp the compiler for an OS then it would spell disaster for both Intel and MS.It would also be interesting to know which compiler Microsoft use to compile their apps. I know they produce their own compilers, but it's possible they are using Intel compiler for certain low-level stuff (such as drivers or other kernel modules).
If they do, you can bet that Intel optimizing compiler is "optimizing" the code in such a way to execute slower on AMD. Even if it produces slightly slower code for their own CPUs, but it's important that it hurts AMD more.