Marius Kintel

A more minimal test would indeed be great. In the meantime: @pca006132 This is the stack trace - looks like an exception thrown when calling the Manifold constructor. ``` OpenSCAD!manifold::VecView::operator[](unsigned...

The hard crash is likely a separate issue, so let's deal with that separately. The warning is pretty common. Since you're modeling in pretty small coordinates, it's likely an issue...

We optimized the Manifold interface code quite a bit around mid-March, so we probably uncovered some instability.

@pca006132 I slimmed down the example to this. Note: Lots of very close vertices: ``` cube(0.1); union() { multmatrix([[0.939693, 0, -0.34202, 0], [0, 1, 0, 0], [0.34202, 0, 0.939693, 0],...

This may be a partial duplicate of #4824 Note: There are two separate places where Manifold throws this exception: 1. The original example in this issue is about throwing in...

Also, try to enable `Preferences->Features->manifold` - this new geometry backend is quite a bit more robust.

With manifold enabled, your design renders perfectly on OpenSCAD-2024.03.17 on an M1 Mac, without any offset needed.

The union worked fine after enabling manifold. Are you still having a problem with that?

You have to restart, or do `Design->Flush caches`. We don't spend too much effort on UI or docs for experimental features, until they make it out of the experimental stage..

You don't even have to create a separate file: Just wrap the partial theta sweep in a `render()` statement, and it will be cached. Using that trick rendered the full...