WIP: Fix #105578: Fix the tilt of the curve if realize instance makes it impossible to calculate the normal correctly #105634
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#105634
Loading…
Reference in New Issue
No description provided.
Delete Branch "mod_moder:fix_tilt_of_realized_curve"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If, when realize instances, the curve gets into a state where its normal cannot be calculated (the tangent is vertical), then can take into account the state of this normal in order to rotate the tilt of the curve.
WIP: Fix 105578: Fix the tilt of the curve if realize instance makes it impossible to calculate the normal correctlyto WIP: Fix #105578: Fix the tilt of the curve if realize instance makes it impossible to calculate the normal correctlyFine.
It seems to be easier to take and save the normals of the curve. Keep them separate when realizing. Apply a transformation matrix to them.
After that, take the new normals from the realized curve, based on the old normals and tangent, calculate the angle of rotation for each point on the curve, and add that to the tilt attribute.
I see this overhead for all other cases instead of reported one...
Seems like a workable approach to me.
So far the problem is:
I took a (somewhat) longer look at the code, and you're completely right: it is kinda complicated.
Maybe it's better after all to just document this as a 'known limitation' and better document that the curve normals are always parametric and calculated based on the evaluated curve? After all a workaround is quite straightforward using a 'capture attribute', which does more or less the same as the proposed fix but only when you need it.
The main problem is that it's rather confusing , so maybe better docs is the way to go?
If during implementation we could get the transformation matrix attribute, then yes, it would be very simple. For now, a little more movement is needed. But it's still possible.
Since this case is very unlikely, unless you try to achieve it on purpose, I think it's easier to expect the user to be able to bypass it himself if necessary.
Pull request closed