Platform category: Unity 2022.3.62f2 and Unity 2022.3.62f3
Device type & OS version: iOS 26.2
ARDK version: 3.15 and 3.17
After updating iPhone devices to iOS 26.2, meshing accuracy has significantly degraded, directly impacting production measurements.
Reconstructed surfaces are systematically offset inward (deeper) compared to their real-world physical positions.
(See attached screenshots for visual comparison.)
Regression Context:
The issue started immediately after upgrading to iOS 26.2.
No project settings were changed at the time of regression.
Prior to iOS 26.2, meshing accuracy was acceptable and stable.
This issue is not related to visual fidelity; it directly affects metric correctness.
A fix for the meshing depth regression introduced in iOS 26.2, or
Clear, officially recommended configuration guidelines to achieve measurement-grade meshing accuracy, if the default/sample configuration is not intended for precise measurements.
If additional flags, parameters, or engine-level workarounds are required to restore previous accuracy, please provide explicit instructions.
Bug reproduction steps:
Install the Lightship ARDK Sample Project using default settings.
Deploy the project to an iPhone running iOS 26.2.
Launch the application and open the Meshing Sample Scene.
Slowly scan a flat vertical surface (e.g. a wall) and a horizontal surface (e.g. floor).
Observe the alignment between the generated mesh and the real-world surfaces.
As you noticed we were having some issues with replies showing up on the forums but you should be able to see this one. To keep all the information in this post I’ll add a brief summary of the messages that did not come through.
I started off by asking if you can provide information on the devices this is happening on to which you replied with the following:
iPhone 12 | iOS 26.2 and 26.01
iPhone 14 | iOS 26.2
iPad 10th Gen | iOS 26.2
I did test out meshing on an iPhone 13 Pro and didn’t observe any inconsistencies with the mesh. I’ve presented your screenshots and reproduction steps to our developers so that they can take a closer look. I will reach out to you as soon as I have new information to share
Could you confirm the version of the ARDK Samples that you’re running? The version will be located on the bottom left corner of the main samples app list when you first launch it.
Yeah we had some time to take a look and one factor we did want to point out (in case this is a deal breaker) was that our meshing feature does NOT offer measurement grade accuracy.
If this is still a bug you want to continue troubleshooting regardless, our development team did ask if some recordings could be provided to be able to see meshing bug in real time and if possible recordings with both iOS 26 and iOS 18 if you happen to still have a device running iOS 18.
Yes, I would like to troubleshoot this. Previously, we had extremely good accuracy, which is why we decided to use it as a measurement tool. However, now the mesh is placed farther than the real surface. This can be a significant difference that has a real impact on the project.
I will post several recordings in the next messages.
I’ve been planning to use your SDK and noticed some comments mentioning issues. I’m still very interested in using it and wanted to check in on the current state of things.
I was also considering using it for measurement systems, but I see there have been some recent accuracy losses with newer iOS versions. Could you share an update on the current status and any recommendations?
We’ve released NSDK 4.0 and would encourage you to try it and see if the updates meet your expectations. NSDK 3.17 will continue to be supported for another year but will not receive any new updates other than critical bug and security fixes.
