UI drawing offset randomly on Windows 10 #61884

New Issue

Dont Want · 2019-02-23T17:28:36+01:00

Dont Want commented

2019-02-23 17:28:36 +01:00

System Information
Operating system: Windows 10
Graphics card: GTX 660 Ti

Blender Version
Broken:
2.80 Beta, 779860d34e, 2019-02-22, as found on the splash screen

Short description of error
In the render window the UI is positioned incorrectly sometimes which leads to the mouse interaction being offset to the UI.

Exact steps for others to reproduce the error
Open the default project and press F12 a few times. This should render in a new window (maybe the behavior is different on single screen systems, could not try at the moment), where sometimes the UI is moved upwards.

**System Information** Operating system: Windows 10 Graphics card: GTX 660 Ti **Blender Version** Broken: 2.80 Beta, 779860d34e26, 2019-02-22, as found on the splash screen **Short description of error** In the render window the UI is positioned incorrectly sometimes which leads to the mouse interaction being offset to the UI. **Exact steps for others to reproduce the error** Open the default project and press F12 a few times. This should render in a new window (maybe the behavior is different on single screen systems, could not try at the moment), where sometimes the UI is moved upwards.

Dont Want commented

2019-02-23 17:28:36 +01:00

Added subscriber: @McLP

Gavin Scott commented

2019-02-24 21:52:46 +01:00

Added subscriber: @GavinScott

Gavin Scott commented

2019-02-24 21:52:46 +01:00

Behavior reproduced here on Windows with a single screen and Nvidia 1060. The header bar on the Image Editor in the new window shifts up and becomes mostly obscured by the Window top border area. Dragging the window by its OS window header causes it to pop back down into place. If you maximize the window then the header becomes completely invisible and there's no way to get it back short of un-maximizing the window (at which point it corrects itself).

Sebastian Parborg commented

2019-02-25 14:02:53 +01:00

Added subscribers: @LazyDodo, @ZedDB

Sebastian Parborg commented

2019-02-25 14:02:53 +01:00

@LazyDodo can you reproduce this?

Ray molenkamp commented

2019-02-25 15:14:00 +01:00

did 10 renders no issues.

Gavin Scott commented

2019-02-25 18:16:35 +01:00

The issue is specifically spamming the F12 key rapidly 2-3 times. If you wait for the render to complete each time then the window updates without issue.

Ray molenkamp commented

2019-02-25 18:44:01 +01:00

hit F12 like a maniac, still nothing. window pops up, then stalls blender pretty much until the render is finished.

Gavin Scott commented

2019-02-25 20:10:24 +01:00

Just updated to Feb 22 Nvidia drivers and built 2.80 master up to the minute. It reliably does it if I hit f12, wait til the render is complete, then quickly hit f12 twice while the mouse is over the render output image viewer.

But this issue should be super low-priority as it causes no data loss or other serious issue, and is trivially worked around by simply moving the window etc. It's definitely not a showstopper for 2.80 release, and we should maybe have a specific priority or other triage output state for such things to help prioritize 2.80 bugs if there isn't already such a convention.

Just updated to Feb 22 Nvidia drivers and built 2.80 master up to the minute. It reliably does it if I hit f12, wait til the render is complete, then quickly hit f12 twice while the mouse is over the render output image viewer. But this issue should be super low-priority as it causes no data loss or other serious issue, and is trivially worked around by simply moving the window etc. It's definitely not a showstopper for 2.80 release, and we should maybe have a specific priority or other triage output state for such things to help prioritize 2.80 bugs if there isn't already such a convention.

Gavin Scott commented

2019-02-25 20:12:36 +01:00

Here's a screenshot of the problem state just for reference

Here's a screenshot of the problem state just for reference ![image.png](https://archive.blender.org/developer/F6713562/image.png)

Ray molenkamp commented

2019-02-25 20:17:03 +01:00

still nothing, one major difference between us two is i'm still on 7, while your screenshot looks like win10

Gavin Scott commented

2019-02-25 20:29:46 +01:00

