In playing around with the Meerkat demo, I am getting something that I don’t expect.
If I open up the project and hit play, I get this, which matches the YouTube video on the project, so I am sure its right:
However, if I change nothing and build lighting, I get this:
Since certain materials seem to be picking up more blue, I looked around for some blue light somewhere and came across Rayleigh scattering in the SkyAtmosphere settings, and changing the color did seem to help some (I just lightened the blue and did not tweak this at all, but I am sure it could be used to get closer even though its likely definitely not the problem)
The only caveat to all this is that as soon as I opened the project the first time, the first thing I did was change the project to Ray-traced and built the lighting and the result was the same. At some point, I deleted that project to start over but every time I build lighting this is the result I get. Something I read really quickly gave the impression that there was some behind the scenes “connectedness” with UE projects, but it was just something I saw really quickly so I might be wrong about that. But it just seems to me like that first raytraced lighting build keeps sticking around somehow, even though my intuition tells me that is not the case, as I’ve rebuilt the lighting in raytraced and non-raytraced several times.
And even if it was sticking around, why would simply changing the project to raytracing produce such a stark difference? And secondly, why would it even play in the first place without having built the lighting? When you first open the project there is no builtData for the map. Is that because the shaders were just compiled and therefor the lighting is already built in some temporary space?
Any assistance appreciated!