By default you means it's unmodified keys come with Blender. No it doesn't work at all. I have tested it by remove addons folders and factory reset all preference. Default IC keymap by Default cannot switch to Draw mode by pressing 4 but can press 4 to toggle back to object mode. Blender Default keys tabbing will toggle to edit and draw mode however.
I am quite confused here.
Yes, but only Industry Compatible keymaps, since Blender default doesn't have hotkey binded as far as I know. Even vanilla IC keymaps are unable to switch to Draw mode by pressing 4. Since it's sharing a same keybind as object mode. If reassign Draw mode to keys like 9 for example, Object mode will be assign to 9 as well.
Does this happen with keymap without any modification?
Here's the demonstration of the issue. If you save the keymaps while in Draw mode. All other keymaps will mess up next blender starts.
Yeah, it's a slight modify of Industry compatible keys. But it behaves the same with Blender default too. With grease pencil selected. You wont able to switch or assign other modes with hotkeys. It gets replace to blank key maps. Selecting other polygon object restores it.
Even in industry compatible keymap, I can't reproduce this
@Richard Antalik (ISS) I think those shortcuts are from the Industry Compatible keymap.
Thanks @Evan Wilson (EAW) I had forgotten this task.
I am not sure what the problem is.
Mon, Jul 6
@Dalai Felinto (dfelinto) Unfortunately, this is still not solved in 2.31 LTS. I think it isn't just a papercut or nice to have. Wy shouldn't it work the same as in 3D mode? It worked before Grease Pencil was fully integrated into Blender. I mentioned in my previous post that it might have stopped working when Lock Object Modes was introduced. Even when it's unchecked it might not fully unlock for Grease Pencil. Maybe I'm wrong and the problem lies somewhere else but it feels like a bug that is somehow hard to spot. At the moment weight painting more complex characters is a tedious process, also a weight blurring brush would be a welcome addition.
I am sorry to put some more pressure on this but hope if not Philipp Oesser someone else will find time to pick up this task.
Anyway, thanks for all the great work already done.
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Sun, Jul 5
As well I am having this issue when I move the camera to a top down view. While drawing in the camera view all points of a stroke stick to the camera origin.
This is not a bug, it's a change in how works grease pencil. Your stroke is in frame 80 and is not visible before that frame. If you move the current frame to 80, you will see the strokes.
Sat, Jul 4
Fri, Jul 3
The slider are not visible for annotations and this datablock is set as annotation:
hey, there is one more problem while inserting texture(.png file) to the material for GP, the blending option does not work properly, it worked fine in 2.82 as it did not have the blending option. i saw a tutorial in which blending option was working fine, i guess he was using windows but in mac we have this issue.
hey, there is one more problem while inserting texture to the material for GP, the blending option does not work properly, it worked fine in 2.82 as it did not have the blending option. i saw a tutorial in which blending option was working fine, i guess he was using windows but in mac we have this issue.
I think i reproduced it once by using the symmetry modifier to create a drawing and then clock on apply for the modifier, but i couldn’t reproduce it another time, so maybe there is something else. I have some live recordings also but i don’t remember the occurence on the bug on it. Let me check again today, i will tell you if i find a recording.
Thanks for your help!
@Clément Foucault (fclem) Thanks! 🙂
I don't know where the points in the background came from because I did paint only in front view with Draw Plane set to Front (X-Z) so I for me this came out of nowhere. Maybe the issue occurs again and I remember my steps I've done – Then I could fire another bug report.
@Andry (dedouze) And: I remember you did a live stream some time ago, but I didn't watch it. Maybe you did some more and maybe the issue occurred in one of the streams? Then we could watch it and see what causes the issue.
Thu, Jul 2
The reason to had different code was the modifier was initially totally different and never was cleanup.
@Andry (dedouze) Did you find a way to reproduce it? have you found again the bug?
I wrote a patch.
Tested with commit 85980743b058e287f1d6400a64dcc60f87fad000
Date: Thu Jul 2 10:16:54 2020 -0600
Fixed, Thanks @Clément Foucault (fclem) for finding the root cause.
This is due to the bounding box of the GPencil object being incorrect for the buggy frames.
The call to BKE_object_boundbox_get inside gpencil_object_cache_add is returning a Unit boundbox incorrectly.
Wed, Jul 1
We have rewritten the whole GPencil engine for speed, ease of use and clarity. This was part of the changes. This change have some benefits (no Z-fighting in almost all cases and is cheap). If you want correct depth test use the 3D stroke depth type.