As long as you’ve got the hardware, most games should run fine right after an install. But every once in a while, you’ll run into a game that refuses to run properly, regardless of whether you’ve got the hardware for it. This often means a long, drawn-out troubleshooting process where you measure game performance as you work your way through the settings.
So this time, I gave Claude Code the task to examine my game configurations and system logs, and figure out what needed changing. The most useful discovery it came up with wasn’t a magical graphics preset; it was how many things outside of those presets could affect your games.
Four overlapping problems, none of which a preset would have fixed
I just got my hands on FC27, and despite the game having a ridiculous amount of bugs year after year, this is one game franchise I haven’t been able to shake off since I first got it in 2021. Regardless, my HP Omen Transcend 14 should’ve been able to run the game just fine with its 8GB RTX 4060, 16GB RAM, and Core Ultra 7 155H processor. The game might strain the system, especially memory, but theoretically, it should run fine.
I couldn’t play FC26 on my laptop because the game had a bug where it would run in slow motion, no matter what graphics settings I changed. I was half afraid that FC27 would do the same thing, but thankfully it didn’t. It did have a fair amount of stuttering and frame drops, though.
I gave up after fiddling with the graphics settings, which didn’t seem to make any difference. When Claude was put on the task, it looked through the logs from my latest session and found four overlapping problems. My laptop’s charger had cut out at some point while the game was running, Windows Update had been installing during the final 10 minutes, and the CPU had reached 105 degrees Celsius and started throttling. The game itself had no frame-rate cap, V-Sync was disabled, and dynamic resolution was targeting 60 FPS despite my using a 120 Hz monitor.
This changed the question from why the game wasn’t working to why my laptop wasn’t delivering consistent performance. Claude’s explanation connected the configuration to what was happening elsewhere on the PC. But I wouldn’t treat that as proof that each issue contributed equally to the stuttering. Several things were happening together, making their individual effects difficult to separate.
FC27 became the guinea pig, and I made a backup first
A 120 FPS cap, no dynamic resolution, and a laptop that stopped coasting
When I asked Claude to fix game settings, it first backed up the game’s fcsetup.ini file. That’s important because in case Claude’s modifications break something, you’ll have a safe point to return to later. It’s always better to back up functional configuration files than to reconstruct a mystery configuration later.
It then proceeded to apply a 120 FPS cap at 120 Hz and disabled dynamic resolution. All other settings were okay, and the game itself reported that it fit in my VRAM at the high graphics settings — the default preset it chose when the game booted for the first time.
Apart from these, I switched my laptop into performance mode from the Omen Gaming Hub. Note that this isn’t the same as changing the Windows power plan to performance. Manufacturer utilities and Windows tools might control the same hardware, but they operate with different limits in mind. So if you’ve got your laptop set to high performance in Windows but the manufacturer utility has set it to power saving or balanced modes, you’re leaving both compute and thermal performance on the table.
These changes combined produced a much smoother session: FPS consistently stayed between 60 and 70 FPS, and temperatures peaked at 101 degrees Celsius. That’s an encouraging result, but a lower temperature peak and smoother gameplay don’t establish an average-FPS improvement by themselves. I also changed more than one variable at a time, so I can’t credit a single configuration edit for the entire difference.
Claude also suggested different settings for my Aurzen projector: 60 Hz with either a 60 FPS cap or V-Sync enabled. That also points out that your in-game settings should account for the display you’re using, not just graphics presets.
It also had opinions about my older games
Assetto Corsa gets a cap, Counter-Strike 2 gets Reflex
I only install games I frequently play, so I’ve got Counter-Strike 2 and Assetto Corsa installed. When Claude had a look, it rightly pointed out that optimizing Assetto Corsa would be complicated because I use Custom Shaders Patch and the Sol weather mod. Claude pointed out that the base video.ini file wouldn’t cover the entire editing workload. In the end, it just proposed capping my FPS at my monitor’s refresh rate for more stable performance and lower temperatures.
As for Counter-Strike, Claude was going up against nearly a decade of setting optimizations I’ve done on various laptop configurations for the best performance. It still pointed out that enabling Nvidia Reflex could improve responsiveness. I didn’t find as noticeable an improvement here compared to FC27, but it’s nice to see that it’s not chasing FPS figures blindly and is also focusing on responsiveness.
Claude didn’t find a secret setting, and that’s the honest part
A smoother game and a benchmark I can defend beat a longer list of tweaks
Claude Code didn’t uncover a secret setting that transformed my laptop’s gaming performance. What it did was connect problems I would otherwise have investigated separately. Its suggestions haven’t yet degraded performance on any of the games I’ve tried, but I’m yet to try it on my most challenging titles.
While an AI assistant can help narrow the search and explain what to try, the results still need checking. I’d rather finish with a smoother game and an honest benchmark than a longer list of tweaks I can’t prove actually helped.