Customer support & technical troubleshooting.

I first noticed worse-looking hair and more shimmering indoors in patch 5.00c, compared with 5.00b. I wanted to reproduce the difference under closely matched conditions.

With AI assistance, I worked on the capture mod's .ws scripts for player and Photo Mode controls, including ComparisonPlayerHook.ws and ComparisonPhotomode.ws. I tested the controls in-game to hold Geralt still and save and restore the camera setup across instances, preparing his position and pose separately in each.

Build and shader comparisons helped me narrow down changes in hair rendering. In my initial 5.00b/5.00c investigation, I tested a hybrid configuration using the earlier rendering components. It recovered the earlier appearance in the scenes I checked.

The images here show a later comparison of 5.00b with 5.01, where I still observed the issue. They provide a closely matched view of the difference; still images do not demonstrate temporal shimmering, and these checks are not a game-wide validation of the hybrid configuration.

I wanted to compare lower-power GPU settings against stock behavior. I worked on Silicon Tuner and tested it on my RTX 5090 and RTX 5070, using recorded measurements to check performance, power draw and temperature.

For the RTX 5070 results shown here, I ran Cyberpunk 2077's built-in benchmark with the same game settings across three profiles. The balanced profile averaged 160.3 W at 50 FPS, compared with 230.7 W at 49 FPS for stock.

Those measurements show a power/performance trade-off in this setup. The table does not include run-to-run variation, and a one-FPS difference is not evidence of a performance improvement. The tool remains in development; these results do not establish stability across other games or hardware.

I started GameStutterLab after encountering stutters while playing. I wanted a more useful first pass through frame times and available hardware activity, so I could identify an event worth investigating and decide what to test next.

I captured a quicksave hitch in Cyberpunk 2077 and inspected the frames around it. The recorded peak was 98.79 ms against a local median of 16.57 ms, with nearby disk activity. The chart and downloadable CSV show the measured frame-time event.

The useful result is a captured hitch with timing evidence, not a confirmed diagnosis. Disk activity near the event is a lead to investigate, not proof that storage caused it. The tool is still in development, and its suggestions need validation against real gameplay.