- User Since
- Aug 21 2018, 8:46 AM (179 w, 3 d)
Mon, Jan 3
Dec 12 2021
Here is a video illustrating the issue in realtime. I left the TaskManager in frame in case it reveals something.
. I load a simple scene (GreasePencil in my case).
. I go back and forth in the Timeline. It's smooth.
. I switch to Render Viewport..
. Just before fiddling around in the Timeline again I opened the Preference Window and moved it around. Just to show that the whole Blender interface is still smooth.
. I then went back and forth in the Timeline. Slowdown appears. The playhead no longer sticks to the mouse/pen movement.
. Opening the Preference Window and moving it around shows stutter and no longer is smooth.
Could this be a memory leak of sorts? A driver issue? Or is it because these Intel cards don't have any VRAM and start using er, something else (I have 16G of Ram and a lot of disk space)?
Either way it'd be great to find a solution for this. Being able to work on the go (with the Surface Pro in my case) is pretty awesome...
Thanks for any helpful hints or insights!
Dec 1 2021
Is there no one seeing this?
Nov 30 2021
Nov 13 2021
Sep 7 2021
Hi! I don't think this is a Wacom related bug. I have been having the same problem with the latest 3.0 alphas on my Surface Pro 7 using Windows Ink.
Works as expected on previous Blender version (2.92 at least).
Aug 31 2021
I'm not seeing this fixed in the latest nightly, is that normal?
Aug 26 2021
Sorry again for asking, but is this going to get fixed at some point?
Aug 20 2021
Aug 7 2021
Jul 12 2021
Sorry for asking, but is this going to get fixed?
Jul 3 2021
Ok sorry for the multiple messages. Turns out I was wrong about 2.93 working! I thought I used Drivers on my scene but I wasn't...
So in short, in my experience, Drivers never worked with GP Local transforms.
I'm going to edit my first post to reflect that.
Sorry again for the confusion!
Hi again! It worked on 2.93 (probably alpha or beta, that's when GP Local Transforms first appeared). I did a job back in March and everything worked as expected. But when I load the scene today it no longer does (same Driver problem).
My Blender scene is dated from the 27th of March if that helps you find the 2.93 version of that time (I don't see alpha/beta builds on Blender's archive site).
I don't know where to look in Blender to see precisely what version was used for that scene.
Tell me if you need anything that can help you pinpoint the problem....
Jul 1 2021
Hello again. I don't know if this helps, but the above steps work as expected on regular objects. So this bug only affects Grease Pencil...
Jun 22 2021
Hi, this is still an issue. Any ideas on how to fix it? Or maybe a workaround? It's cool (and powerful!) to be able to use drivers with GP... Thanks!!!!
May 21 2021
May 20 2021
Mar 23 2021
Mar 22 2021
Mar 19 2021
@Falk David (filedescriptor) I did at some point yes. But removed it when trying to debug.
Feb 23 2021
Feb 18 2021
Sure! Here are two outputs from two machines (working and non-working). In case it's helpful...
@Ankit jain (Ankit) Meel (ankitm)
Nope sorry. The latest nightly gives me the same error (related to Python?). I have to disable the mac's SIP to access the addon...
Feb 16 2021
Ok I found a workaround. It's a Mac security issue.
When I disable the Mac's SIP (System Integrity Protection), I can load the Addon without any errors and everything works as expected.
I have no clue how to solve this at a Blender (Rigify?) level. Can anyone help? I'm not sure it's a good idea to lower the system's security to be able to run an addon...
Feb 15 2021
Feb 12 2021
Jan 28 2021
Aug 22 2020
Aug 21 2020
Here on WIN10 latest Blender nightly build, the gizmo works again (it didn't yesterday). You can transform when when you click on the red green blue helpers. But gimbal rotation is no longer recognized...
Aug 13 2020
The latest builds seem to have fixed the issue for me. Thanks!!
Aug 11 2020
May 27 2020
Oh yes it does!!
Sorry for the trouble and thanks for the answer!
May 20 2020
Ah ok sorry. I was confused by the fact that it worked in edit mode without issues.
May 19 2020
That was very fast! Thanks so much!!
May 18 2020
Mar 30 2020
Mar 19 2020
Hey! I found out what was causing the problem. I have an app called BetterTouchTool running and turning it off actually solves this problem.
Sorry about this. I'll warn the developer of the app.
And thanks again for everything :)
Mar 13 2020
Mar 2 2020
This crash seems to be gone with the latest nightles.
Feb 27 2020
Feb 24 2020
Oct 18 2019
Thanks so much for responding to this.
. Draw a ball with Grease pencil. Or anything basic.
. Create Mesh Plane.
. Create Particles on Plane. Choose Hair Emission.
. Choose Render Object. Pick Grease Pencil ball.
. Result: Viewport insanely slow, even when lowering number of particles.
Sep 5 2019
Aug 21 2019
This doesn't seem to work on curve points. Unless I'm mistaken of course!
. Add Circle (or any sort of curves), go in Edit Mode.
. Choose point, Insert Key.
. Change frame, move point, Insert Key: The point snaps back to where it was, resulting in no animation...
Am I the only one?
Oct 25 2018
I think it's the same problem as here: https://developer.blender.org/T56447
It's not that it's "not working" but it feels like there are clipping issues that disrupt the display.
Lowering the quality of the viewport makes it "work"...
Oct 19 2018
Aug 26 2018
Ok I found a solution.
It seems like the Viewport Quality Settings (in User Preferences/System) when set to anything else than 0, screws up the 3D Viewport.
In short, for anyone having the above problem on MacOs, put that setting on 0.
Aug 24 2018
Er, I'm not really used to these forums so sorry in advance for asking.
Is anyone taking care of this MacOs gfx problem? Or need more information?
Happy to help if I can...
Aug 21 2018
I did a second comparison ADM/Intel.
AMD: Graphic glitches galore, but fast interaction.
Intel: No glitches, but object manipulation feels really sluggish.
Is this what you're talking about?
(Watch until the end for my machines specs).
This seems only to happen with the AMD GPU (Radeon Pro 455 in my case).
As a test, I've forced MacOs to use the Intel HD Graphics 530 and it works as expected (although everything seems really slow).