When a User enables AMD Frame Generation in the User Settings and hits the Save button, he needs to restart the game for the changes to take affect. Before the game closes, these cvars get set in the Engine.ini:
r.FidelityFX.FI.OverrideSwapChainDX12=1
r.FidelityFX.FI.AllowAsyncWorkloads=1
For our game AMD Frame Interpolation works, but the debug UI causes flickering, therefore the param r.FidelityFX.FI.AllowAsyncWorkloads=1. For non-RDNA4 GPUs it works fine (also no flickering), but for RDNA4 GPUs (RX 90xx series) the game crashes on launch. Commenting out r.FidelityFX.FI.AllowAsyncWorkloads=1 in Engine.ini and make the file write protected works as a workaround, but then we have the UI flickering again.
Is this issue known and if so, is there a fix planned in the near future?
Thanks in advance
When a User enables AMD Frame Generation in the User Settings and hits the Save button, he needs to restart the game for the changes to take affect. Before the game closes, these cvars get set in the Engine.ini:
For our game AMD Frame Interpolation works, but the debug UI causes flickering, therefore the param
r.FidelityFX.FI.AllowAsyncWorkloads=1. For non-RDNA4 GPUs it works fine (also no flickering), but for RDNA4 GPUs (RX 90xx series) the game crashes on launch. Commenting outr.FidelityFX.FI.AllowAsyncWorkloads=1in Engine.ini and make the file write protected works as a workaround, but then we have the UI flickering again.Is this issue known and if so, is there a fix planned in the near future?
Thanks in advance