Search Issue Tracker
Fixed in 5.6.0f3
Votes
0
Found in
5.5.0f3
Issue ID
859497
Regression
Yes
[iOS] Hidden/Fastblur (BloomOptimized) shader does not work on iOS with Metal
Hidden/Fastblur, when applied to the camera, has no effect on iOS with Metal API.
Steps to reproduce:
1) Open the latest attached project.
2) Build for iOS.
3) Run on a Metal-enabled device.
Errors show up in Xcode console:
'The image effect Main Camera (UnityStandardAssets.ImageEffects.BlurOptimized) has been disabled as it's not supported on the current platform.'
The scene contains a single cube. On the Editor it is blurred out (due to the effects of the shader attached to camera), however, on iOS this effect is not visible when Metal is used. Does not reproduce with OpenGLES.
Reproduced on:
5.6.0b1, 5.5.0p1
Did not reproduce:
5.4.3p3
Devices tested:
iPhone 7 iOS 10.2
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
DrakkenWulf
Mar 05, 2019 20:18
Can confirm that it starts working if you remove the SGX blur shader content and support. Not sure why, might be too complicated. Splitting the one shader into two would probably suffice for all reasonable needs.
This is now available as part of the Legacy Image Processing package on the Asset Store.
Glowing_Slab
Sep 17, 2018 18:12
Not working in OSX Metal build in 2018.2.8f1.
eelstork
Aug 07, 2018 09:06
Broken in 2018.2.1f1
puzzlekings
Jul 02, 2017 20:07
Just seen this issue again in Unity 2017.1.0f1