A request I’ve heard a lot recently is the ability to get the raw camera texture pixels on the CPU for computer vision or other custom processing applications. While was already possible, it involved reading data back from the GPU, which can be slow. No longer!
ARFoundation now supports raw camera image access on both ARCore and ARKit with a new Camera Image API. The documentation includes samples code snippets, and you can find a functional sample over on the ARFoundation Samples Github repo.
Thanks for all your work on ARFoundation. I upgraded all of my XR components today to fix the iOS 12 bug reported here:
As part of this, I also upgraded ARFoundation to 1.0.0-preview.19. Now after enabling and disabling the ARSession a couple of times, I’m getting an illegal memory access crash within the CameraImageApi.
I’m building for iPhone 8 running iOS 12. Attached is a screenshot of XCode at the time of the crash.
I can also file a proper bug report if you’d like.
Hi @tdmowrer
I too experienced issues on IOS after upgrading to ARFoundation 19… I also tracked down a crash to Arkit 16… I ended up building with different combinations of versions of packages to get a stable enough build.
My question is, what versions of the folliwing should “currently” work best based on your testing (simply updating all to the latest does not work best)
Arfoundation package
ARKit package
Unity versiin
Xcode version
Min target ios version
Are these thing tightly coupled and where is the best place to check dependencies between them when each are updated?
