Hey! Thanks for the kind words, and that's a really good question honestly.
Your reasoning makes total sense — if Lens Mode works fine with 125% scaling, it's natural to assume the capture window would too. The thing is, they actually use different capture paths internally, which is why one works and the other doesn't (yet).
The core issue isn't screen capture itself — it's how the app currently handles DPI and coordinate mapping. At 100% scaling everything lines up cleanly, but at 125% or 150% Windows and Qt can report coordinates differently (logical vs physical pixels), which causes the captured region to get offset even if the window looks perfectly fine visually.
It's something we'd like to fix, but it's not a straightforward change — the tricky part is making sure it works correctly across different scaling values, single and multi-monitor setups, mixed scaling across monitors, and different display modes. So it needs proper testing before we can ship it reliably.
For now, 100% scaling is the safest workaround for the capture window. Sorry for the inconvenience, and thanks for taking the time to explain your setup so clearly!