Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Orange or Blue?
Red or Green?
-
Most likely solution is to turn on VRR/G-sync.
I can run Cyberpunk at max settings with no issues so I'm pretty sure yes, I can.
GC: 4080 Super
Processor: i7 14700F
HD: NVME drive
Memory: 32gb DDR5
I don't understand the orange / blue / red / green question but I'll check out vrr/gsync
Orange = Ryzen/AMD
Blue = intel
Red = Radeon/AMD
Green = Nvidia
In case other people might have this issue in the future, another reason I found out, is if you're watching a video before you log into the game, then try to play, the game will do this stuttering/rubberbanding. However, if you close the video, while the game is already running, then load the video again, the issue stops.
I am almost always watching a video while playing this game so this is relevant info for me as well
Same here. I get it with watching Netflix, Prime, or a standalone video off my hard drive. I wonder why having a video load before the game loads, make the game stutter, but not afterwards.
Bad windows memory allocation, always been an issue to some degree, was worse back when windows was 32bit (4GB limit).
That's a good point.
Your comment also reminded me to do something. Even though this is possibly not an end-user induced problem, as a just-in-case, I'm going to run a Memory Diagnostics test next time I start up my PC, just to be sure it's also not my RAM.
If you have any other ideas, please share your wisdom. I've been having this problem sporadically with Windows 10, but quite a lot more noticeable with Windows 11.
memtest[www.memtest86.com]
I have been doing this line of work for about 20 years and I can't count how many times Windows diag told me the hard drive or memory was bad when I know for a fact it wasn't.
Please, for the love of whichever god you believe in, don't EVER depend on Microsoft's half-hazard software. They put very little effort into their built-in software and put in even LESS EFFORT in testing it. It's only there to give the impression that they care for users as a company, in order to preserve their reputation and appease shareholders and investors. That's it.
[MY RANT/THEORY] Although windows built-in diag tools have improved over time, they continue to fall short for a variety of reasons. One of the primary causes is Microsoft's [nasty] business practices, which encourage you to think that your computer is broken when it isn't, so they can profit from your increased expenditure on replacement parts. That's the short, straightforward gist of it. It's like going to a doctor and they tell you theres something wrong when there's not.
And if you don't believe it, then ask yourself this one simple question.
Why does the world's largest, most influential, most profitable, and most innovative company still fail to offer the BEST security and hardware testing software in 2025?
/End rant --Sorry I ad to get that off my chest when I read your post lol. It irks me that much.
To redescribe the problem: It's like a positional desync and rubberbanding in single player.
Changing my refresh rate to 60hz on my monitor fixed this; give that a shot (settings-home-display-advanced)
Thanks for the heads up and reminder James. I totally forget about memtest. I haven't used it for quite a few years.
To be pedantic, that's a workaround. It should work at any refresh rate. Thanks for the suggestion it indeed stopped it but a driver update seems to have cleared it up for me. That computer can now run it without any problems above 60hz.
I decided to look at what nvidia drivers that other computer was running. It was running 560.11. So a bit old. I updated to the latest 566.36 and that seemed to fix it for that computer.
Maybe 560.11 had problems with Win 11 24h2...