search

Unity-Technologies / arfoundation-samples

Example content for Unity projects based on AR Foundation
Other
3.07k stars 1.15k forks source link

Problem with XRCpuImage.ConversionParams when dealing with depth images #761

Closed AndreNicolai closed 3 years ago

AndreNicolai commented 3 years ago

Hey there,

I discovered a problem when I was trying to access depth images on the CPU, which only seems to work when setting XRCpuImage.Transformation to MirrorY.

How to reproduce: Try to build the 'CPUImages.unity' scene for iOS/Android after changing the transformation to either 'MirrorX' or 'None' in the 'CPUImageSample' class line '295'. When running the sample on the phone, much of the depth image data seems to get lost along the way, somewhere.

I tested this on iOS, only, so far, with both Unity 2019 + 2020 and ARFoundation 4.1.5 respectively 4.1.3.

Can anybody confirm this is happening?

Best regards,

André

tdmowrer commented 3 years ago

Could you please log a bug by following the directions at https://unity3d.com/unity/qa/bug-reporting and post the case ID here?

AndreNicolai commented 3 years ago

Sorry for the delay, but here is the case ID: 1321178.

By now I was also able to do some testing on Android and can report that this issue does not occur.

tdmowrer commented 3 years ago

Thanks; we've reproduced it on iOS. Will look into it.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

artoonie commented 3 years ago

Hi, I'm experiencing the same bug. I heard that it's already on the internal bug tracker but not on the public issues list. Can it be added there?

In particular, only 64 lines of depth data are accessible when MirrorY is disabled. iPhone 12, latest iOS, latest Unity version.

tdmowrer commented 3 years ago

The public issue tracker link will be available shortly here: https://issuetracker.unity3d.com/product/unity/issues/guid/1321178/

tdmowrer commented 3 years ago

This was fixed in a recent release (4.2.0-pre.8).