@ideasman42: I just tested this again in Blender 4.0.2, Blender 4.1.0 beta (2024.02.24), and Blender 4.2.0 alpha (2024.02.24), and this issue still breaks Blender UI. (tested on linux builds)
T…
let me know if I need to take a look at it. thanks for your work, @mano-wii
will take a look as soon as I can (later tonight?).
in general, the snapping steps is useful for breaking a large transformation into smaller ones, with snapping happening after each small…
This PR is applied to Blender 4.0. Is there any way to get these changes into 3.6? even if 3.6.1?
Thanks for the review+feedback @dr.sybren and @ideasman42!
added checks for negative values and for too positive (>1) values.
Values over 1 don't make sense either. Should we test against these? Do these tests need to be reported in the docstring?
Removed as a tuple and made some additional adjustment to docstring.
Attached is a better version of testing code. Rather than rendering two triangles with coincident points, here it renders two coplanar triangles. The Z-fighting is very evident and an effect…
I was following example of scissor_get. Should docs for both remove the as a tuple?
Ah, I was following the example of doc for fragment_source, which I notice know also has the…
First, I noticed and fixed a bug in the depth_range_set function. This change is in commit 4e6fcb4349.
Attached is a Python script to demo the depth_range_set and write_depth functions. …
A note: as of Blender 3.6.0, there is no way to create a shader in Python that updates the depth in fragment shader. This commit exposes that ability.
I followed the instructions on https://wiki.blender.org/wiki/Tools/Pull_Requests as best I could. Please let me know if this PR needs to be updated before reviewing.