Simulate the cuts as the tool moves rather than just the final cut workpiece. The advantage is that it would help in debugging problems if you could see exactly when a cut (or over cut) was made. However, OpenSCAM already allows you to run the simulation at any point in the cutting process by setting the tool path to that point and resimulating.
The plan is to invalidate regions of the 3D space and have the renderer regenerate affected 3D blocks as needed.
The text was updated successfully, but these errors were encountered:
I was not aware of voxelcut. However, it's unlikely that voxel methods will be as efficient, in terms of accuracy and speed, as the method OpenSCAM uses. Actually, I already know how to solve this problem, it's just a matter of finding the time to do so. Thanks for your input.
Simulate the cuts as the tool moves rather than just the final cut workpiece. The advantage is that it would help in debugging problems if you could see exactly when a cut (or over cut) was made. However, OpenSCAM already allows you to run the simulation at any point in the cutting process by setting the tool path to that point and resimulating.
The plan is to invalidate regions of the 3D space and have the renderer regenerate affected 3D blocks as needed.
The text was updated successfully, but these errors were encountered: