Maniphest T39709

Navigation jitter when using middle mouse button - OSX
Closed, Duplicate

Assigned To
Campbell Barton (campbellbarton)
Authored By
Ethan Snell (Enthymeme)
Apr 13 2014, 10:57 PM
Tags
  • User Interface
  • BF Blender
  • Platform: macOS
Subscribers
Bastien Montagne (mont29)
Campbell Barton (campbellbarton)
Ethan Snell (Enthymeme)
jens verwiebe (jensverwiebe)

Description

System Information
OS: Apple OSX 10.9.2
Processor: 2.8 GHz Intel Core 17
Memory: 8 GB
Graphics: NVIDIA GeForce GT 330M

This is on a 17in Macbook pro.

Blender Version
Broken: 2.70a main release from blender.org
Worked: 2.69 main release

Short description of error

When using the middle mouse button in the viewport to navigate, a massive jitter occurs, disrupting navigation. This renders transformation almost impossible. This occurs when using the middle mouse button in any editor, such as 3D view, UV/image editor, and the graph editor. The jitter occurs at the refresh rate of the screen.

A short video that demonstrates the bug is available here:
https://www.youtube.com/watch?v=dxAZO2MEyBI&feature=youtu.be

Exact steps for others to reproduce the error
Occurs immediately after loading blender.

Event Timeline

Ethan Snell (Enthymeme) created this task.Apr 13 2014, 10:57 PM
Ethan Snell (Enthymeme) raised the priority of this task from to 90.
Ethan Snell (Enthymeme) updated the task description.
Ethan Snell (Enthymeme) added projects: BF Blender, User Interface, Platform: macOS.
Ethan Snell (Enthymeme) edited a custom field.
Ethan Snell (Enthymeme) added a subscriber: Ethan Snell (Enthymeme).
Bastien Montagne (mont29) added subscribers: jens verwiebe (jensverwiebe), Bastien Montagne (mont29).Apr 13 2014, 11:07 PM

This sounds awfully similar to T39504

Jens, thoughts?

Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.Apr 13 2014, 11:07 PM
jens verwiebe (jensverwiebe) added a comment.EditedApr 14 2014, 10:31 AM

Hi
Watched the example video and must say i have no clue whats causing this atm..
T39505 was more the changed nicing prio issue afaik.

This one looks much uglier.

It looks we may have a problem limited to certain machines here and i saw something
like this in the intet, where Adobe claims they identified a bug with newest Apple build
env causing wrong instructions. The root problem is new stricter clang bringing up
a longstanding system lib issue more prominent.

Thats all speculative but i have a testbuild done with former 2.69 build env ( gcc-4.8.1 )
that could give us insight if we are affected here.
So please test this 2.70a done with alternative compiler pls.: http://www.jensverwiebe.de/Blender/blender_2.70a_gcc_physical_threads.zip

Don't worry about the odd name of the zip, it was intentionally made to check another issue.

Enthymeme, would be nice if you report back soon ....

Jens

Bastien Montagne (mont29) triaged this task as 30 priority.Apr 14 2014, 10:33 AM
Ethan Snell (Enthymeme) added a comment.EditedApr 14 2014, 12:43 PM

Hey Jens,

Downloaded the version you provided, and the bug seems to be re-occurring in that build. The jitter is just as bad.

Also, quick note: I realize that the video I uploaded doesn't really give an accurate depiction of the jitter, since that video is at 30FPS. The jitter is actually occurring at the rate of my screen refresh, which is 60hz (I think!). I can record a higher frame-rate video if you would like.

Let me know if there's anything else you need... if it only affects certain machines, that definitely makes fixing it difficult for you.

~Enthymeme

jens verwiebe (jensverwiebe) added a comment.Apr 14 2014, 1:10 PM

Hi Enthymeme

Thats in a way good news, cause i feared there would be something fishy in my actual build environment.
There is a lot of information around regarding compiler/OS issues, which leaded me to check this assumption
first.

