The Witcher 3 From a HairWorks regression to repeatable captures.
After updating from patch 5.00b, I noticed that HairWorks hair looked worse indoors, with more visible shimmering. I first saw it in 5.00c, and it was still there in 5.01. I wanted to understand what had changed and whether I could recover the earlier appearance.
Comparing the builds helped me narrow the change down to the hair-rendering pipeline. I then tested a hybrid configuration that combined the earlier rendering components with the newer game data. In the scenes I checked, it brought back the appearance I had seen in 5.00b.
Getting a closely matched pair of screenshots felt almost impossible at first. To make these comparisons easier, I developed a mod that lets me run multiple instances of the game, hold Geralt still and save both his position and the camera setup. I can then load that setup in the other instance, matching Geralt's position and the camera angle across builds.
Drag the image divider, or focus the image and use the arrow keys.
These images have different aspect ratios. Use matched captures before describing this as a controlled comparison.
Original in-game captures, matched with the mod. Still images can't show temporal shimmering, and these checks aren't a game-wide validation of the hybrid configuration. 5.00b full resolution · 5.01 full resolution.
Recording and replaying benchmark routes
I also built a mod that records character movement, camera motion and pauses, then replays the sequence automatically. Saved routes stay available between game sessions, so I can run the same sequence under different settings without recreating every movement by hand.
In this video, I record a route and replay it to compare path tracing, path tracing with DLSS 5, and rasterized rendering.
- Comparable captures
- Matching Geralt's position and the camera across builds makes it easier to see what actually changed, instead of lining up shots by eye.
- Repeatable test sequences
- Replaying the same route for each configuration keeps the movement consistent between runs, which makes visual and performance comparisons simpler to set up and repeat.
- What they are, and aren't
- These are practical tools I built for my own testing, not a certified lab methodology. They reduce the variation that comes from manual movement, but results still need checking across repeated runs.









