Strange blender user interface bug where UI lags behind user input. #46190

New Issue

kjelbyts · 2015-09-21T06:30:57+02:00

kjelbyts commented

2015-09-21 06:30:57 +02:00

System Information
Windows 7 64-bit
Acer Aspire 5750G (i5-2450M - Intel HD Graphics 3000, NVIDIA GT 630M)

Blender Version
Blender 2.75
Although this bug is present in most (if not all) blender versions after 2.5. Unsure if it is present on blender versions before 2.5.

This is a bug in the updating of the user interface. When doing something in the viewport like selecting a vertex. The vertex will not be highlighted until another action is performed. Another example is when you press file on the info view. The file menu will not appear until you move the mouse cursor. It looks like the user interface is lagging behind by 1 step. Selecting different window draw methods in Preferences -> System does not help solve the problem. Please view attached video:
https://www.youtube.com/watch?v=zA4dkWD_Pnk

Not sure how widespread this bug is. But if you have a laptop with windows vista or windows 7 (perhaps even window 8 and windows 10). With optimus technology with an NVIDIA card. The bug will occur if you disable windows AERO. This means you cannot use the Basic or Classic themes. This is also means that for users experiencing this bug, enabling AERO will circumvent the UI bug.

It is important for laptop users to be able to use blender with AERO disabled since AERO uses resources that could be allocated to blender. Having AERO disabled also allows other programs to interact with Blender properly. For instance screencasting with OBS.

**System Information** Windows 7 64-bit Acer Aspire 5750G (i5-2450M - Intel HD Graphics 3000, NVIDIA GT 630M) **Blender Version** Blender 2.75 Although this bug is present in most (if not all) blender versions after 2.5. Unsure if it is present on blender versions before 2.5. This is a bug in the updating of the user interface. When doing something in the viewport like selecting a vertex. The vertex will not be highlighted until another action is performed. Another example is when you press file on the info view. The file menu will not appear until you move the mouse cursor. It looks like the user interface is lagging behind by 1 step. Selecting different window draw methods in Preferences -> System does not help solve the problem. Please view attached video: https://www.youtube.com/watch?v=zA4dkWD_Pnk Not sure how widespread this bug is. But if you have a laptop with windows vista or windows 7 (perhaps even window 8 and windows 10). With optimus technology with an NVIDIA card. The bug will occur if you disable windows AERO. This means you cannot use the Basic or Classic themes. This is also means that for users experiencing this bug, enabling AERO will circumvent the UI bug. It is important for laptop users to be able to use blender with AERO disabled since AERO uses resources that could be allocated to blender. Having AERO disabled also allows other programs to interact with Blender properly. For instance screencasting with OBS.

kjelbyts commented

2015-09-21 06:30:57 +02:00

Changed status to: 'Open'

kjelbyts commented

2015-09-21 06:30:57 +02:00

Added subscriber: @kjelbyts

kjelbyts commented

2015-09-21 06:35:20 +02:00

Here are previous reports on the same bug, but they didn't seem to go anywhere:

https://developer.blender.org/T41687

https://developer.blender.org/T42011

It seems to be the disabling and enabling of Aero that triggers the bug.

Here are previous reports on the same bug, but they didn't seem to go anywhere: https://developer.blender.org/T41687 https://developer.blender.org/T42011 It seems to be the disabling and enabling of Aero that triggers the bug.

Campbell Barton commented

2015-09-21 07:09:25 +02:00

Closed as duplicate of #41687

Campbell Barton closed this issue

2015-09-21 07:09:25 +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

Strange blender user interface bug where UI lags behind user input. #46190