Wow impressive for a 1660ti. Guess you have a nvme ssd too? Anyway, cant stress it enough how amazing this game looks, it just doesnt get old.
Correct installed on nvme disc
Wow impressive for a 1660ti. Guess you have a nvme ssd too? Anyway, cant stress it enough how amazing this game looks, it just doesnt get old.
Oh FFS ... I wonder if it uses GPUOpen Libraries even on consoles.
AMD' cpus are underutilized due to this issue
~15% hit in minimum FPS benchmarks
AMD' cpus are underutilized due to this issue
~15% hit in minimum FPS benchmarks
Thanks for reporting this;
I got +12% improvement with the hack
default
with hex edit
It says it's deleted. Can you help me with another link?
The proposed hex string is sub-optimal, because it inverts the check instead of neutralizing it (thus potentially breaking Intel). It is safer to change the hex string to EB 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08 instead
Now here's the weirder part. The new code calculates the number of threads by checking the reported thread count. Then it would check if an AMD CPU is installed. If an AMD CPU is installed, it would then check if a FX CPU is installed. If it's both an AMD and FX, it would use the thread count that the CPU reports (which is identical to Intel, despite FX CPUs misreporting) If it's an AMD CPU, but not a FX CPU (so CPUs like Ryzen), it use the reported core count to count the number of threads (which is also incorrect because Ryzen properly reports thread count if I am correct). So on the new code, if a 4-core 8-thread Intel CPU is installed, then it would report "8" as the number of threads. if a 4-core 8-thread AMD Ryzen CPU is installed, then it would report "4" as the number of threads. If an "8-core" AMD FX CPU is installed, it would report "8" as the number of threads.
And the devs didnt find this while testing?
I think you're confused.
Devs develop.
Testers test.
Managers manage.
Internet complains.
Open the cyberpunk2077.exe with HXD (Hex Editor).
Look for
75 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08
change to
EB 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08
Ooops.
So, is this something that will need to be done every time the game is patched?
This is what I expected.1.0.4 I believe is now available for Series X? It moved to XboxOneGen9aware after the patch.
Why 45fps? Does your monitor support a multiple of that refresh rate? I capped to 40 and ran my monitor at 120hz and it was pretty good most of the time, but I missed the extra performance I got in some of the combat sandboxes that ran faster, so I went back to uncapped.So I managed to get it running on my 6600k + 2060 with RT lighting and, it looks pretty good. With a 45fps cap I'm keeping the GPU at 95% usage most of the time and the CPU is not causing any major issues.
Open the cyberpunk2077.exe with HXD (Hex Editor).
Look for
75 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08
change to
EB 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08
Allright. As Cyberpunk 2077 has finally arrived let's compare its final retail version with the very first Gameplay Demo which was revealed back in 2018. How do you like the changes?