starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Bad HiDpi scaling #4389

New issue

Closed

opened 2026-02-21 17:17:32 -05:00 by deekerman · 27 comments

deekerman commented

2026-02-21 17:17:32 -05:00

Owner

Originally created by @CaesarRulezzz on GitHub (Jun 20, 2016).

After latest release i'm having scaling issues: blurry fonts and images. Looks like app is not suppurting working in HiDpi mode. On v3.3.4 everything where fine!

qBittorrent: 3.3.5
Qt: 5.6.1
libtorrent: 1.0.9.0
boost: 1.61.0
OS version: Windows 10 1151

Originally created by @CaesarRulezzz on GitHub (Jun 20, 2016). After latest release i'm having scaling issues: blurry fonts and images. Looks like app is not suppurting working in HiDpi mode. On v3.3.4 everything where fine! # ![default](https://cloud.githubusercontent.com/assets/3651057/16189323/8307cce8-36e2-11e6-9ff7-b022fc4fba8b.jpg) qBittorrent: 3.3.5 Qt: 5.6.1 libtorrent: 1.0.9.0 boost: 1.61.0 OS version: Windows 10 1151

deekerman

2026-02-21 17:17:32 -05:00

closed this issue
added the
OS: Windows

GUI
labels

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jun 20, 2016):

Open qt.conf with a text editor (in qBittorrent installation directory)
change dpiawareness=0 to dpiawareness=1

Does it solves the issue?

UPDATE: you can set the file to read-only, in case future updates set the value back.

@Chocobo1 commented on GitHub (Jun 20, 2016): Open `qt.conf` with a text editor (in qBittorrent installation directory) change `dpiawareness=0` to `dpiawareness=1` Does it solves the issue? UPDATE: you can set the file to read-only, in case future updates set the value back.

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@CaesarRulezzz commented on GitHub (Jun 20, 2016):

Yes! This file was reseteted to stock by updater?

@CaesarRulezzz commented on GitHub (Jun 20, 2016): Yes! This file was reseteted to stock by updater?

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jun 20, 2016):

Yes! This file was reseteted to stock by updater?

yes.

@sledgehammer999
I don't intend to modify the dpiawareness value again, the best value will vary for everyone (for me 1 is worse than 0). Keeping to 0 is the safe option IMO.

@Chocobo1 commented on GitHub (Jun 20, 2016): > Yes! This file was reseteted to stock by updater? yes. @sledgehammer999 I don't intend to modify the `dpiawareness` value again, the best value will vary for everyone (for me `1` is worse than `0`). Keeping to `0` is the safe option IMO.

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@nZeus commented on GitHub (Jun 20, 2016):

Hi Chocobo1,

I have just upgraded to v3.3.5, I'm using Win10 with UltraHD resolution.

In my case, dpiawareness = 1 gives blur fonts but more or less good icons.
dpiawareness = 0 gives correct font scaling and very small icons.

Both solutions are bad and have annoying leftovers.

I like qBitTorrent, but these UI issues exist for more than half a year and I wonder if you guys have any ideas how they can be fixed? I would like to help you to find the solution, but I am not familiar with qt, I'm a web developer.

Kind regards,
Ilia

@nZeus commented on GitHub (Jun 20, 2016): Hi Chocobo1, I have just upgraded to v3.3.5, I'm using Win10 with UltraHD resolution. In my case, `dpiawareness = 1` gives blur fonts but more or less good icons. `dpiawareness = 0` gives correct font scaling and very small icons. Both solutions are bad and have annoying leftovers. I like qBitTorrent, but these UI issues exist for more than half a year and I wonder if you guys have any ideas how they can be fixed? I would like to help you to find the solution, but I am not familiar with qt, I'm a web developer. Kind regards, Ilia

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@qTorrent commented on GitHub (Jun 23, 2016):

To DEV. You can make an option in the settings?

@qTorrent commented on GitHub (Jun 23, 2016): To DEV. You can make an option in the settings? ![default](https://cloud.githubusercontent.com/assets/20108196/16300141/0d5a9bc6-3947-11e6-9a53-fddb9d6f148e.png)

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 4, 2016):

My impression is that we can't control this programmatically. @Chocobo1 am I wrong?

