Set Curve Radius is Effecting Bounding Box of Curves #103387

New Issue

Gerstmann Bradley · 2022-12-21T21:44:07+01:00

Gerstmann Bradley commented

2022-12-21 21:44:07 +01:00

System Information
Operating system: Windows-10-10.0.17134-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11

Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-12-21 15:03, hash: 51e2ce7df5
Worked: 3.4 and before

Behaviour changed in e8f4010611

Short description of error

I assume it's taking "Curve Points" into account, but here I am evaluating Curves not Curves Points. This behavior is not seen before 3.5. Is this a bug or a change implemented?
I don't think it's expected to evaluate Curve Points when I am inputting Curves and trying to get Curve's bounding box.

**System Information** Operating system: Windows-10-10.0.17134-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11 **Blender Version** Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-12-21 15:03, hash: `51e2ce7df5` Worked: 3.4 and before Behaviour changed in e8f4010611 **Short description of error** ![image.png](https://archive.blender.org/developer/F14081149/image.png) I assume it's taking "Curve Points" into account, but here I am evaluating Curves not Curves Points. This behavior is not seen before 3.5. Is this a bug or a change implemented? I don't think it's expected to evaluate Curve Points when I am inputting Curves and trying to get Curve's bounding box.

Gerstmann Bradley commented

2022-12-21 21:44:07 +01:00

Added subscriber: @Bradley_G

blender-admin commented

2022-12-21 21:44:07 +01:00

blender/blender-addons#103974 was marked as duplicate of this issue

blender-admin commented

2022-12-21 21:44:07 +01:00

#103566 was marked as duplicate of this issue

Richard Antalik commented

2022-12-21 22:15:10 +01:00

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

Philipp Oeser commented

2023-01-02 11:05:49 +01:00

Added subscribers: @HooglyBoogly, @lichtwerk

Philipp Oeser commented

2023-01-02 11:05:49 +01:00

Changed status from 'Confirmed' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2023-01-02 11:05:49 +01:00

Behaviour changed in e8f4010611

But doesnt it make sense to have the bounding box change on curve radius changes?

CC @HooglyBoogly , opinions?

Behaviour changed in e8f4010611 But doesnt it make sense to have the bounding box change on curve radius changes? CC @HooglyBoogly , opinions?

Iliya Katushenock commented

2023-01-02 12:21:51 +01:00

Added subscribers: @baoyu, @PratikPB2123, @mod_moder

Iliya Katushenock commented

2023-01-02 12:22:06 +01:00

Found 10 days earlier than duplicate

Philipp Oeser commented

2023-01-02 12:57:12 +01:00

Thx finding the duplicate @mod_moder !

Lets keep it on High prio then to get an answer quick.

Thx finding the duplicate @mod_moder ! Lets keep it on High prio then to get an answer quick.

Hans Goudey commented

2023-01-09 16:43:40 +01:00

I'm not sure what to do here unfortunately. The problem is sort of because of the curves/legacy curves problem, since the new curves are at least intended to be drawn with the radius so the bounds make sense. Since the old curves are just drawn as wires, it doesn't really make sense in cases like this. But I'm not sure if we can vary the behavior depending on the object type.

I wish the bounds could be computed more simply (without evaluating the curves and without including the radius) since that would be much faster, but I think the bounds are used to determine viewport culling so I'm not sure that's possible.

I'm not sure what to do here unfortunately. The problem is sort of because of the curves/legacy curves problem, since the new curves are at least intended to be drawn with the radius so the bounds make sense. Since the old curves are just drawn as wires, it doesn't really make sense in cases like this. But I'm not sure if we can vary the behavior depending on the object type. I wish the bounds could be computed more simply (without evaluating the curves and without including the radius) since that would be *much* faster, but I think the bounds are used to determine viewport culling so I'm not sure that's possible.

Germano Cavalcante commented

2023-01-09 19:39:13 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2023-01-09 19:39:13 +01:00

I feel like the draw culling can actually be impaired if the bounds are not calculated based on what is seen.
For new curves it makes sense to use the radius, as the user can see this radius in action,
but for the old ones, this radius is not visible and the bounds is misleading.

I feel like the draw culling can actually be impaired if the bounds are not calculated based on what is seen. For new curves it makes sense to use the radius, as the user can see this radius in action, but for the old ones, this radius is not visible and the bounds is misleading.

Hans Goudey commented

2023-01-10 18:00:12 +01:00

We talked about this briefly in the geometry nodes module meeting. The best idea we had was adding an option like "Use Radius" to the node so users could have control of this behavior.

Hans Goudey commented

2023-01-18 17:39:10 +01:00

Added subscriber: @purplemeanie

John Martin commented

2023-01-18 17:56:02 +01:00

@HooglyBoogly, thanks for sorting out my duplicate. Apologies, I looked but didn't spot this original task.

Hans Goudey commented

2023-01-18 18:05:39 +01:00

No worries, thanks for the report!

Jhon Rincón commented

2023-02-06 16:46:35 +01:00

Added subscriber: @renderart

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Set Curve Radius is Effecting Bounding Box of Curves #103387