The PackageManager now contains Mac-only package: ObjectCaptureFromPhotos available to those running macOS Monterey (or later) on Apple Silicon Macs. This command uses photogrammetry to process a set of photographs to produce a mesh and an associated material:
Got it. I am curious why did you decide to only make it Apple Silicon compatible, if it would in theory work? My naive guess is, that this would not necessitate any software development work from your side?
Preview- 90 secs-25k vertices- not the best texture mapping, “soft” low-detail mesh, but usable for preview
Reduced - 4 mins - 24,999 vert- better texture mapping, and meshing detail is improved
Medium - 4 mins - 50k vertices- texture mapping appears similar to the Reduced setting, meshing detail is a step up again with corners, edges looking crisper
Full- 5 mins - Status bar completes, pauses to think about 30 sec until the timeout, then got this error.ObjectCaptureFromPhotos error occured. Failed to create: “longFileName”/baked_mesh.obj
Also this command does not show in Repeat Last Command dialog box on right mouse click.
On import, the size comes in as a unit of the current measuring system. It might be 1.2 mm, 1.2 in, 1.2 ft. in your workspace.
This was all just quick playing to see what was up. Gonna play with the Nike files. Very nice potential here. Thanks for tossing a bone to the Mac folks!
RH-66252 ObjectCaptureFromPhotos: progress should include file import step
I implemented that part rather poorly and I bet that will prevent people from testing out really large captures until I fix it. I’ll prioritize that one.
That was intentional…but perhaps misguided on my part. I presume you’d want it to be repeatable? Logged here:
RH-66337 ObjectCaptureFromPhotos: Remove DoNotRepeat status
Ah yes, that We might be able to be smarter about the units…I’m not sure. If the source images are HEIC from a modern iPhone, we could infer some real-world measurement (the stereo cameras allow for this). Otherwise, I’m not sure what people would expect. Perhaps we need some sort of calibration?
re: RH-6637- If by “repeatable”, you mean access from right click command history, then yes. Of course I want to repeat it easily because I ran it about a dozen times in a row last night.
Re: Units- Yeah, kinda feel like something is needed here, but not sure what. Many 3d printing software packages can give a “Object is very small/large. Do you want to convert it?” size warning on import. Usually just meaning you are in Metric mm or Imperial inches In Rhino it is a bit trickier as you could be in feet, inches, mm, meter, cm, etc. I used several different size templates. Of course, for the shoe- “Small Objects - Feet” is the only the correct choice.
— I did think I saw that the TrueDepth cameras can maybe give something close to actual measurements since they use it for FaceID. I wonder if the LIDAR in the newest phones can be tapped. It would be cool to have a “Smart Opening” if that info was passed in from Apple.
Lastly, the Nike shoe files from Apple seemed to display very nicely, but of course were slower to process due to double the photos, but not bad (again, got the error for Full setting), taking about twice as long. These are very good scanning examples made by someone that took care and planning on their scan. There is an art to creating a quality scan.
For others to reference for speed, I am using a 2020 16GB M1 mini