QModMaster Blurry on High-DPI Displays? Fixes

If QModMaster looks fine on an old 1080p monitor but turns into a blurry, cramped mess on your 4K laptop screen, you are not alone. A SourceForge reviewer put it bluntly: “Windows GUI is unusable on a high-dpi display… controls are scaled properly but positioned with hardcoded pixel counts.” QModMaster is built on the older Qt5 toolkit, and this class of high-DPI problem is common to Qt5-era desktop apps. The good news: Windows gives you several per-app levers that usually make it usable again.

Honest expectation up front: the fixes below mitigate the problem — they do not guarantee a pixel-perfect UI. QModMaster is a community-maintained open-source project (LGPLv3, built on libmodbus and Qt), and as far as publicly documented releases go, no version has been announced with a rewritten high-DPI layout. If you came here hoping for an “official fix in version X,” that does not exist — what exists are workarounds, ranked below from most to least effective.

Why it happens

Qt5 applications ask Windows how much to scale text and controls, but some dialog layouts inside QModMaster position widgets with fixed pixel coordinates. When Windows applies 150% or 200% display scaling, the text grows but the boxes it sits in do not — labels overlap buttons, the register table squeezes into a corner, and everything renders through a blurry bitmap-scale fallback. The ugliness is worst when:

  • Windows display scaling is set above 100% (125%, 150%, 175%, 200%).
  • You use multiple monitors with different scaling (e.g. a 4K laptop at 200% plus an external 1080p monitor at 100%). Dragging the window across screens can re-trigger the bad layout.
  • You run QModMaster over Remote Desktop, where the remote session’s DPI rarely matches your local screen.

Fix 1: Override the high-DPI scaling behavior (most reliable)

This is the single most effective workaround, and it works per-application so it will not change how the rest of your system looks:

  • Find QModMaster.exe in File Explorer, right-click it, and choose Properties.
  • Open the Compatibility tab and click Change high DPI settings.
  • Check “Override high DPI scaling behavior” and try the two modes in order:
    • System (Enhanced) — Windows scales the app’s text crisply using its own renderer. This usually gives the sharpest result for Qt5 apps.
    • System — Windows bitmap-scales the whole window. It may look slightly soft, but layouts stop overlapping.
  • Click OK, restart QModMaster, and re-check the dialogs that were broken (Modbus settings, register table, Bus Monitor).

There is no universally “best” choice between the two — it depends on your GPU driver and Windows build. Try System (Enhanced) first; if dialogs still misbehave, fall back to System.

Fix 2: Match the monitor setup

If you run a mixed-DPI desk (e.g. laptop 200% + external monitor 100%):

  • Keep QModMaster on one monitor and do not drag it across screens mid-session. The bad layout is typically re-triggered on monitor switches.
  • As a test, temporarily set the monitor you work on to 100% scaling (Settings → System → Display). If QModMaster snaps back to normal, you have confirmed this is purely a scaling issue and not a corrupted install.
  • On Remote Desktop, set the remote session to the same scaling as your local display before connecting.

Fix 3: Lower the resolution you ask of the app

If the override in Fix 1 does not help on your machine, a blunt but effective option is to run your display at its native 100% scaling with a lower resolution while debugging Modbus (you can switch back afterwards). QModMaster is a troubleshooting tool you open for minutes at a time — a slightly chunkier desktop for one session is a fair trade for readable registers.

What NOT to expect

  • No registry hack or manifest edit is required — the Compatibility-tab override is the supported path.
  • Do not expect font-size settings inside QModMaster to fix layout overlaps; the app has no built-in DPI controls.
  • If someone on a forum claims “version X fixed high-DPI,” treat it as unverified unless the upstream project’s SourceForge page release notes say so.

FAQ

Why is QModMaster blurry only on my 4K monitor?

Because Windows applies display scaling (150–200%) on high-resolution screens, and QModMaster’s Qt5-era layouts position some controls with fixed pixel coordinates. Text scales, boxes don’t — the result is overlapping, blurry widgets.

Which “Override high DPI scaling” mode should I pick?

Start with System (Enhanced) for the sharpest text. If dialogs still overlap or crash into each other, switch to System, which bitmap-scales the whole window and is the most layout-safe option.

Does this affect my Modbus data or readings?

No. High-DPI scaling is purely cosmetic — it changes how the window is drawn, never the bytes on the wire. Your register values, timeouts, and bus traffic are unaffected.

Is there an official fixed version?

Not that has been publicly announced. QModMaster is community-maintained open source (LGPLv3); the workarounds on this page are the current practical answer.

Related Guides

Similar Posts