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).
Thank you. Спасибо. Если можно последний вопрос- Почему собранный движок иногда подвисает? не используя даже vxgi. В то время как движок от лаунчера допустим идет гладко. причина в сборке или так должно быть? Спасибо оперативность.
@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/5rxj6lhgqfbxfd6/419_TXAA.gif?raw=1
and here UE4’s TAA: https://www.dropbox.com/s/m0llmelg5jquzw7/419_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.
Let’s stick to English here…
I’m not sure why the non-VXGI engine that you build yourself sometimes lags, compared to the binaries from Epic. Are you building the Development Editor configuration? Are you running it from Visual Studio - if so, will it still lag if you use Debug / Start Without Debugging command? In any case, you should probably discuss this with Epic support.
Hi Alexey, thanks for the the VXGI 2.0 update. Started diving into the new post process format.
Do you have suggestions for an extreme performance setup that would be similar to former:
VXGI diffuse only - 4 Cones - 3 Tracing Sparsity - Cone Rotation On - Refine Space tracing On - Multi-bounce On - MapSize 64.
After trying Tracing-resolution Quarter-Res, MapsizeX/Y/Z 64 and Quality/sample Rate to .5 i feel like i lost a couple frame per second compared to my former performance setup.
I’m merely trying to define an extreme performance setup that should run on a maximum amount of users.
Edit: The VXGI pdf at the root of the engine build has actually been updated with the new vxgi format and lots of information.
EDIT: nvm, instructions seems to be included.
Hey thanks for answer. IT would be really nice to get it working.
Ie. On elemental demo scene, default settings voxelization takes about 8.88ms on GeForce 1080 TI (enabled Diffuse and AO pass). And that scene is mostly static. I gues trade off for much faster voxelization (but with less quality due to less often updates), would be acceptable especially for diffuse and AO.
But it is so nice that this tech is still being worked on.
Those settings are most closely matched with Quality = 0 (which doesn’t mean off).
Just for reference, here’s the code that translates the new-style parameters (Quality and Sampling Rate) to the old-style number of cones and angle.
float quality = saturate(params.quality); const float minAngle = 15.f; const float maxAngle = 60.f; float coneAngle = (minAngle - maxAngle) * quality + maxAngle; int numCones = int(clamp(directionalSamplingRate / (1.f - cosf(deg2rad(coneAngle * 0.5f))), 4, 128));
The Elemental scene perf appears to be CPU limited just because of its mesh count and the thickness of UE rendering code. I would try to carefully filter the meshes and only voxelize those which matter.
I’ve asked one of our technical artists to try VXAL, and here’s what he came up with. Only two area lights with shadows.
Exactly what i was looking for, thanks Alexey. VXAL is truly looking amazing.
Hi @Alexey.Panteleev, Just dropping by to say this is amazing! So much control over things and the first results look absolutely gorgeous. You deserve a statue, street name, river and tons of hot girls and camel! Many thanks for this amazing new version
Yes, I’m using Development Editor. Launch from the shortcut. The assembly of the engine runs without errors and warnings. Everything is clear.
I thought Russian would be better explained in Russian.
Hey Alexey! Thank you so much for delivering VXGI 2.0 and VXAL! I’ve had an absolute blast playing with it so far, and it’s closer to perfect now than ever before! I do have a single recommendation that I believe would greatly enhance its’ capabilities!!
I’m no engineer like you, so please bear with me while I noob my way through this.
Setting up an Area Light has been dreamy, and I love how one can set it up with a material for the plane and a texture for the light emissive - this does pose a restriction, however, in that the light is ‘stuck’ I guess - in being that it’s static - it would be AAAAMMMAAAZZZIIINNNGGG if it was possible to apply the material itself as emissive to the light, where the material’s emissive value is output as the area light - OR - to be able to plug either a media texture or scene capture 2d into it as well. These features would MASSIVELY improve the flexibility of the area lights!!
I did manage to do this on my own using a veeeeery expensive (and therefore totally unreasonable) workaround - I built a blueprint that takes the output of a scene capture 2d texture, saves it overwriting a texture2d that’s applied to the area light - on every tick (and I did tests to see how it would look with various tick times) and yeah - it worked - but it’s a suuuuuper expensive process, obviously. So being able to apply a material or scene capture, or media texture - into the area light texture slot as the emissive - that’d be AMAZZZZIIIINNNNGGGGGGGG!!
Hello Alexey, also wanted to say great work and a huge thank you!! These are some amazing improvements
I do have one question though — where did the “r.VXGI.Range” console command go? It doesn’t seem to appear and I can’t find it in the PP settings either.
It’s been replaced with r.VXGI.VoxelSize.
Since the voxel volume can now have different dimensions along X, Y and Z axes, specifying a single “range” no longer makes sense.
Thank you for the feedback!
Using a dynamic texture should be possible to implement, I mean, VXGI can use any texture with mip-maps as area light texture. Whether it comes from an asset or is a render target, doesn’t really matter. I just need to figure out how to properly do that in the engine.
Just using a material’s emissive output without rendering it to a texture first is not possible. It has to be a texture.
Did few 4.19 merges:
https://github.com/0lento/UnrealEngi…4.19-Flow-VXGI contains UE 4.19.1 combined with Flow, HBAO+4 and VXGI2
and https://github.com/0lento/UnrealEngi…4.19-GameWorks contains UE 4.19.1 combined with Blast, Flow, HairWorks 1.4, HBAO+4, TXAA3 and VXGI2
Do note that TXAA 3 crashes the engine immediately on forward shading atm, so avoid that combo with this repo (you can always reset it back from projects Config/DefaultEngine.ini)
I didn’t merge Flex as I’m hoping Nvidia will update Flex integration into Flex 1.2 and UE 4.19. Latest Nvidia Flex branch is still at 4.17 so it would make sense that they’d update it but there’s no official word if they are working on this or not.