Page MenuHome
Create Task
Maniphest T90272

Voxel Remesh Modifier - No Minimum Cap on Voxel Size? Crash on 0 value.
Closed, DuplicatePublic
Actions

Description

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

Blender Version
Broken: version: 2.93.2 Release Candidate, branch: master, commit date: 2021-07-27 12:05, hash: rB45ed762124c5
Worked: n/a

Short description of error
There doesn't seem to be an apparent minimum for the Modifiers > Remesh > Voxel > Voxel Size. If a user adjusts the voxel size using the interface, or by typing in a value of 0, Blender consumes 100% of CPU and RAM until Blender or system crash.

Exact steps for others to reproduce the error

On default startup:

  • Add to default cube: Modifier > Remesh > Voxel
  • Set voxel size to 0
  • Watch your motherboard burst into flames

Based on default setup.

Related Objects

Event Timeline

Jared Kuvent (Microweb4) created this task.Jul 28 2021, 7:34 PM
Silas Opel (Schamph) added a subscriber: Silas Opel (Schamph).Jul 28 2021, 7:51 PM

Did you slide the value or typed it in? I am for a soft limit when sliding the value but typing can be anything above 0. Mentioned it a couple of times also in the node thread where someone ported it to nodes.. Even though it might not be a bug in its definition, this feature should be added.

Robert Guetzkow (rjg) closed this task as a duplicate of T77868: Remesh Voxel Size can be much to small by default (leading to crashes). 'Edit Voxel Size' operator can have wrong range.Jul 28 2021, 7:57 PM
Robert Guetzkow (rjg) added a subscriber: Robert Guetzkow (rjg).EditedJul 28 2021, 8:01 PM

This should be partly addressed by D9074 and rBe95f71bf152ad227383c3512f848cd924512a68b by using a logarithmic scale for the slider in Blender 3.0.0. It avoids accidentally dragging it close to zero which causes out of memory issues because there far too many small voxels.