Another reason to wait to replace this feature with a built-in node group that could use curves. The mirror modifier would also be replaced by a group that would definitely not create a mesh XD
Seems to be a duplicate from blender/blender#106982. But it's better to wait for a fix to be sure.
Hi @JacquesLucke, seems there is some bug in indexing graph output usage data? This is the modifier node group + nested node group.
Something very old, in debugging you can make an example file from just 2 nodes. I'll try to find the reason.
Should blender use -Y direction to render and stick to that in the gizmo? Are there other places in blender where Y is in front?
Why is that wrong?))) Give examples from other parts of the blender if this is inconsistent behavior. If it's just your desire, then yes, it's just a feature request
I'd close this as a feature request since you're just saying it shouldn't work that way. But you did not give any examples, without the need to explore by myself, I could't consider this to be…
Hi thanks for the reply, I can't reproduce this in 3.5.1 and 3.6. I can always see the eyebrows in the render. Maybe the problem is related to denoise? Or is it already fixed?
I can confirm that real-time compositor gives a result that doesn't look right here. And also, the final composer is completely serviceable.
This hasn't changed since 3.1, it's not mentioned in the documentation. Maybe it was a way to get around the dependence on the evaluated version of the curve, to rely only on the control points.…
Hey, you can't use various old data because the geometry nodes turn it all into attributes that modifiers don't see. If this is your issue, then I'll close it as expected behavior.
@lichtwerk I imported the example cube with the old and new importers. Saved this in release 3.6. Opened this in debug 3.6, repository state 1-2 hours ago. And I get a crash when I try to U-unwrap…
@lichtwerk True, yes, there is no crash in the release. Seems like unsafe behavior since debugging crashes Now I building today's debugging. Also, to make sure, is it a legacy import or a new one?
This is caused by the use of the GPU. This is an old bug, was in 3.1. So no regression. Maybe there is a duplicate.
Can't test as I just crash off while deliting all the hair.
Hi, thanks for the report, but without the sample file, it's impossible to test. Can you give some steps to play this from an empty file, or a ready file?
@lichtwerk i added my stack trace from 3.6 debug build (13.04)