NVIDIA GameWorks Integration

[anonymous_user_7c71c8ec]

@dkloving;568987

Okay, makes a lot of sense and explains the effect seen when turning multibounce on. So, when we make lighting changes, we could simply run a few updates of the scene and then stop to get multibounce?

If the anchor is static, yes, you could do that.

@dkloving;568987

There is only one possible anchor point per scene right? We place a VXGI anchor in the middle of the scene, which I presume overrides the normal camera-located anchor? Our scenes are interior / room-scale, so is workable for us.

Correct, there is only one anchor. When you place and enable VXGI Anchor component, you override the default one attached to the camera.

If the scene is completely static and the anchor is static too, you can hack the engine to stop doing all the voxelization calls after a few frames… the main problem I guess would be to detect when you can do that.