Update: PRISM v3 is now here! Hey Ivan, Please check our forum thread as beta signups for PRISM version 3 are now open, it is very far from discontinued, and instead has been re-written from the ground up with new features like Neural Network AO, Ultra HD Color Correction in CIELAB colour space, new DoF, bloom, and more. While I agree it has aged poorly, the new PRISM v3 again will be a highly compelling choice - unfortunately as I am one developer not able to work on PRISM full-time, vs. Unity's team of 5+ full-time post-processing developers who change their API every 6 months, it has been longer than what I'd like as well for an update. PRISM v2's bloom does actually have an attached flares component as well, it's located right underneath lens dirt. All color adjustments you mentioned can be achieved with PRISM v2's Look-Up Textures - which are getting reworked in v3, and were that way by design originally as it offers a higher level of performance than Unity's method, which is easier to use but re-bakes a 3D LUT every frame (a killer on mobile).

Hey Sjam, PRISM's bloom has a default that is specced more towards performance than Unity's PostFX Stack (which is also why it performs better when combined) - if you would like to visit our forum thread and post the look you are trying to achieve, I would be happy to show you how to achieve it with PRISM!

Hi Leo, Sounds like a 2018.x issue, which I'm happy to get resolved for you. I don't have a current iOS device to test on so it's hard for me to fix this without the help of users, but I definitely want to make sure whatever bug that is gets fixed (likely a simple metal compiler gotcha in 2018). If you would like, I can offer 1-on-1 support for you to get this bug fixed (and likely improve performance in 2018.x as well), alternately I'm happy to give a refund if you are rushed for time and can't swap back to 2017 for the moment in your project. Thanks, Alex

Hi Anflo, I'd be very surprised if PRISM did actually 'destroy your project' - it is comprised of 4 primary shader files and a couple of scripts which utilize basic Unity functionality. Please get in touch with me if you can reproduce this issue, I endeavor to respond to support emails within 24 hours. PRISM has been tested (and used on released games across all platforms) on all Unity 5.x platforms, as well as Unity 2017.1. If you can reproduce this issue, I will happily refund you and also give you a key to PRISM so you can still use it.

Hi JD, This error (related to PRISM's brand new VR support) has since been fixed. Please update to the latest asset store package to get the fix.

Hi Curtis, Recent instability has been caused by migrating PRISM completely over to have VR-compatibility, which required changes of over 200 lines of shader code - definitely a bumpy few updates, but I believe it's worth it for our VR developer community. As always, if you don't need features like VR support, you should stay on whatever version of PRISM works for you. PRISM's latest update has full 5.6.1 support.