Remesh Modifier in Voxel mode produces surface artifacts when Adaptivity enabled #82834

Open
opened 2020-11-19 09:12:56 +01:00 by Andrii Mykhailov · 6 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71

Blender Version
Broken:

  • 2.83.9
  • 2.91.0 Beta, branch: master, commit date: 2020-11-17 22:01, hash: e580c18853
  • 2.92.0
    Worked: never

Short description of error
Remesh modifier produces artifacts on mesh which look like a result of bad triangulation.

Exact steps for others to reproduce the error

  1. Open attached blender file
  2. Open modifier panel and select testMesh
  3. Change adaptivity value from 1 to 0 cm and back
  4. Observe black shading artifacts
    remesh_bug.blend
    remesh_bug.png
**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71 **Blender Version** Broken: - 2.83.9 - 2.91.0 Beta, branch: master, commit date: 2020-11-17 22:01, hash: `e580c18853` - 2.92.0 Worked: never **Short description of error** Remesh modifier produces artifacts on mesh which look like a result of bad triangulation. **Exact steps for others to reproduce the error** 1. Open attached blender file 2. Open modifier panel and select testMesh 3. Change adaptivity value from 1 to 0 cm and back 4. Observe black shading artifacts [remesh_bug.blend](https://archive.blender.org/developer/F9323133/remesh_bug.blend) ![remesh_bug.png](https://archive.blender.org/developer/F9323140/remesh_bug.png)

Added subscriber: @zelfit

Added subscriber: @zelfit

Added subscriber: @rjg

Added subscriber: @rjg

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

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

The issue is that the modifier creates a vertex connected to surrounding vertices, but places it outside of the 1-ring neighborhood. This results in a self intersecting mesh and the strange shading. The vertex should be placed within the bounds of the surrounding 1-ring neighborhood or not be generated at all.

remesh_modifier.png

Note: While I have confirmed this problem for now, this ticket may get closed if this turns out to be an inherent limitation of the current implementation.

Contrary to my original comment, it does close the mesh properly. All neighboring vertices form a face.

The issue is that the modifier creates a vertex connected to surrounding vertices, but places it outside of the 1-ring neighborhood. This results in a self intersecting mesh and the strange shading. The vertex should be placed within the bounds of the surrounding 1-ring neighborhood or not be generated at all. ![remesh_modifier.png](https://archive.blender.org/developer/F9323681/remesh_modifier.png) Note: While I have confirmed this problem for now, this ticket may get closed if this turns out to be an inherent limitation of the current implementation. Contrary to my original comment, it does close the mesh properly. All neighboring vertices form a face.

Added subscriber: @LeonardSiebeneicher

Added subscriber: @LeonardSiebeneicher

There is another reason too.

Adaptive Voxel Remesher erases some details, and puts a lot of faces on areas which do not change much.

Just use Adaptive Voxel Remesh on a sphere:
aremesh.jpg

For some reason adaptive remesh does add a lot of detail to the sphere, while other areas are kept low-detail.
If a smooth brush on this sphere is used, there will be a lot of artifacts on areas where surface details vary.

There is another reason too. Adaptive Voxel Remesher erases some details, and puts a lot of faces on areas which do not change much. Just use Adaptive Voxel Remesh on a sphere: ![aremesh.jpg](https://archive.blender.org/developer/F10274393/aremesh.jpg) For some reason adaptive remesh does add a lot of detail to the sphere, while other areas are kept low-detail. If a smooth brush on this sphere is used, there will be a lot of artifacts on areas where surface details vary.
Philipp Oeser removed the
Interest
Modeling
label 2023-02-09 15:28:54 +01:00
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
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
3 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#82834
No description provided.