This is part of a deliberate change that will be called out in the Major Release Notes for 4.15 with more information.
We now use the default value of 1 for r.TonemapperFilm instead of 0. To get the old color emissive back you'll need to change the CVar back to 0.
When multiplying vector 3 (R,G,B) values by a scalar value of increasing quantity the emissive output will begin to change colors. The most unexpected is the blue color that will turn purple while the bloom remains blue.
The color turning white while being multiplied by larger values seems intentional however, there is no documentation to be found even in our internal 4.15 release notes regarding this behavior.
REGRESSION?
Yes
Worked: Binary 4.14.3 CL 3249277
Broken: Binary 4.15 Preview 1 CL 3258144
RESULT
The mesh will start blue then fade to purple if you continue it will turn white.
EXPECTED
The mesh stays blue with increased bloom as the emissive gets multiplied by larger values.
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
I am not able to find world outliner how to enable it?
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How does TextureRenderTarget2D get TArray<uint8> type data?
How does UMG set overlapping layouts?
Hey, why do i get this when i snap two similar meshes together?
Head over to the existing Questions & Answers thread and let us know what's up.
40 |
Component | UE - Graphics Features |
---|---|
Affects Versions | 4.15 |
Target Fix | 4.15 |
Created | Jan 24, 2017 |
---|---|
Resolved | Jan 30, 2017 |
Updated | Apr 27, 2018 |