I'll take the few bugs I've had, over the biggest technical and graphical leap in a video game, EVER. Or is it because it's not made by Sony?Yet I was told, this was a resource hog and it was just too ambitious. Maybe most ambitious for the buggiest and most unoptimized game released this year.
Yet I was told, this was a resource hog and it was just too ambitious. Maybe most ambitious for the buggiest and most unoptimized game released this year.
Consoles likely aren't using SMT currently. It's optional on the new machines, and disabled by default to attain higher base clock speeds.Consoles use AMD CPUs..
Consoles likely aren't using SMT currently. It's optional on the new machines, and disabled by default to attain higher base clock speeds.
It is plausible SMT has been disabled to fix bugs. This game definitely came in hot, and a potential flaw in SMT is that naive load balancing can end up hurting performance by not utilizing all the available physical cores. It might run faster in tests, but it also might introduce unexpected behavior elsewhere.
What's the situation on Intel?
Again, on the assumption that the snipped I posted is accurate, no. Bulldozer family chips ("0x15") are the only AMD chips that are using all threads.Would this work for FX processors? My 6300 needs all the help it can get.
Nah I'm good
You can choose to disable only on Series X|S GDK.Consoles likely aren't using SMT currently. It's optional on the new machines, and disabled by default to attain higher base clock speeds.
It is plausible SMT has been disabled to fix bugs. This game definitely came in hot, and a potential flaw in SMT is that naive load balancing can end up hurting performance by not utilizing all the available physical cores. It might run faster in tests, but it also might introduce unexpected behavior elsewhere.
What's the situation on Intel?
The thread claims there is a bug and that for AMD CPUs the game ignores SMT and only uses physical cores.
Think I read this game will use up to 12 cores so 3900X owners and up may not see any improvement with this fix as they may not be experiencing any problems with CPU performance anyway.
EDIT : There seems to e improvmments even for 3900X users.
I will have to try this.
Yeah, but they don't use Windows though.Consoles use AMD CPUs..
Well xbox uses windows. A modified version but it is still the same core.Yeah, but they don't use Windows though.
One of the claims in AMD's sensational antitrust complaint against Intel has been getting some play around the web lately. Specifically, folks are focusing on what AMD says about Intel compilers and how they react to the presence of AMD processors. Here's the meat of the claim, taken directly from the AMD complaint:
"Intel has designed its compiler purposely to degrade performance when a program is run on an AMD platform. To achieve this, Intel designed the compiler to compile code along several alternate code paths. Some paths are executed when the program runs on an Intel platform and others are executed when the program is operated on a computer with an AMD microprocessor. . . . By design, the code paths were not created equally. If the program detects a "Genuine Intel" microprocessor, it executes a fully optimized code path and operates with maximum efficiency. However, if the program detects an "Authentic AMD" microprocessor, it executes a different code path that will degrade the program's performance or cause it to crash."
DWORD getDefaultThreadCount() {
DWORD cores, logical;
getProcessorCount(cores, logical);
DWORD count = logical;
char vendor[13];
getCpuidVendor(vendor);
if (0 == strcmp(vendor, "AuthenticAMD")) {
if (0x15 == getCpuidFamily()) {
// AMD "Bulldozer" family microarchitecture
count = logical;
}
else {
count = cores; <--------------- HERE IS THE PROBLEM!
}
}
return count;
}
The problem seems to be in this GPUOpen (AMD initiative?) library file:
![]()
GPUOpen-LibrariesAndSDKs/cpu-core-counts
CPU core and thread count detection for various operating systems - GPUOpen-LibrariesAndSDKs/cpu-core-countsgithub.com
It's not Intel compiler problem but it seems that for non-bulldozer AMD chips this is returning number of cores as the thread count:
For non-AMD processors this returns the number of logical cores.
Before it was:
![]()
4 threads are not utilized (11% is windows probably)
In the video I posted earlier all of them at 60% +
But yeah with this game treats your CPU like it was Intel with monolithic design and low latency between cores, same applies to 5600x and 5800x but no other AMD CPUs, so there might be instances where performance would drop on multi CCX CPUs.
Is CP2077 the first game in "earliest access"? Where fans have to fix your game instead of your own developer?
So this will not be useful for 5600x?
Long story short this just makes changes to how scheduling is done it seems thus the up in % on usage. The game will still dip into the 40FPS range when speeding down a road regardless of difference on CPU usage.
Pretty poor for a game that doesn't really have any simulation compared to GTA & RDR. I mean GTA has simulation running for WIND for fuck sakes.
Is this you first week playing video games?Is CP2077 the first game in "earliest access"? Where fans have to fix your game instead of your own developer?