Not yet - high DPI support is something we want to add to Slate ( UI framework) and it is fairly high on list but we haven’t had a chance to implement yet.
UPDATE - 10/12/2016
As of 4.14, we’ve add a commandline parameter to enable a High DPI / DPI Aware mode, you’ll need to pass
-enablehighdpi
to editor when you start it. There are some known issues that still need to be resolved with some UI. If you want to try it out in 4.14, give it a go and as always report any problems you encounter with any of editor UIs when in this mode.
Same HW configuration, same issue. In any case, it would probably help being able to scale down fonts and UI in general once HDPI is supported, on default setting e.g. material editor is barely usable even when maximized, since most of labels are cropped (see screenshot) and everything looks bulky and blocky. 15 inches are not much for this kind of application, but other similar editors (e.g. blender) fit this display size better.
We haven’t been able to tackle this yet, but it is still something we are committed to. It will require a concentrated effort of engineers across different teams, and we probably won’t be able to get to it until after 4.9 release. We’re tracking this as UEPLAT-352.
@StephenEllis This is unfortunately kind of issue which gets harder to solve with time as more and more features are implemented with assumption of a fixed pixel ratio. I think Epic (just like Unity) will not be able to solve this now.
There hasn’t been a lot of movement on UEPLAT-352 as it’s a large undertaking. Our engineers will need to block out a large chunk of time to do this and it hasn’t become a high enough priority to dedicate that time yet.
With UE5 soon around corner I guess there’s no point in updating it now. I hope next UIX is being reworked for ground-up and as modulable as possible. Well it’s obligatory for VR/AR and mobile/devices anyway so…
Figured I would chime in since we’ve had some activity. status on UEPLAT-352 has moved to “In Progress” and has received a higher priority (Pri-1, which is highest “Non-Blocker” priority). This is not expected to make it into 4.13, but will show up in a future release.
Unfortunately UEPLAT Jira entries are not eligible for public jira. If you’re curious about any progress, feel free to ask here.