Yeah we are also getting a lot of random crashes. Most seem to be related to the Metal framework. I have reverted to Beta 2 for now which seems far more stable but sadly produces much inferior results in our testing.

The past betas there was issues with Metal that causes a lot of crashes for us. I was hoping this would be fixed in this release. I have to say it has been rather disappointing on how Apple has rolled out these new features so far. First it took 1 month for the sample code to land and then there was multiple issues with memory usage and performance on early betas. and then they entirely changed to the Observable Object Framework without any notice and or updating their sample code.

thanks @brandonK212 . I wish there would be a notification in place in case these samples get updated. Maybe good to file a feedback request for it.

You could capture with an iphone side by side with your current setup and then apply the scale from the iphone model to the full model. technically the way scaling is done in most Photogrammetry sw is via scale bars that get detected by the software where you define your bounds and it then scales the models based on a few of these points in space that have a given distance defined. sadly there is no support for this in PhotogrammetrySession yet. maybe file a suggestion.

not supported in ObjectCaptureSession as confirmed by Apple directly. You can continue to use the macOS APIs for that though.

you could request for Apple to support scale bar detection. that way you could define a scale from that bar and get very good accuracy with Photogrammetry. Even the lidar currently has a 3cm variance which is too much if you are after high accuracy.

no size limit but there is an image limit of 1000 images so anything larger than an elephant is probably a no go at good quality.

we are also facing this issue and have filed this bug a long time ago. FB13157298. yet to receive a response from Apple on this. it has issues both with previous images captured with their sample app but also with images captured from their own native camera app.

Super helpful thread. How could we enable this programmatically via swift? noticed reality composer pro has these settings we can enable for an asset.

this would be especially useful for Object Capture photogrammetry models as well.

Thank you for the quick response. Images were captured with AVFoundation on an iPhone 16 pro max. I have filed this as: FB18747950

thank you. |default 19:07:58.533572+0200 Object Capture Reconstruction Mobile assets are already available, not requesting again. so I guess this means the model has been downloaded successfully. given that I am still not seeing any improvement on the model after reconstruction compared to a few weeks ago I think the ticket is still valid. I would love to know in which case this new helps (I tested a dataset of a black matte frame that has little to no texture) and what datasets Apple has tested this with. It's hard to evaluate a new feature without more information. thanks!

We also filed an enhancement request on this (FB20353610). 24MP capture would be a welcome addition while keeping file sizes manageable.