# Issue with Designer/Vision Client Launchers on Linux with HiDPI displays

**URL:** <https://forum.inductiveautomation.com/t/issue-with-designer-vision-client-launchers-on-linux-with-hidpi-displays/53712>\
**Category:** Ignition\
**Tags:** ignition80, ignition81\
**Created:** [December 3, 2021, 5:03am UTC](https://forum.inductiveautomation.com/t/issue-with-designer-vision-client-launchers-on-linux-with-hidpi-displays/53712 "2021-12-03T05:03:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mitchell-ACS](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mitchell-acs/32/30062_2.png) [@mitchell-ACS](https://forum.inductiveautomation.com/u/mitchell-ACS)\
**Post date:** [December 3, 2021, 5:20am UTC](https://forum.inductiveautomation.com/t/issue-with-designer-vision-client-launchers-on-linux-with-hidpi-displays/53712/2 "2021-12-03T05:20:12Z")

</div>

I think I resolved this myself, I noticed in the log it was still using the 1.5 value that I had given it initially, I removed the .ignition folder and launched again and then added my

```auto
"jvm.arguments": ["-Dsun.java2d.uiScale=2.0"],

```

And it looks correct now, it seems that not every element in swing respects a decimal scaling value.

---

_[View the full topic](https://forum.inductiveautomation.com/t/issue-with-designer-vision-client-launchers-on-linux-with-hidpi-displays/53712)._
