Without Image Stabilization, there is no blinking of Game Objects.
Why does it happen?
- Unity 6000.1.5
- AR Foundation 6.1.0
- Vulkan Graphics API using customized as it indicated here
- URP
- Samsung Galaxy A71
Hi makaka, thank you for reporting the issue. If you haven’t already – could you also kindly file a bug report through the Unity bug report portal (steps)? That way it would get to the relevant teams faster, especially if it requires a particular project set up.
Do you know if this only happens on Galaxy A71, or does it also occur in other devices you have tested?
I’ve only tested on A71
Is the blinking reproducible only in your project, or is it reproducible with an empty project / AR Foundation sample project as well?
I used Raw Project with Unity 6000.1.5 and “AR Mobile” Official Template with the Development Build option checked.
Added Vulkan API by the manual for the 1st place in the list of API in the Player Settings, and check “Auto Graphics API” flag: Universal Render Pipeline | AR Foundation | 6.1.1
Then turned on the Image Stabilization on AR Camera Manager.
Linear Color Space
Gamma Color Space
On my personal projects, Image Stabilization also causes blinking on Game Objects (not only on shadows).
Do you have occlusion features active in the scene?
I don’t remember about AR Mobile template, but on my FPS Shooter Template there are no occlusion features enabled, so I disabled the stabilization to avoid this bug.
I had a theory that somehow occlusion was causing the shadows to flicker but I’m not sure if you don’t have that enabled, we will have to see in the bug report then, also thank you for filing a bug report!
Is there any update on it?
Hey there, sorry for the delayed response. Lots going on lately!
Did you file a bug with Unity for this issue? It should have a bug number of the format IN-XXXXX. If you have a bug number, we can sometimes help in interactions with QA to make sure that a reproducible bug gets an IssueTracker link.
Once the issue is in IssueTracker, we are able to assign it to our team based on priority and available capacity.
Yes, posted above in 2025: IN-104392
I went to look at IN-104392, and I see that this issue was closed in August 2025 by our QA team. They tested on multiple Android devices and were unable to reproduce the issue on any of them. Have you tested on any devices other than the one you listed in the bug report? If this issue only reproduces on one device, it’s more likely an issue with the device manufacturer.