Scene Capture Cube Missing Post process Effects

Hi;

In the [Reflection project] here is a [captured screen shot in the Editor][1]

When I tried to create a 360 degree image [HDR] using a [Scene Capture Cube] & a [Cube Render Target];

[I got this…][3]

As you see the second image is missing most of the post process effects, moreover there is no emissive materials effect…
I don’t know whether it is [Cube Render Target] limitation issue OR I had missed something to tweak…

BTW;

_All the scene capture cube settings [flags] were set to ON.

_I had checked the [Engine Scalability Settings] and they were set to High.

My aim is to get a 360 degree image with full post process effects [just as with a camera shot] watch this All Photos | Littlstar - The World Revolves Around You

Best regards & Thanks for any advice

Still; waiting for an advice & Help

Hello Cadviz,

I was able to reproduce this issue on my end. I am currently investigating this and will get back to you.

Hi ;

You are welcome at any time…

Thank you for your kindness

This does appear to be a bug as I am able to reproduce this on my end.

I have entered a ticket for this issue. That ticket number is UE-22187.

Thank you very much for reporting this.

I will keep you posted on this bugs progress.

I think the HDR content is very dark and the artist fixed it by ramping up the Exposure Bias.
How do you display the cubemap - if it’s in the scene it should work, if in TextureProperties it will not - there is no exposure / eyeadaptation.

Hi;

Since I want to use the [360 degree image HDR] outside UE4; The best result I had reached was by this try:

  1. Inside UE4… Export the [Render Target Cube] as HDR.

  2. Inside Photoshop

_Open The exported HDR

_Change the Image mode to 16bits/channel,

_ In the [HDR Conversion] window; increase Exposure to 5

_Save the image as PNG

Does that bug involve just Post Process effects in general not showing in a cube render?

Any word on the progress for this bug fix? I am still experiencing it on 4.10 and 4.11, but only in scene that have been updated from previous versions.

This was determined as not a bug, but the need to edit the auto-exposure bias setting, see accepted answer.