@sledgehammer999 commented on GitHub (Jul 4, 2016): My impression is that we can't control this programmatically. @Chocobo1 am I wrong?

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jul 5, 2016):

My impression is that we can't control this programmatically. @Chocobo1 am I wrong?

It should be possible to provide a setting, but the optimal value will differ from user to user.
You just need to replace the value in qt.conf

WindowsArguments = dpiawareness=0  # or 1

@Chocobo1 commented on GitHub (Jul 5, 2016): > My impression is that we can't control this programmatically. @Chocobo1 am I wrong? It should be possible to provide a setting, but the optimal value will differ from user to user. You just need to replace the value in `qt.conf` ``` ini WindowsArguments = dpiawareness=0 # or 1 ```

deekerman commented

2026-02-21 17:17:37 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 5, 2016):

You just need to replace the value in qt.conf

We cannot do this. "Program Files" folder isn't writable by non-admin processes.

@sledgehammer999 commented on GitHub (Jul 5, 2016): > You just need to replace the value in qt.conf We cannot do this. "Program Files" folder isn't writable by non-admin processes.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@ngosang commented on GitHub (Jul 7, 2016):

Please, go back to dpiawareness=1 in next release.

@ngosang commented on GitHub (Jul 7, 2016): Please, go back to `dpiawareness=1` in next release.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@tekko commented on GitHub (Jul 7, 2016):

The new auto scaling helps?
http://doc.qt.io/qt-5/highdpi.html

@tekko commented on GitHub (Jul 7, 2016): The new auto scaling helps? http://doc.qt.io/qt-5/highdpi.html

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@qTorrent commented on GitHub (Jul 22, 2016):

Are you going to add feature "DPI awareness" in the program interface? Edit the file "qt.conf" every time is not very convenient. Please make an option in the settings.

@qTorrent commented on GitHub (Jul 22, 2016): Are you going to add feature "DPI awareness" in the program interface? Edit the file "qt.conf" every time is not very convenient. Please make an option in the settings.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@regs01 commented on GitHub (Jul 28, 2016):

DPI awareness works well on controls and text, though it doesn't scale forms and icons.
https://yadi.sk/i/0x6hL2t0tiWtw

It needs some hidpi iconset.
16x16
20x20 for 125% (for some hidpi notebooks)
24x24 for 150% (1,5x on larger 4K screens)
32x32 for 200% (2x on smaller 4K screens or 1800p notebooks)
48x48 for 300% (3x on larger 8K screens)
64x64 for 400% (4x on smaller 8K screens)

There are some good multisize GPL and CC-BY iconsets for app devs, like Farm Fresh from Fatcow

@regs01 commented on GitHub (Jul 28, 2016): DPI awareness works well on controls and text, though it doesn't scale forms and icons. https://yadi.sk/i/0x6hL2t0tiWtw It needs some hidpi iconset. 16x16 20x20 for 125% (for some hidpi notebooks) 24x24 for 150% (1,5x on larger 4K screens) 32x32 for 200% (2x on smaller 4K screens or 1800p notebooks) 48x48 for 300% (3x on larger 8K screens) 64x64 for 400% (4x on smaller 8K screens) There are some good multisize GPL and CC-BY iconsets for app devs, like Farm Fresh from Fatcow

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@koloved commented on GitHub (Sep 23, 2016):

i'm artist and I can help with icons, only tell me about it

@koloved commented on GitHub (Sep 23, 2016): i'm artist and I can help with icons, only tell me about it

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Sep 24, 2016):

@koloved
FYI: #4253

@Chocobo1 commented on GitHub (Sep 24, 2016): @koloved FYI: #4253

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@lfuser commented on GitHub (Apr 12, 2017):

This seems related to how bad Win10 handles HiDpi compared to Win7/8.
HiDpi users on Win10 might notice that many screens, even from Windows itself, looks blurry (e.g. Device Manager). A more through explanation and fix can be found here: http://windows10_dpi_blurry_fix.xpexplorer.com/

