I have added support of the environment probes to my AR application, but objects start to look “wet” with this type of probes. After some researching, I have found out that this could be related to the absence of a specular convolution feature for those probes. What should be done to fix this problem? Is specular convolution supported by mobile devices at all?
Images with an example of oversaturated reflections are in the attachment.
@tdmowrer is this something you are aware of?
The difference in the looks of the materials is immense between using a regular reflection probe and the environment reflections in ARFoundation for iOS. We ran into this when trying to run the same material library on both Android and iOS for our products.
Here is a comparison between the same materials with and without environment texturing:
Regular reflection probe:
Environment texturing:
As you can see we get heavy reflections in even low glossiness with the environment probes on, most visible in the two middle spheres.
Thank you @mkrfft ! Your images are extremely illustrative, this is exactly the problem we faced.
Hope that @tdmowrer will join us here! 
@tdmowrer : would love to have some input on this. Right now we are unable to use the same material library on iOS and Android due to this issue.
Specular convolution is a process that is applied at texture import time by the editor to generate mipmaps for the cubemap texture. This process is only available in the editor and is not available at runtime.
In the case of environment probes, ARFoundation is getting cubemap textures with pre-computed mipmaps from the ARKit or ARCore implementation. The Unity renderer is simply using these cubemap textures in the reflection probe at runtime.
Todd
Thank you for your answer!
So basically there is nothing to do with ARFoundation and all problems come from ARKit itself? It seems a little bit strange because reflections in native ARKit apps look fine without oversaturated glossiness…
Yet in Apple’s documentation, the examples look like the rough surfaces work as expected, why the difference? @todds_unity could you shed some light on that?
How do you get around these limitations and still have a manageable way for artists to work with roughness in AR apps?
Hi everyone, like @todds_unity mentioned, AR Foundation is only delivering the environment cubemap textures from ARKit to the Unity app. How your content looks at runtime is then dependent on how you use these textures.
In regards to support for specular convolution, there are no immediate plans but we’ll take it under consideration.
So we are still on the same step, waiting? It makes ARFoundation pretty useless when you want some relfections in AR…
