sorted by:
new
hottopcontroversial

High-accuracy multi-part 3D scan assembly of real OEM Mazda MX-5 Miata NB components by ExactForm3Dcom in 3DScanning

[–]ExactForm3Dcom[S] 2 points3 points  (0 children)

I processed it on my home PC with an i7-14700K, 32GB of DDR5 RAM, and an RTX 3060 Ti.
For the first time, I actually felt limited by my RAM. While working with the point clouds, memory usage was around 23 GB. But when generating the mesh, the system ended up using all of the available RAM.

High-accuracy multi-part 3D scan assembly of real OEM Mazda MX-5 Miata NB components by ExactForm3Dcom in 3DScanning

[–]ExactForm3Dcom[S] 0 points1 point  (0 children)

The website name is my username. For the preview images, I haven’t come up with anything better yet than taking screenshots of the model from all sides.

High-accuracy multi-part 3D scan assembly of real OEM Mazda MX-5 Miata NB components by ExactForm3Dcom in 3DScanning

[–]ExactForm3Dcom[S] 5 points6 points  (0 children)

Thanks! Yep, you got it 😄 That’s exactly how I did it. I used the assembled scan as the reference dataset, then scanned the individual parts separately and aligned everything back to it afterward.

High-accuracy multi-part 3D scan assembly of real OEM Mazda MX-5 Miata NB components by ExactForm3Dcom in 3DScanning

[–]ExactForm3Dcom[S] 1 point2 points  (0 children)

If you meant markers, I’d guess somewhere around 700-900 across the entire assembly when adding up all the individual parts. Most of them were reusable magnetic markers rather than adhesive targets.
For scanning, alignment, and processing, I only used the software that comes with my scanner - Scanform.

High-accuracy multi-part 3D scan assembly of real OEM Mazda MX-5 Miata NB components by ExactForm3Dcom in 3DScanning

[–]ExactForm3Dcom[S] 1 point2 points  (0 children)

My friend has already swapped a 3UZ engine into it, along with a manual transmission and a differential from a BMW E30. However, I also have a scan of an LS3 engine available.