Yes Win 10 64-bit / Nvidia 1060 on a laptop here. I just tried it on a desktop Win 10 64 / Nvidia 1080 system with a 16:9 monitor and could not reproduce it there. It also reproduces on a two-month old build so it likely does not represent a recent change and thus probably not evidence of an issue that might cause other currently undiscovered serious issues.

Ray molenkamp commented

2019-02-25 20:35:46 +01:00

can you attach your system-info.txt ? (Help->Save System Info)

Gavin Scott commented

2019-02-25 21:01:54 +01:00

Here's mine system-info.txt

Here's mine [system-info.txt](https://archive.blender.org/developer/F6713783/system-info.txt)

Ray molenkamp commented

2019-02-25 21:06:03 +01:00

This issue reminds me a lot of #51521, and you do also seem to have a HD 630 based gpu in that system, can you validate that your intel drivers are up to date?

Gavin Scott commented

2019-02-25 21:27:06 +01:00

That certainly sounds plausible.

Unfortunately Acer have never released updated Intel drivers for this laptop since it was new, and I'm not willing to override the protection against installing non-vendor-approved video drivers at this point (too much risk in a hybrid graphics system), so I'm using the latest available supported drivers (which are sadly from 2017). I'll do some research and see if others have successfully been able to hack the driver instaal without problems.

Perhaps the original submitter can see if a driver update corrects their issue.

That certainly sounds plausible. Unfortunately Acer have never released updated Intel drivers for this laptop since it was new, and I'm not willing to override the protection against installing non-vendor-approved video drivers at this point (too much risk in a hybrid graphics system), so I'm using the latest available supported drivers (which are sadly from 2017). I'll do some research and see if others have successfully been able to hack the driver instaal without problems. Perhaps the original submitter can see if a driver update corrects their issue.

Sebastian Parborg commented

2019-02-26 14:24:44 +01:00

Just to clarify, we are waiting for @McLP to try with updated drivers.
If @McLP does not have a hybrid setup, let us know.

Just to clarify, we are waiting for @McLP to try with updated drivers. If @McLP does not have a hybrid setup, let us know.

Dont Want commented

2019-02-26 14:38:55 +01:00

I am currently updating my drivers, so I can tell you. I also created a system info if this helps. I am unsure what is meant by hybrid graphics.system-info.txt

I am currently updating my drivers, so I can tell you. I also created a system info if this helps. I am unsure what is meant by hybrid graphics.[system-info.txt](https://archive.blender.org/developer/F6717384/system-info.txt)

Dont Want commented

2019-02-26 14:40:17 +01:00

Problem persists with up-to-date Nvidia drivers.

Dont Want commented

2019-02-26 14:46:38 +01:00

In #61884#627467, @GavinScott wrote:
The issue is specifically spamming the F12 key rapidly 2-3 times. If you wait for the render to complete each time then the window updates without issue.

Can't confirm. Even happens if I wait to complete. But interestingly it did not happen on my laptop with single screen and only cpu rendering yesterday, but now it does. I also created a sysinfo. I believe this is an issue with windows 10 and has nothing to do with the graphics card or dirvers.system-info.txt

> In #61884#627467, @GavinScott wrote: > The issue is specifically spamming the F12 key rapidly 2-3 times. If you wait for the render to complete each time then the window updates without issue. Can't confirm. Even happens if I wait to complete. But interestingly it did not happen on my laptop with single screen and only cpu rendering yesterday, but now it does. I also created a sysinfo. I believe this is an issue with windows 10 and has nothing to do with the graphics card or dirvers.[system-info.txt](https://archive.blender.org/developer/F6717407/system-info.txt)

Sebastian Parborg changed title from ~~UI drawing offset randomly on Windows~~ to UI drawing offset randomly on Windows 10

2019-02-26 15:50:43 +01:00

Brecht Van Lommel commented

2019-04-01 14:38:33 +02:00

Closed as duplicate of #62497

Brecht Van Lommel closed this issue

2019-04-01 14:38:33 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

UI drawing offset randomly on Windows 10 #61884