Cleanup: Sculpt, use C++ types for PBVH proxy node API #114638
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#114638
Loading…
Reference in New Issue
No description provided.
Delete Branch "Sergey/blender:sculpt_pbvh_cpp_proxy"
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?
Unfortunately, there seems to be some artifacts caused by this change. It is a bit hard to reproduce. But is just some quick strokes with a Draw brush.
Investigating it, but if someone sees an obvious issue please let me know :)
Sorry for the spam. Appears the issue is coming from another refactor in the area.
Nice! This sort of things makes things easier and safer to refactor more later. Locally the change is for the better, though obviously they're still within this slightly strange context.
@ -3076,0 +3071,4 @@
/* It is fine to access pointer of the back element, since node is never handled from multiple
* threads, and the brush handler only requests a single proxy from the node, and never holds
* pointers to multiple proxies. */
PBVHProxyNode &proxy_node = *(node.proxies.data() + node.proxies.size() - 1);
What about
node.proxies.as_mutable_span().last()
?Not sure why to go via the span. You can just
node.proxies.last()
.@ -107,3 +107,2 @@
int proxy_count = 0;
PBVHProxyNode *proxies = nullptr;
blender::Vector<PBVHProxyNode> proxies{};
Vector
has a default constructor, so no need for the{}
here. Think it's sort of just unnecessary noise.@ -3298,3 +3299,3 @@
{
PBVHVertexIter vd;
float(*proxy)[3] = BKE_pbvh_node_add_proxy(ss->pbvh, node)->co;
const MutableSpan<float3> proxy = BKE_pbvh_node_add_proxy(*ss->pbvh, *node).co;
I know the semantics are weird, but I usually don't write
const MutableSpan
since it makes scanning the code for "things that can change" more complicated. We often have a bunch ofconst Span<...>
at the top of a function, and theMutableSpan
stands out more if it isn't const. Typically reassigning the span itself doesn't really come up anyway. It's basically the east vs. west const topic I guess.Just always use const, unless it leads to compilation error ;)
@ -2300,3 +2266,3 @@
SCULPT_orig_vert_data_init(&orig_data, ob, node, SCULPT_UNDO_COORDS);
BKE_pbvh_node_add_proxy(ss->pbvh, node);
/* TODO(@sergey): This looks very suspicious. */
Just as a habit I guess it's nice if there's just a tiny bit more detail here
/* TODO(@sergey): Adding proxies here seems suspicious because ... */
@blender-bot build
@blender-bot build