- User Since
- Mar 12 2019, 8:06 AM (39 w, 1 d)
Sat, Dec 7
Yup, with 2.82 alpha 7 Dec build everything works fine.
Thu, Dec 5
You might try again with a newer build.
Ok, will try.
If works, then I will close this :)
Mon, Dec 2
Seems to be connected with T71147 , which is resolved now.
Tested in 2.82 alpha -- bug is gone :)
Sun, Dec 1
Tried new 2.82 alpha 1 December.
Bug IS GONE.
Fri, Nov 29
3 users on same OS (Mac OS Catalina 10.15) have confirmed that issue.
Tue, Nov 26
Sorry, didn't know that.
Any suggestions what I can do with my OS except clean install?
Would NOT put it in archive though...
Downloaded and tested with Blender 2.79 — same bug as with 2.80 and 2.81...
This IS strange, because on 2.79 I didn't encountered it before I tried 2.80 beta...
I will download blender 2.79 to test it again...
do you have maybe some strict permissions?
I didn't modified Mac OS files, System Integrity Protection is enabled (never was disabled).
I have Gatekeeper disabled though, but that couldn't be a problem...
but until we can reproduce this on our side, there is not much we can do.
(Obviously) I will wait as much as needed. If you need some info (with steps how to gather it) I can give it :)
Sebastian Parborg (zeddb) reopened this task as Open.
Phew, thanks. Closed new duplicate :)
And nope — it STILL present.
I am encountering this bug almost every time I open .blend file...
Why closing this task before I've checked it? I could do that (closing issue) myself then if everything fine...
Also, I added in info version that I've tested with video: 2.81 beta 2019-11-11
Wed, Nov 20
Yes, I understand now and it's working properly!
Tue, Nov 19
Works well (no bug) on 2.80 release. So it's not my drivers or OS :)
Also, may be connected with bug T71500
Maybe you can add(assign) someone, who use Mac OS Catalina to test?
Would be much grateful :)
On macOS graphics drivers are built into the operating system and the only way to get newer drivers is to upgrade macOS as a whole to the latest version.
Tue, Nov 12
This bug not always happens -- so to trigger it -- try selecting bones, then some mesh, then empty viewport, then again bones etc., constantly switch between solid and wireframe mode with shortcut shift + z.
Mon, Nov 11
Oh, yep, sorry
Seems to be problem with node wrangler -- if I change shortcut to something like "Ctrl + Alt + X" -- then everything works.
Or if I turn off "node wrangler" add-on -- everything works too.
Sorry, false alarm then...
Remap "toggle maximise area" in settings to "Alt + Up (or Down) arrow"
This is because Mac OS doesn't support maximizing area with default "Ctrl + spacebar" or "Ctrl + Alt + spacebar" (it's switching languages. You probably should fix that too! Not everyone is using standard keyboard with Windows or Linux :)
If problem not reproduces -- try clicking on empty viewport (just outside objects) while pressing "tab" and/or clicking on objects
Jul 21 2019
Agreed -- I had the same problem
Jul 16 2019
Well, this bug happens 1 out of 10 times, but it's really unpredictable and hard to catch...
You may open 20 .blend files fine, and then open other .blend file and this happens....
Jul 15 2019
Strangely, I cannot reproduce it either (with July 2 build or recent RC1)
I didn't make it up (I have no reason to do so :)
But it is strange...
I can record video tomorrow (today I can’t) to show exactly what i mean
I mean opening .blend file from finder.
No, it’s not that
What i mean that it doesn’t open blender file. It starts blender with default scene, but not opening file.
If blender is already launched — yes, it loads file. But if blender is quit, and then you tries to open blender file from finder — it just launches blender with default scene
Jul 12 2019
But the pivot point "IS" actually in the center of scene for armature and mesh!
So the pivot and 3d cursor are at the center of scene -- then why it mirrors through local x axis?