The bad is we must still find out the root reason for your jitter.
Next area to check is the drawing now, pwerhaps something affected by bad video drivers.
I dunno how much technical background you have. It would be interesting if you have the same problem
on another OSX version or on same OSX when switching to software rendering or disable native-pixels etc..

Tell me if you can check:

  • starting blender from terminal with the --no-native-pixels option
  • try set other screen refreshrate ( if possible )
  • try setting other buffer types in prefs ( full, triple, etc. .. )

A bit hazzle i know, but don't have comparable machine to test here.

Jens

Ethan Snell (Enthymeme) added a comment.Apr 14 2014, 2:00 PM

haha, not much luck here I'm afraid.

  • Starting blender from terminal:

I used:

open /Applications/Blender/bugtest.app/Contents/MacOS/blender --no-native-pixels

bugtest.app being the blender version you attached above, renamed and put in my applications folder.

I got this error: http://i.imgur.com/C2zWLie.png
Not sure of the protocols for starting blender from terminal... any tips?

  • try set other screen refreshrate ( if possible )

Unfortunately not possible. I have a macbook pro, and you can't change the refresh rate of the screen for the monitor. I might be able to try plugging into another monitor if that might help.

  • try setting other buffer types in prefs ( full, triple, etc. .. )

Done, but to no avail. It was set to automatic by default, and changing it to full, triple buffer, overlap, or any of the others did nothing to change the problem.

jens verwiebe (jensverwiebe) added a comment.EditedApr 14 2014, 2:07 PM

Damn :)

.... lemme think ....

And start Blender from terminal without leading "open" just.
Aka: /Applications/Blender/blender.app/Contents/MacOS/blender --no-native-pixels
Other way could be open Blender finder Info and uncheck "start in low res" or how thats called in engl. .

Jens

Ethan Snell (Enthymeme) added a comment.Apr 14 2014, 2:30 PM

Ok. So, no luck on the --no-native-pixels. Didn't change anything, the bug persisted.

I don't have a retina display, if that helps at all.

However, Mont29's comment above led me to: https://developer.blender.org/T39094, which seems to be the same issue. The reporter of that bug noted that it is related to the continuous grab checkbox. I can confirm that: When continuous grab is checked, the jittering happens. When it is unchecked, the jitter does not happen.

Additionally, when checking continuous grab in blender 2.69, the jittering happens there as well. Nothing is sacred. ;P

Even more testing led me to discover that it's not just the middle mouse button. It happens when I press [G] to move an object... the transformation starts jittering.

That made me wonder if it happened with any mouse movement at all. I then checked the sliders on the menu, in the render settings. They were not effected by the jitter.

But when I opened up the graph editor and tried to transform a point on an animation curve, it started jittering there as well.

So there's some more info! Does that help?

jens verwiebe (jensverwiebe) added a comment.Apr 14 2014, 2:53 PM

Aaaaah .... the continous grab was a hazzle for some since ever.
We once fixed it for AMD gpu, but i don't remeber exact where the problem has it's root.
Okay, not a biggie then, will invesigate further.

My hint in between: you must guess ;P

Jens

Ethan Snell (Enthymeme) added a comment.Apr 14 2014, 3:02 PM

I see. That's unfortunate!

Can I propose, in the meantime, that Continuos Grab shouldn't be turned on by default? Obviously a bit of a pain, if the user doesn't know what's going on. I imagine new users would be turned off entirely... I've been using blender for 7 years and I was pretty frustrated, haha.

Thanks for your help with the issue!

jens verwiebe (jensverwiebe) assigned this task to Campbell Barton (campbellbarton).Apr 14 2014, 3:30 PM

Oh, indeed. Wasn't aware it is now default on. I never used it :)

Afaik this was an ideasmen project, assigning to him now :)

Jens

Bastien Montagne (mont29) raised the priority of this task from 30 to Normal.Apr 21 2014, 12:59 PM
Bastien Montagne (mont29) changed the task status from Unknown Status to Duplicate.Apr 21 2014, 6:13 PM

✘ Merged into T39094.