So just started happening C10.0.06. When I open Mixconsole or remote editor or Mediabay. The whole window below it’s menu is offset to the right with a white line to the left (see image grabs)
not sure when it started happing , could have been after the May 2020 widows update which just installed last week. I donno, can fix most things but this seems broken now, (done preference trash, safety mode etc, yada yada yada). The widow rights itself as soon as as maximize, resize etc.
Thats a bit of a pita. I find this sort of thing pretty distracting on a daily use level and there are two concerns for users.
There is only a short time peridod window in which you can roll back this update, otherwise its an image restore.
THe other thing is C10 is technically not supported anymore.
I run 2 screen 1920x1080 and this problem apears only at 2nd screen set in Windows Monitor settings.
Also in my system i tweak window borders little bit, to make them thin
That is a red herring, any win32 (not UWP) program I have tried to run the compatibility troubleshooter on, defaults to Windows 8.
So even a perfectly running programs, Windows will try running it in Win8 compatibility mode.
I would have thought that the troubleshooter would not make any changes to compatible application. Why would it apply windows 8 settings unless something sbout the application was not spot on. (honestly never ran the troubleshooter before)
If there is one thing I have learned in my 25+ year IT career, it is that the Windows Troubleshooter is useless. That piece of worthless software never ever was able to fix anything on my systems, let alone make any meaningful suggestion. Most unhelpful helper of this century and many centuries to come.
Regarding the graphics problems, there are known bugs in Windows 10 2004, some of which have also been confirmed by Microsoft (problems with old NVIDIA Drivers, Intel on-chip graphics, …).
Most unhelpful helper of this century and many centuries to come.
Errrm, i can think of quite a few things vastly more unhelpful than this but hey.
Only certain elements of the GUI are affected, those which do not have ‘always in top’. I have a hunch that it is still a Cibase coding oversight rather than the update breaking Cubase.
Anyway not going to lose any sleep over it. Just pointing out the issue.
Why make a comment like this based on zero evidence that this was the case? But I agree this is the general rule and you are correct to point it out:-)
Because being like you ,a member of this forum from day one you can always presume that this is the case otherwise it would be stated "I updated windows to update Cubase to the latest version " . That’s not the case so from my experience of this forum i stated what i stated . Being a wise one yourself (obviously ) why did you fix what wasn’t broken and then come to the forum telling Steinberg to sort out an issue because of something you just updated without find out weather there would be any conflicts first … Both Win and Mac love to throw things out and catch the developers out as you know .
Unistall the update or use a restore point and i hope that works for you
Cheers for the heads up about the update thou
