I am Nick i have a youtube channel at Youtube.com/TinyMediaTV
- User Since
- Feb 27 2021, 7:54 PM (91 w, 2 d)
Mon, Nov 21
Yeah it has been a pain to deal with! Took me a while to track down the actual bug, thank you for confirming.
Sun, Nov 20
Oct 13 2022
Oct 5 2022
Aug 25 2022
I did mean sceeen space, when i go to screen space mode theres the thickness still just reports as a value not a pixel value.
Aug 23 2022
Jul 7 2022
May 20 2022
May 12 2022
I tested this, seems to be working. Scale and offset work as expected as well.
Apr 4 2022
Mar 26 2022
Mar 25 2022
Mar 7 2022
According to my testing, this patch also resolves this issue https://developer.blender.org/T95735
Feb 19 2022
I think it should be left as is, lots of users subdivide meshes, maybe just document the importance of this option if its not already in the manual would be the only course of action i see.
Feb 17 2022
@Bastien Montagne (mont29) Thank you, that does appear to work as a temporary workaround. I appreciate the tip it seems to have worked! The playback speed is reasonable using the workaround.
Feb 14 2022
I have also tested this in the production file where I found the original error and it has fixed the line art in that scene as well thank you.
Thank you, just some additional context: lattices are often used when rigging grease pencil characters, smaller grease pencil objects dont seem to produce this error (needs testing). I only discovered this because the addition of a new more detailed character unexpectedly tanked my performance.
Feb 13 2022
Feb 12 2022
Feb 11 2022
Dec 14 2021
All good no worries! Checkout this https://wiki.blender.org/wiki/Process/Bug_Reports before submitting your next bug report.
Looks like there is a broken dependency on that blend file in particular. If you look under the Blend File data it is linked to another blend file. Im not sure what occurred here as the attached file doesn't match your screenshots either.
Dec 9 2021
There are some changes to how Geo Nodes work between 2.93 and 3.0. This is a matter of using an 2.93 Node tree in 3.0. The Collection Info Node has changed. When I opened your file I got a warning that said "Collection Contains Current Object". Here is a copy of the same blend file but with a new collection that seems to solve the issue.
Just another user here testing this error.
Ok we do use LTS for all our productions right now so it would be nice to have it fixed there and not be on the latest release.
Dec 8 2021
Jul 21 2021
I have just gone through and re-tested all my Pop OS Machines and I was unable to reproduce the bug so lets just mark this as archived. My apologizes. I will reopen if I figure out what I was experiencing.
Jul 20 2021
Blend File for refrence
Feb 27 2021
I have also encountered this as an unexpected result, but I was able to find a work around converting the string to a float. I conquer that it is not a bug but maybe this would be appropriate as a feature request instead? @Brecht Van Lommel (brecht) I made a post about my findings and work around here https://blenderartists.org/t/how-to-focus-on-an-integer-in-an-operator-in-an-addon/1287896/2 but this really only seems to be an issue for beginner programmers, because it seems that if you have a robust understanding of python its a pretty simple solution.