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.
Hi @, Just dropping by to say 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 amazing new version
Hey ! 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 .
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 - 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 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 , 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.
Hello , 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.
[/QUOTE]
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.
Hey ! 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 .
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 - 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 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!!
[/QUOTE]
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.
Do note that TXAA 3 crashes the engine immediately on forward shading atm, so avoid that combo with 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 or not.
Btw, I did experience a crash on Flow if I brought it into VXGI sample level, my naive fix for that was: https://github//UnrealEngi…7662e7daf5e4e7 (included in previous posts repos). I didn’t make PR for as I wasn’t completely sure why was happening (development editor didn’t give much info and didn’t have time to make a debug build for the engine to dig in deeper), just noticed that it threw nullpointer on missing Actor.
People who have tried it feel like it might be slightly slower than the previous one. To properly test the perf difference though, one should run benchmarks on same scenes using same UE version and both VXGI 1 and 2 and also try to match the settings/visuals between them. It’s just that there’s no official integration for VXGI 1 on 4.19 so it makes it harder to make fair comparisons.
@. Thank you for quick job. But In version of the engine, there is a critical bug on Material. Changing on Material Instances not saving and reset on restart the engine. According to Epic, will be fixed on 4.19.2 (https://issues.unrealengine/issue/UE-57086) Do you have any plan for 4.19.2?
