-
Blender Bug Triaging Lead and Developer (as in : supporting modules with bugfixes), LTS releases Prior to that, mainly doing R&D at studios in Germany and the UK.
- Joined on
2008-09-14 -
-
There was a time when invalid material index attributes could be written by several operations (see #103198, #99015, a2d59b2dac, 1a6d0ec71c)
And I do see these invalid material indices in this…
on my way out, @HooglyBoogly , @Baardaap : mind having a look?
I still don’t fully understand why you need to take into account local offset if there are no parents
Frame nodes themselves have offsets (even if they dont have parents), they get that in…
Any updates/info on this @JosephEagar ?
From the commit message:
These types of operators are not supposed to be undoable in the first place.
Well, at least you need to be able to redo…
Thanks! I think this is fine for 3.5 by the way, this sort of update tag should not be risky at all.
lets not put more things on @ThomasDinges table to go through today... it is not critical,…
Snap curves to surface operator does not update geometry for geometry nodes
Seems like just tag_positions_changed is missing.
Will post a PR
Should I bother with a PR for the release branch?
go for it (if it is considered low enough prio for 3.5, the PR can still be changed to go into main instead)
CC @SimonThommes (maybe you could check if this is working as intended for you)
@mod_moder : will self-assign if you dont mind (since this is caused by my commit), thx looking into it anyways!
