Slinging through Manhattan was a disaster; the minimum FPS would suddenly tank to 30, making the game feel like a slideshow, which was honestly laughable. The default memory mode on the MSI PRO B760M-A was choking on the massive amount of city assets, with bandwidth utilization hitting 90%, leaving the CPU idling for data. I tried enabling every 'performance boost' setting in the drivers, but that just pushed my GPU to 80℃ without gaining a single frame—a complete exercise in futility. I went into the BIOS and forced the memory controller from Gear 2 to Gear 1, then dialed the RAM frequency to 3200MHz. In RivaTuner, the 1% lows jumped from 30 FPS back up to 52 FPS, making the swinging feel fluid. I did struggle with a couple of memory training failures after switching to Gear 1, but bumping the RAM voltage from 1.35V to 1.38V sorted it out. The motherboard core temp is now 45 - 52℃ and memory latency dropped to 62 - 68ns. Exported frame time logs show the fans are humming along steadily at 1400 - 1600RPM. Last updated onMarch 11, 2026 10:14 AM.
This drive was testing my patience; every time the game switched turns, it felt like I was watching a slideshow. Once the TiPro9000's SLC dynamic cache fills up, the write speed plummets from 7000MB/s to under 900MB/s, leaving the system in a brutal I/O wait state for 0.8-1.5 seconds. In a moment of desperation, I tried moving the game to a RAM disk, but I just ran out of memory and got a BSOD—definitely don't do that. Instead, I went into Device Manager and bumped the NVMe controller queue depth from 1024 to 2048 and enabled the forced write cache flush policy. In CrystalDiskMark, my 4K random reads jumped from 48-55MB/s to 65-72MB/s, and the turn-switching stutter felt about 50% better. I had some file corruption errors right after changing the queue depth, but that stopped once I disabled my real-time antivirus. Drive temps are now 45-58℃ and fans are humming at 1400-1600RPM. Last updated onMarch 8, 2026 9:47 AM.
This game eats RAM like a black hole. I'd be riding along and the road would suddenly turn pitch black before popping back in. My Kingston 16GB DDR4 2666 was pinned between 14.8-15.5GB, and the second it hit the ceiling, the FPS tanked. I tried dropping the settings to Medium, but the game looked like a pixelated mess—absolute torture for the eyes. Instead, I went into system settings and locked the virtual memory (page file) at 32GB and dialed the texture quality from Ultra down to High. Using Resource Monitor, I saw memory usage stabilize between 12.1-13.2GB, and the texture flickering vanished. Weirdly, my boot time slowed down by 3 seconds after the change until I disabled Fast Startup in Windows. CPU temps stayed around 62-68℃ with fans at 1300 RPM. I exported the memory curves to verify, and fan speeds stayed steady at 1300-1400RPM. It's a band-aid fix, but it works. Last updated onFebruary 21, 2026 4:24 PM.
With these high-res mods, 8GB of VRAM is honestly a joke; the memory pressure is just ridiculous. Once the Gigabyte RTX 5060 hits 7.5GB, the system starts aggressively swapping to system RAM, and my frame rate collapses from 60 FPS to a pathetic 12-18 FPS—it literally looks like a slideshow. I tried setting Power Management to 'Prefer Maximum Performance' in the NVIDIA Control Panel, but that just spiked my temps to 82℃ without adding a single frame, which was just absurd. I eventually forced the Windows page file to 32GB via the registry and dropped the texture filtering from 16x to 4x. RivaTuner showed frame time spikes of 80-120ms finally settling into a 25-35ms range. I noticed the system took an extra 5 seconds to boot after the page file change, but that was fixed once I moved the file to my NVMe SSD. VRAM usage now hovers between 7.2-7.8GB with a stable 2500MHz core clock. Exported timestamps confirm frame generation is now steady at 25-35ms. Last updated onMarch 3, 2026 10:10 PM.
The way this game munches through RAM is just ridiculous; 16GB feels like a joke here. When loading massive terrain assets, the Trident Z kit would hit 15.4GB instantly, putting the system into a severe I/O wait for 0.5-1.2 seconds, which just froze the screen. I tried closing every single background app, but other than making my chat apps useless, the stuttering barely changed—the optimization is just laughable. I went into advanced system settings, changed the processor scheduling to prioritize background services, and manually locked the page file write speed. In RivaTuner, the frame time spikes of 20-110ms finally settled into a more reasonable 15-28ms. I did run into some nasty audio tearing after the first tweak, which I only fixed by dropping the audio sample rate from 192kHz back to 48kHz. RAM temps stayed between 45-52℃. Used the internal profiler to export the logs, and the scheduling parameters are now solid. Last updated onMarch 9, 2026 7:01 PM.