When installing v3.3.12 without the fix on a fresh install everything was blurred. After applying the fix above it looks as it should, without modifying anything on qBittorrent (i.e. didn't modify the DPI awareness on the config file). It's the same on many other applications.
Hope this helps someone or the devs in finding a workaround.

@lfuser commented on GitHub (Apr 12, 2017): This seems related to how bad Win10 handles HiDpi compared to Win7/8. HiDpi users on Win10 might notice that many screens, even from Windows itself, looks blurry (e.g. Device Manager). A more through explanation and fix can be found here: http://windows10_dpi_blurry_fix.xpexplorer.com/ When installing v3.3.12 without the fix on a fresh install everything was blurred. After applying the fix above it looks as it should, without modifying anything on qBittorrent (i.e. didn't modify the DPI awareness on the config file). It's the same on many other applications. Hope this helps someone or the devs in finding a workaround.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@ngosang commented on GitHub (Apr 17, 2017):

@Chocobo1 could you take a look?

@ngosang commented on GitHub (Apr 17, 2017): @Chocobo1 could you take a look?

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Apr 17, 2017):

@Chocobo1 could you take a look?

From the website:

If you are using the latest version of Windows 10 (Creators Update) you might not need this DPI Fix

@lfuser
It would be interesting to see you post some screenshots: one with the XPExplorer fix, another with the DPI awareness fix in the config file.

@Chocobo1 commented on GitHub (Apr 17, 2017): >@Chocobo1 could you take a look? From the website: >If you are using the latest version of Windows 10 (Creators Update) you might not need this DPI Fix @lfuser It would be interesting to see you post some screenshots: one with the XPExplorer fix, another with the DPI awareness fix in the config file.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@regs01 commented on GitHub (Apr 17, 2017):

~~Redstone 2 has ability to enforce dpi awareness. Not more than that. Scaling still should be performed by the app itself. Considering that most portion is being drew natively it's not a big deal. But icons still needs to be properly sized. I posted a little workaround in another issues for that which could be added into form creation procedure.

Internal qt scaling does it bad. First it's drawing the image, then upscaling, making it blurry.~~

EDIT:

Reverting what i said. I thought icons should be a bit larger, but they seem to be properly sized.

If so, then only few noticeable problems - form size and column widths. But as they are resizeable, they could be easily and quickly fixed by user himself.

@regs01 commented on GitHub (Apr 17, 2017): ~~Redstone 2 has ability to enforce dpi awareness. Not more than that. Scaling still should be performed by the app itself. Considering that most portion is being drew natively it's not a big deal. But icons still needs to be properly sized. I posted a little workaround in another issues for that which could be added into form creation procedure. Internal qt scaling does it bad. First it's drawing the image, then upscaling, making it blurry.~~ **EDIT:** Reverting what i said. I thought icons should be a bit larger, but they seem to be properly sized. If so, then only few noticeable problems - form size and column widths. But as they are resizeable, they could be easily and quickly fixed by user himself.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@lfuser commented on GitHub (Apr 17, 2017):

Ok, here a bunch of screenshots. I'm on Creators Update. Recommended viewing on full size.

(1) qBittorrent with fix, dpiawareness=0:

(2) qBittorrent without fix, dpiawareness=0:

(3) qBittorrent without fix, dpiawareness=1:

As you may have noticed, (1) and (3) are roughly the same.

I guess as far as qBittorrent goes, the dpiawareness=1 solves its problems in any case (at least on W10 CU). Maybe you should consider leaving it on by default.

However, many other programs are affected by this issue, and this is why I stick with that fix. An example:
Without fix:

With fix:

@Chocobo1

If you are using the latest version of Windows 10 (Creators Update) you might not need this DPI Fix

Not true. I did notice a little improvement on Creators Update, but is still bad all around (as demonstrated above).

I just hoped to bring some clues on where the different scaling behaviors across different Windows might be coming from so you can more easily find a fix for everyone.

Cheers!

