All mouse actions are one step behind. #42011

New Issue

Bastien Montagne · 2014-09-29T19:15:26+02:00

engineer42 commented

2014-09-29 19:15:26 +02:00

(Migrated from localhost:3001)

System Information
win7 64bit. nvidia GeForce GT 520MX

Blender Version
Broken: 2.71

Short description of error
All mouse actions(click, mouse over on menu, select anything) are one step behind.

Exact steps for others to reproduce the error
Bug was from first start of the program.

**System Information** win7 64bit. nvidia GeForce GT 520MX **Blender Version** Broken: 2.71 **Short description of error** All mouse actions(click, mouse over on menu, select anything) are one step behind. **Exact steps for others to reproduce the error** Bug was from first start of the program.

engineer42 commented

2014-09-29 19:15:26 +02:00

(Migrated from localhost:3001)

Changed status to: 'Open'

engineer42 commented

2014-09-29 19:15:26 +02:00

(Migrated from localhost:3001)

Added subscriber: @engineer42

Bastien Montagne commented

2014-09-29 21:12:25 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2014-09-29 21:12:25 +02:00

We need clear explanations of what "one step behind" means - is it just lag, or do you mean you have to always click twice to get things done, or… ?

Also, did you check this is not an issue with either your mouse or your system?

Did you try to start Blender with factory settings (--factory-startup option in commandline)?

We need clear explanations of what "one step behind" means - is it just lag, or do you mean you have to always click twice to get things done, or… ? Also, did you check this is not an issue with either your mouse or your system? Did you try to start Blender with factory settings (`--factory-startup` option in commandline)?

André Løfaldli commented

2014-09-30 15:37:06 +02:00

Added subscriber: @helt_vilt

André Løfaldli commented

2014-09-30 15:37:06 +02:00

I am also having this problem, so I will try to explain it more clearly.

The problem seems to be that the user interface is one step behind in drawing the window.

When I do some action, eg. "select all", nothing happens on screen until another key is pressed or I move the mouse out of the window.

This applies to any action in the 3D window as well as any text field (even the space bar-menu).

If I try to write something, this is what I see:

key - text field
h -
e - h
l - he
l - hel
o - hell

and then if I move the mouse or hit enter the o will be drawn.

EDIT:
I believe this guy is having the same problem.

I am also having this problem, so I will try to explain it more clearly. The problem seems to be that the user interface is one step behind in drawing the window. When I do some action, eg. "select all", nothing happens on screen until another key is pressed or I move the mouse out of the window. This applies to any action in the 3D window as well as any text field (even the space bar-menu). If I try to write something, this is what I see: `key - text field` `h - ` `e - h ` `l - he ` `l - hel ` `o - hell ` and then if I move the mouse or hit enter the `o` will be drawn. EDIT: I believe [this guy ](https://developer.blender.org/T41687) is having the same problem.

Bastien Montagne commented

2014-09-30 16:03:25 +02:00

Well, that guy never answered, so I’ll ask it again: can you please try those things? ;)

Play with OGL setting in UserPreferences, System tab (esp. Window draw method).
Start Blender with factory settings (from a commandline, use --factory-startup option).
You may also download this dll and put it next to blender.exe, and see whether this fixes the issue.

Well, that guy never answered, so I’ll ask it again: can you please try those things? ;) * Play with OGL setting in UserPreferences, System tab (esp. Window draw method). * Start Blender with factory settings (from a commandline, use `--factory-startup` option). * You may also download [this dll](http://download.blender.org/ftp/sergey/softwaregl/win64/opengl32.dll) and put it next to blender.exe, and see whether this fixes the issue.

Bastien Montagne commented

2014-09-30 16:04:17 +02:00

Oh, and please also check with a build from our buildbot, 2.71 is becoming old now ;)

Oh, and please also check with a build from [our buildbot](https://builder.blender.org/download), 2.71 is becoming old now ;)

Bastien Montagne commented

2014-09-30 16:05:02 +02:00

Added subscriber: @MartijnBerger

André Løfaldli commented

2014-09-30 16:48:28 +02:00

I tried all those things and none of them seem to fix the problem. (Honestly I see no difference when changing any of the options on the system tab.)

I also tried the v2.72 win64 build which appears to have the same problem.

Interestingly, enabling the "screencast keys" addon sort-of works. There is still a small delay, but not enough to be annoying.

I tried all those things and none of them seem to fix the problem. (Honestly I see no difference when changing any of the options on the system tab.) I also tried the v2.72 win64 build which appears to have the same problem. Interestingly, enabling the "screencast keys" addon sort-of works. There is still a small delay, but not enough to be annoying.

engineer42 commented

2014-09-30 19:00:50 +02:00

(Migrated from localhost:3001)

I also tried all those things and my problem is still there :(

Bastien Montagne commented

2014-10-07 08:33:22 +02:00

I’m short on ideas here… Martijn?

Sergey Sharybin commented

2014-10-14 10:57:30 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-10-14 10:57:30 +02:00

The issue reported can't be reproduced so far, and has been moved to the BF Blender: Unconfirmed project.
If 2 other people aren't able to redo the bug after 2 weeks, it will be closed.

We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them.
If there is anything you can provide to help others to reproduce the problem, be sure to include it.

The issue reported can't be reproduced so far, and has been moved to the *BF Blender: Unconfirmed* project. If 2 other people aren't able to redo the bug after 2 weeks, it will be closed. We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them. If there is anything you can provide to help others to reproduce the problem, be sure to include it.

Julian Eisel commented

2014-11-11 18:40:49 +01:00

Changed status from 'Open' to: 'Archived'

Julian Eisel closed this issue

2014-11-11 18:40:49 +01:00

Julian Eisel self-assigned this 2014-11-11 18:40:49 +01:00

Julian Eisel commented

2014-11-11 18:40:49 +01:00

No news for 4 weeks -> closed