You can actually just make a cube and move it in edit mode, or move the origin, and any face facing positive direction will be marked non-planar.

Also in this video in this tweet, I have a single face, duplicated, moved and scaled multiple times, and only the middle one is marked planar. This makes no sense in any scenario involving a threshold. https://twitter.com/floatharr/status/1534823120032374784

Confirmed with the included blend file: the issue shows up in Cycles but not EEVEE. The exact resolution above which lineart fails to show up is 2048x2048

I can't reproduce either in 2.93 stable or the latest 3.0 alpha by following the steps or using the attached file. I also tested the file with 2.91.2 which I still had installed, and I can crash it reliably. Feels like this one is fixed.

Nuking my drivers would be counterproductive to resolving the bug, no way to know what caused it if it works. Everything else is working flawlessly, and I don't work with fluid sims regularly so I prefer to be able to reproduce the bug.

I have managed to get the file I was tinkering with to a state where it renders consistently but with incorrect/broken motion blur. With 64 render samples, 499 px max blur, and 63 steps I believe this frame should have smooth motion blur on it. Maybe this'll help with debugging.

Since others have failed to reproduce, I felt like it's best I do some investigation on my own. Hopefully this helps to narrow it down.

I can still reproduce the crash with latest drivers (version 467.09) in 2.92 alpha and 2.91 beta with both the included file and following steps in the video.

I am using Driver version 452.06 which as of August 17th is the latest version available. There is no newer driver to update to.

Here are the files generated on the latest 2.91 development build

Alright, I see. So if I want to use it to add detail on the surface of a 3D object I should have each face with its own grease pencil object so all the strokes lie on a flat plane. Really felt like it was bugged because I expected the grease pencil strokes to be lit like any other piece of geometry. Maybe one day we can have that. Sorry for taking your time. Thank you.

The walk/fly navigation also likes to drift and jump around at high mouse polling rates, so I would assume this is a broader issue with how mouse input is handled in blender. I've recorded a video comparison of 125hz vs 1000hz:

Please follow the steps exactly as listed, and shown in the video. The cloth brush has a deformation mode called "Grab".

I think my issue is related to this. I've been getting these zero area faces stitched to the wrong side of the bevel in my UVs after applying a bevel modifier, so far the only way to fix it is to apply bevels before UVing or stitch all the faces manually which takes time. It would be amazing to see some progress on this. This bug is making it difficult to work with nondestructive bevels in game assets.

Forgot to search before reporting, this has been reported already here https://developer.blender.org/T69000

I've used emulate mmb since the start maybe a decade ago, because I built up muscle memory for alt-orbiting and panning with a pen tablet from other software. For multiple reasons I would highly prefer to not have to readjust.

I managed to reproduce this (or possibly a related bug...) having the pen within the proximity of the tablet (but not necessarily in contact with it), alt-tabbing away, lifting the pen and putting it aside, and then alt-tabbing back to blender and trying to sculpt with my mouse. Mouse sculpting and texture painting is broken until I bring my pen close to the tablet, no actual contact necessary at any point.

Couldn't reproduce the crash on Nvidia/Windows 10 with the latest alpha build.