NVIDIA GameWorks Integration

[Alexey.Panteleev]

Alexey.Panteleev I tried TXAA3-4.19 and now it does give slightly different visuals on my testing. It doesn't really perform that well in comparison to unreals built-in TAA on my trivial ghosting test but one can tell it's not same ghosting anymore. For comparison shots:

Here's Nvidias TXAA 3: https://www.dropbox.com/s/5rxj6lhgqf...TXAA.gif?raw=1
and here UE4's TAA: https://www.dropbox.com/s/m0llmelg5j..._TAA.gif?raw=1

Ghosting isn't that bad on normal use cases, I just use that test as it brings the worst out of temporal AAs and can show what might happen on noisy materials.

As as side note, TXAA crashes UE4 instantly on postrprocessing pass if unreals forward shading is enabled. Is Nvidias TXAA supposed to work in forward at all?

Oh that scene is definitely a difficult case for the T(X)AA neighborhood filter. Try setting r.TXAA.UseRGB = 1, but I don't expect it'll become much better. Basically, the filter sees that the road has a range of colors from black to white, and the car falls roughly into the same range, so it's considered to be road as well. It should be better if there is some chromatic difference between the car and the road.

I'll need to look into the forward shading issue.

[0lento]

Alexey.Panteleev I tried TXAA3-4.19 and now it does give slightly different visuals on my testing. It doesn't really perform that well in comparison to unreals built-in TAA on my trivial ghosting test but one can tell it's not same ghosting anymore. For comparison shots:

Here's Nvidias TXAA 3: https://www.dropbox.com/s/5rxj6lhgqf...TXAA.gif?raw=1
and here UE4's TAA: https://www.dropbox.com/s/m0llmelg5j..._TAA.gif?raw=1

Ghosting isn't that bad on normal use cases, I just use that test as it brings the worst out of temporal AAs and can show what might happen on noisy materials.

As as side note, TXAA crashes UE4 instantly on postrprocessing pass if unreals forward shading is enabled. Is Nvidias TXAA supposed to work in forward at all?

[sudey]

Fixed. Исправлено.

Thank you. Спасибо. Если можно последний вопрос- Почему собранный движок иногда подвисает? не используя даже vxgi. В то время как движок от лаунчера допустим идет гладко. причина в сборке или так должно быть? Спасибо оперативность.

[Alexey.Panteleev]

Alexey.Panteleev

Hey while you are here I have question.

Did you considered optimizing Voxelization pass to not happen every frame ? Ie. do not revoxelize static objects, voxelize further cascades less often (every N frames). Etc ?

On complex scenes consistently even on 1080ti Voxelization pass is most time consuming. It would do wonders to make VXGI more scalable to lower end hardware.

Considered - yes, implemented - not yet.

There are two feasible options. One is to only update dynamic objects (not just UE-dynamic, but also moving static meshes) and regions that were not covered on the previous frame. This is somewhat problematic because it relies on the engine being able to compute accurate bounding boxes for dynamic objects, and also update parts of the static objects that happen to intersect with dynamic. Adding direct lights makes this even more fun because shadows potentially depend on objects far away, and objects that receive the shadows then also need to be updated.

The second option is to freeze the voxel representation for some number of frames while the game/project knows that things are static. This is relatively easy, but it will lead to stutter when something does change, and voxelization needs to happen. A more advanced version of this would perform voxelization of a complex scene over multiple frames, while VXGI lighting will be either turned off or based on the previous voxel data (with the latter requiring changes to VXGI itself to handle two sets of voxel data).

[Alexey.Panteleev]

Why when allow static light is disconnected, in case of switching on of vxgi 2.0, the engine crash? Почему когда отключен allow static light, при включении vxgi 2.0, движок крашется?

Fixed. Исправлено.

[0lento]

Why when allow static light is disconnected, in case of switching on of vxgi 2.0, the engine crash?

I noticed this as well. If you disable static lighting from project settings and enable VXGI, engine will crash immediately on VxgiRendering.cpp while trying to read nonexisting SceneContext.GBufferE.

[0lento]

I just went ahead and ported the TXAA integration to 4.19 and fixed the crash on viewport resize. It's not perfect (e.g. I expect the dynamic resolution feature will not work properly yet), but it's better than before.

To make sure that you're using TXAA and not built-in TAA, do something to break it, for example set r.TXAA.EnableColorClipping to 0 and observe trailing artifacts when moving the camera.

Thank you, I'll check the new branch

[sudey]

I just went ahead and ported the TXAA integration to 4.19 and fixed the crash on viewport resize. It's not perfect (e.g. I expect the dynamic resolution feature will not work properly yet), but it's better than before.

To make sure that you're using TXAA and not built-in TAA, do something to break it, for example set r.TXAA.EnableColorClipping to 0 and observe trailing artifacts when moving the camera.

Why when allow static light is disconnected, in case of switching on of vxgi 2.0, the engine crash? Почему когда отключен allow static light, при включении vxgi 2.0, движок крашется?

[iniside]

Alexey.Panteleev

Hey while you are here I have question.

Did you considered optimizing Voxelization pass to not happen every frame ? Ie. do not revoxelize static objects, voxelize further cascades less often (every N frames). Etc ?

On complex scenes consistently even on 1080ti Voxelization pass is most time consuming. It would do wonders to make VXGI more scalable to lower end hardware.

[Alexey.Panteleev]

Ok, I'll ping the author of that branch (or take a look at it myself).

I just went ahead and ported the TXAA integration to 4.19 and fixed the crash on viewport resize. It's not perfect (e.g. I expect the dynamic resolution feature will not work properly yet), but it's better than before.

To make sure that you're using TXAA and not built-in TAA, do something to break it, for example set r.TXAA.EnableColorClipping to 0 and observe trailing artifacts when moving the camera.

[Aeries]

Hi everyone,

UE 4.19 branch with VXGI 2.0 is up on GitHub: https://github.com/NvPhysX/UnrealEngine/tree/VXGI2-4.19

I'll try to answer your questions about it here.

THAT TIMING, THOUGH!! *dies happily*

[Alexey.Panteleev]

I'd also love to get some NVIDIA staff response on what's going on with the TXAA's UE4 integration. They also seem to neglect the issue thread on the repo about it. I could never get it to work (it compiles but it looks 100% same as Unreals built-in TAA, I have exactly same ghosting with it so it's safe to say it's not really running on TXAA). The branch on TXAA is also pretty old (based on 4.16) and it has some issues, like if you resize the viewport in editor it will just crash right away.

Ok, I'll ping the author of that branch (or take a look at it myself).

[0lento]

I'd also love to get some NVIDIA staff response on what's going on with the TXAA's UE4 integration. They also seem to neglect the issue thread on the repo about it. I could never get it to work (it compiles but it looks 100% same as Unreals built-in TAA, I have exactly same ghosting with it so it's safe to say it's not really running on TXAA). The branch on TXAA is also pretty old (based on 4.16) and it has some issues, like if you resize the viewport in editor it will just crash right away.

[0lento]

They've updated Flow for 4.19 as well: https://github.com/NvPhysX/UnrealEng...ee/NvFlow-4.19

[Novarek]

Hi everyone,

UE 4.19 branch with VXGI 2.0 is up on GitHub: https://github.com/NvPhysX/UnrealEngine/tree/VXGI2-4.19

I'll try to answer your questions about it here.

Nice job !
Now just have to wait for the merged GameWorks git ^^