@lfuser commented on GitHub (Apr 17, 2017): Ok, here a bunch of screenshots. I'm on Creators Update. Recommended viewing on full size. (1) qBittorrent with fix, dpiawareness=0: ![qb_withfix](https://cloud.githubusercontent.com/assets/11896084/25093495/8f40d89a-2360-11e7-932e-59b1e5ef0dd7.png) (2) qBittorrent without fix, dpiawareness=0: ![qb_withoutfix](https://cloud.githubusercontent.com/assets/11896084/25093507/9f5da384-2360-11e7-97e4-3f993101cf9d.png) (3) qBittorrent without fix, dpiawareness=1: ![qb_withoutfix_dpiawareness1](https://cloud.githubusercontent.com/assets/11896084/25093539/ba67e39c-2360-11e7-9ab7-2544a5642f1c.png) As you may have noticed, (1) and (3) are roughly the same. I guess as far as qBittorrent goes, the dpiawareness=1 solves its problems in any case (at least on W10 CU). Maybe you should consider leaving it on by default. However, many other programs are affected by this issue, and this is why I stick with that fix. An example: Without fix: ![withoutfix](https://cloud.githubusercontent.com/assets/11896084/25093618/0b6a02c0-2361-11e7-91d3-46a0b749a888.png) With fix: ![withfix](https://cloud.githubusercontent.com/assets/11896084/25093625/122685d4-2361-11e7-813c-4ebc8fc07d48.png) @Chocobo1 > If you are using the latest version of Windows 10 (Creators Update) you might not need this DPI Fix Not true. I did notice a little improvement on Creators Update, but is still bad all around (as demonstrated above). I just hoped to bring some clues on where the different scaling behaviors across different Windows might be coming from so you can more easily find a fix for everyone. Cheers!

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@regs01 commented on GitHub (Apr 17, 2017):

What fix are you talking about? System (Enhanced) or Application?

@regs01 commented on GitHub (Apr 17, 2017): What fix are you talking about? System (Enhanced) or Application?

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Apr 17, 2017):

What fix are you talking about? System (Enhanced) or Application?

The link in this post:
https://github.com/qbittorrent/qBittorrent/issues/5393#issuecomment-293468340

@Chocobo1 commented on GitHub (Apr 17, 2017): >What fix are you talking about? System (Enhanced) or Application? The link in this post: https://github.com/qbittorrent/qBittorrent/issues/5393#issuecomment-293468340

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@sumon511 commented on GitHub (May 4, 2017):

@Chocobo1 the fix you are talking about only works <125%.I'm guessing you have 1080P display.

The fix doesnt really work on anything beyond 125%.I've used this on several laptops in the past.

@sumon511 commented on GitHub (May 4, 2017): @Chocobo1 the fix you are talking about only works <125%.I'm guessing you have 1080P display. The fix doesnt really work on anything beyond 125%.I've used this on several laptops in the past.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@dimon222 commented on GitHub (May 13, 2017):

4k Resolution - manual set of
WindowsArguments = dpiawareness=1

Looks perfectly clear - icons and text.

@dimon222 commented on GitHub (May 13, 2017): 4k Resolution - manual set of WindowsArguments = dpiawareness=1 Looks perfectly clear - icons and text.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@Chocobo1 commented on GitHub (May 13, 2017):

@sledgehammer999
Lots of users seems to favor dpiawareness=1 over 0, maybe it's time to make the change?

@Chocobo1 commented on GitHub (May 13, 2017): @sledgehammer999 Lots of users seems to favor `dpiawareness=1` over `0`, maybe it's time to make the change?

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@thany commented on GitHub (Aug 12, 2017):

I agree. dpiawareness=1 should be the default. Unless it causes huge problems elsewhere, in which case those problems need fixing. Hiding those problems is not the way forward. Either way, please have it enabled.

@sledgehammer999

We cannot do this. "Program Files" folder isn't writable by non-admin processes.

That is why programs can request the OS to (temporarily) elevate a process. Windows too, believe it or not, has had this mechanism for a good number of years.

@thany commented on GitHub (Aug 12, 2017): I agree. `dpiawareness=1` should be the default. Unless it causes huge problems elsewhere, in which case those problems need fixing. Hiding those problems is not the way forward. Either way, please have it enabled. @sledgehammer999 > We cannot do this. "Program Files" folder isn't writable by non-admin processes. That is why programs can request the OS to (temporarily) elevate a process. Windows too, believe it or not, has had this mechanism for a good number of years.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@regs01 commented on GitHub (Aug 12, 2017):

As a temporal workaround you can force Application scaling in Compatibility tab. It does not require elevated rights.

@regs01 commented on GitHub (Aug 12, 2017): As a temporal workaround you can force Application scaling in Compatibility tab. It does not require elevated rights.

deekerman commented

2026-02-21 17:17:38 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Aug 12, 2017):

See #7260

@sledgehammer999 commented on GitHub (Aug 12, 2017): See #7260