Bone custom curve shape makes it invisible #92120

New Issue

Roman · 2021-10-11T19:13:49+02:00

Roman commented

2021-10-11 19:13:49 +02:00

System Information
Operating system: linux
Graphics card: amd

Blender Version
Broken: blender-3.0.0-alpha+master.79425ed32676
Worked: 3.0.0 Alpha, branch: master, commit date: 2021-08-28 20:38, hash: 4256eeeec4

Caused by b9febb54a4

Short description of error
Bone custom curve shape makes it invisible.

Exact steps for others to reproduce the error
Open attached file curve-bone-bug.blend
Make sure bone is selected.
In the Viewport Display panel, click Custom Object, and pick Bezier Curve

Result: bone invisible.
Expected: bone takes shape of the curve

There was some shenanigans with curves previously, may be related: https://developer.blender.org/T85423

**System Information** Operating system: linux Graphics card: amd **Blender Version** Broken: blender-3.0.0-alpha+master.79425ed32676 Worked: 3.0.0 Alpha, branch: master, commit date: 2021-08-28 20:38, hash: 4256eeeec4ca Caused by b9febb54a4 **Short description of error** Bone custom curve shape makes it invisible. **Exact steps for others to reproduce the error** Open attached file [curve-bone-bug.blend](https://archive.blender.org/developer/F10975219/curve-bone-bug.blend) Make sure bone is selected. In the Viewport Display panel, click Custom Object, and pick Bezier Curve ![Screenshot_20211011_200231.jpg](https://archive.blender.org/developer/F10975246/Screenshot_20211011_200231.jpg) Result: bone invisible. Expected: bone takes shape of the curve There was some shenanigans with curves previously, may be related: https://developer.blender.org/T85423

Roman commented

2021-10-11 19:13:49 +02:00

Added subscriber: @rwman

Pratik Borhade commented

2021-10-12 09:06:50 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-10-12 09:18:05 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2021-10-12 09:18:05 +02:00

Thanks for the report. I can reproduce this on master.
Introduced between eab26f1334 - 15405685d9 (Will find the exact commit)

Most probably culprit commit would be b9febb54a4

Thanks for the report. I can reproduce this on master. Introduced between `eab26f1334` - `15405685d9` (Will find the exact commit) Most probably culprit commit would be b9febb54a4

Philipp Oeser commented

2021-10-15 13:59:25 +02:00

Added subscribers: @HooglyBoogly, @lichtwerk

Philipp Oeser commented

2021-10-15 13:59:25 +02:00

Think this is used in rigs quite often? (will dare setting this to High priority).
And yes, this is indeed caused by b9febb54a4.

CC @HooglyBoogly

Think this is used in rigs quite often? (will dare setting this to High priority). And yes, this is indeed caused by b9febb54a4. CC @HooglyBoogly

Hans Goudey self-assigned this 2021-10-15 16:21:01 +02:00

Hans Goudey commented

2021-10-16 01:27:06 +02:00

This is looking like a really unfortunate situation honestly. The situation that causes the problem is described in a comment:

 * \note Curve and text objects evaluate to the evaluated geometry set's mesh component if
 * they have a surface, so curve objects themselves do not have a surface (the mesh component
 * is presented to render engines as a separate object).

That works fine when the render engine is looping through all evaluated objects, but the overlay that draws this only uses a single object.
So this is a very ugly case where we have to teach Blender that an object can evaluate to multiple data types that are separate objects.

What I'm currently wondering is how does pchan->custom end up pointing to the evaluated object intsead of the original object?
Presumably, that same place could be used to make it point to multiple evaluated objects instead.

This is looking like a really unfortunate situation honestly. The situation that causes the problem is described in a comment: ``` * \note Curve and text objects evaluate to the evaluated geometry set's mesh component if * they have a surface, so curve objects themselves do not have a surface (the mesh component * is presented to render engines as a separate object). ``` That works fine when the render engine is looping through all evaluated objects, but the overlay that draws this only uses a single object. So this is a very ugly case where we have to teach Blender that an object can evaluate to multiple data types that are separate objects. What I'm currently wondering is how does `pchan->custom` end up pointing to the evaluated object intsead of the original object? *Presumably*, that same place could be used to make it point to *multiple* evaluated objects instead.

Martin Capitanio commented

2021-11-22 18:46:47 +01:00

Added subscriber: @capnm