Bloom does not work in Build

Hello,
i just upgraded to Unity 2019.1 today. I could fix most of the problems caused by the update, but not the following one.

I use bloom from the post processing stack in combination with HDR-Color / emission to add a glow effect to Images. This worked fine in 2018.3 and but in 2019.1 it only works in the editor but not in the final build (MacOS).
Editor:


Build:


Setup & Settings:
- 2019.1 + LWRP 5.7.2
- Post Processing 2.1.6



Maybe someone has a solution for the problem? I cant get it to work ...

 

I did submit a bug report for this issue and got the following answer:

"... We successfully reproduced this issue and have sent it for resolution with our developers ..."

So for all others having the same problem, i think we have to wait for a patch/fix.

EDIT:
Please vote if you have the same problem: https://issuetracker.unity3d.com/issues/macos-bloom-does-not-work-in-standalone-build

 

This needs more attention, if any of you are working on a project at the moment that requires this part of the PPS, please take the time to report / vote on the link provided by MidnightGameDeveloper. We need this to be pushed up the priority list!

 

Up-voted the issue tracker. Seeing it on 2019.1.4f1, Windows, Standalone.

Any work-arounds for this? I'm using the post-processing v2 stack... thinking of reverting to v1. Very disruptive bug indeed.

 

Maybe you should report this as a new bug, if it happens also under windows.
The reason why the bug does not get any attention could be that its tagged for macOS...

 

Looks like the Tracker has been updated that the bug is under "Regression". Usually that means either the Devs/QA are actively trying to recreate the bug, or actively testing a fix. Hopefully something will develop soon.

 

Well this good news! Hope it is resolved quickly. I saw 2019.1.5 was released so I was going to test it out but seeing this makes me think we'll be waiting a bit longer. Here's to hoping sooner than later.

 

I am not sure, but i think "Regression" simply means a return to a former or less developed state. So the problem is not occurring in the older versions but in the new ones!

 

From my experience in the Software Engineering field, "Regression" is a loosely defined term that is interpreted differently depending on the engineering group.

Here is what Wikipedia thinks it means:
https://en.wikipedia.org/wiki/Regression_testing

 

in 2019.1.8f seems to be working fine now! I checked for both built-in and LWRP.
Thanks to whoever fixed this!

 

Good to know, thanks!

 

please help to solve this