Remesh modifier generates different results depending on object origin position #31626

Closed
opened 2012-05-28 18:31:55 +02:00 by Emanuele Gissi · 3 comments

Relates to: #31111

%%%Currently Remesh modifier voxel size depends on the following expression:

voxel_size = max(ob.dimensions) / mo.scale / 2 ** mo.octree_depth

When the object origin lies inside the object bounding box, max(ob.dimensions) is the max size of the bounding box in local coordinates.
In this case the voxel_size does not depend on the position of the object origin.

When the object origin lies outside of the bounding box, max(ob.dimensions) considers the position of the origin as well.
In this case the voxel_size depends on the position of the object origin.

See attached example: the five boxes are identical, the same Remesh modifier is applied.
The resulting modified cubes are different:

  • the green boxes object origins lie inside the bounding box,
  • the red boxes object origins lie outside from the bounding box; voxel_size changes, the result changes!

IMHO a proper and dependable implementation would require:

  • mo.scale and mo.octree_depth properties should be replaced by mo.voxel_size;
    or use a fixed reference lenght instead of max(ob.dimensions), e.g: 1 Blender unit.

  • object origin should become the reference point for the voxelization.
    In other words: one voxel center always lies at the object origin.

Tell me if further research is required.
Thank you very much and best regards,
Emanuele Gissi%%%

**Relates to**: #31111 %%%Currently Remesh modifier voxel size depends on the following expression: voxel_size = max(ob.dimensions) / mo.scale / 2 ** mo.octree_depth When the object origin lies inside the object bounding box, max(ob.dimensions) is the max size of the bounding box in local coordinates. In this case the voxel_size does not depend on the position of the object origin. When the object origin lies outside of the bounding box, max(ob.dimensions) considers the position of the origin as well. In this case the voxel_size depends on the position of the object origin. See attached example: the five boxes are identical, the same Remesh modifier is applied. The resulting modified cubes are different: - the green boxes object origins lie inside the bounding box, - the red boxes object origins lie outside from the bounding box; voxel_size changes, the result changes! IMHO a proper and dependable implementation would require: - mo.scale and mo.octree_depth properties should be replaced by mo.voxel_size; or use a fixed reference lenght instead of max(ob.dimensions), e.g: 1 Blender unit. - object origin should become the reference point for the voxelization. In other words: one voxel center always lies at the object origin. Tell me if further research is required. Thank you very much and best regards, Emanuele Gissi%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Thanks for reporting, the bounding box calculation had an initialization bug. Fixed in r47443.

I'm taking another look now at making the suggested "voxel_size" property change. Since that is feature change rather than a bug, I'm closing this report and will email you about it directly.%%%

%%%Thanks for reporting, the bounding box calculation had an initialization bug. Fixed in r47443. I'm taking another look now at making the suggested "voxel_size" property change. Since that is feature change rather than a bug, I'm closing this report and will email you about it directly.%%%

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
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
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#31626
No description provided.