Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Office Holiday

Epic Games' offices will be on holiday from June 22nd to July 7th. During this period support will be limited. Our offices will reopen on Monday, July 8th. 

[Closed] FXAA without tonemapper


I would like to use FXAA without tonemapping. If I either replace the tonemapper with a custom one (as a blendable in a global post process volume), or disable it completely using FEngineShowFlags, FXAA does not seem to work anymore. Is this expected behaviour ?

Note : temporal AA still works in this case, but I would prefer FXAA since I am capturing a preview scene (previous frames information would not be available for TAA).



Product Version: Not Selected
more ▼

asked Oct 27 '16 at 09:19 PM in Rendering

avatar image

Answers.Archive STAFF
1.9k 206 312 684

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Oct 27 '16 at 09:20 PM by AndrewHurley for the following reason:

The question is answered, right answer was accepted

1 answer: sort voted first

Hi Nicolas, Thanks for reporting this. It looks like this is a bug. FXAA requires luminance in the alpha channel in order to work, and that's not generated if you're using a custom tonemapper.

You could workaround (albeit with some loss of quality) by defining FXAA_GREEN_AS_LUMA 1 in FXAAShader.usf.

The proper fix would probably involve modifying the pixel shader in PostProcessMaterialShaders.usf like this (from PostProcessTonemap.usf):

 half3 Color = GetMaterialEmissive(PixelMaterialInputs);
 half LuminanceForPostProcessAA = dot(Color, half3(0.299f, 0.587f, 0.114f));
 OutColor = float4(Color, LuminanceForPostProcessAA);

You'd probably want to only do that for materials with BL_ReplacingTonemapper.

I think also you'd need to make the BL_ReplacingTonemapper PostProcessMaterial output to a R8G8B8A8 texture, because it uses an R11G11B10 buffer currently.

I'll get this bugged at our end so we fix it in a future release.

more ▼

answered Oct 27 '16 at 09:19 PM

avatar image

Answers.Archive STAFF
1.9k 206 312 684

avatar image Answers.Archive STAFF Oct 27 '16 at 09:19 PM

For tracking purposes, this is bugged as UE-35455

avatar image Answers.Archive STAFF Oct 27 '16 at 09:19 PM

Hey Ben,

Thank you for your help :)
It would actually be an issue for us to have a modified engine (even if it is a single shader), so we will probably wait for the fix to be integrated to a proper engine version. Can we expect it to be in 4.14 ?

Have a nice week end,


(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question