Sadly, I already must report that when enabling the newly added option (from the plug-in right-click menu) “Allow Window to be Resized” the user interface of Kontakt 6 [latest v6.4.2] renders to absolute nonsense. It is important to note, that for a split second the UI renders as expected but then instantly crashes by collapsing all the UI elements. When keeping this new option disabled, the (relative) UI stays in shape, but just like already in Cubase 10.5, it will remain really small and almost illegible. People who have dealt with these issues will know what I am talking about.
I have also tested this with LoopMash, where the UI does not natively support HiDPI/Retina either. At least here “Allow Window to be Resized” works fully as expected. I am assuming the bug with Kontakt 6 exists, because Kontakt’s interface is resizable by itself. I find it astonishing how none of the beta testers have been able to detect this major UI bug in due time… This was the number one fix I was looking forward to!
This subject absolutely deserves recognition: What I am reporting here is nothing entirely new. This issue has now been going on for already three generations starting with the introduction of HiDPI/Retina in Cubase version 10. For anyone who is unfamiliar with this problem I do want to emphasize that this has absolutely nothing to do with Microsoft Windows. In fact, for the sake of justice I want to point at their well-structured documentation, which explains this exact topic in detail, so any keen programmer can eliminate these DPI problems.
Other DAWs like Ableton and Studio One have been able to sort this out a long time ago. Three years is a long time, even for something as complex as software development. Just for the record: In Ableton Live the entire HiDPI interface of the DAW got ruined with the Windows May 2020 Update (20H1), but they managed to fix this within a month after the Windows update had gotten released, something which we Cubase users can only dream of. This goes to show fixing appearance issues like these might be tedious, but really is not rocket science.
As of now I still have no other choice but to use the Windows Magnifier tool, or disable HiDPI altogether, which would be absolutely ridiculous at this stage, since the rest of the HiDPI integration in Cubase 11 finally seems to be on point (knocking on wood!).
I do have to admit that for such a (third) paid update this is really sad and disappointing. Following these incidents, I will definitely try to sign up becoming a (real) beta tester in order to prevent these things from ever happening again. As of now I am still unsure, whether it is unawareness or rather incompetence which keeps these issues persisting. I have good hopes that with such detailed contributions it will be possible to eliminate annoyances like these, which have been creeping through the last couple of major update cycles.