Is it safe to use it this way in terms of performance? In Oculus branch, it was safe, because it was not causing the “standard” mobile-hdr negative performance impact, but was only enabling specific features such as LUTs, vignette and etc (described here) with minimal performance impact. When I enabled it, my SpaceSky color changed, so I started wondering if it is ok.
If we enable mobile-hdr, to we need to modify any other options in the project settings?
It’s not typically necessary to modify other settings when enabling Mobile-HDR, but check the project’s post-processing settings to ensure they align with your performance and visual quality goals. Always test thoroughly on target devices.
In 5.4 we currently only support Tonemap Subpass w. HDR. Tonemap Subpass w. LDR is supported on Meta’s fork, and we’re looking at taking those changes sometime in the future.
Starting from the vrTemplate, the only way to enable Mobile HDR is to disable desktopTAA on mobile. After that and building for Quest, you get glitches and one black eye. You have to disable MobileMultiview AND switch from MSAA to TAA to get it working on Quest but the AA looks just horrible.
The alternative to get mobile HDR is to switch the mobile shading method to deferred but then you’re in the same situation again; you need to disable MSAA and mobile multiview to get things working again but that results in a big framedrop and blurry graphics (due tot TAA).
Any suggestions @VictorLerp how to enable HDR (for bloom and exposure) on Quest and still have decent performance and visual quality?
And for this feature I had to switch to oculus version of unreal. But I want to use standard UE, that’s why was hoping maybe these functionalities have been merged.
