Houdini VAT stops rendering when used in Niagara System

Hi I’m following this tutorial by Houdini and rendered my VAT and mesh. It’s all working in engine if I place it in the world, but the moment I add it to a Niagara mesh component it stops. I read in another thread in this forum that I need to turn my Tangent Space to World Space node to Instance /Particle space to World space, but it still doesn’t work :confused:

Hello!

Yes this is an issue with different coordinate space. There is currently a way to do this which is setup in the Labs VAT export node. In this case, on export, you need to enable support instancing as well as exporting the Real-Time Data .Json file.

With both of these enabled and your export is finished, in your export folder there will be a data folder with this .Json file. Inside this text file there is parameters for the exact scene bounds for setting up instancing. At this point, all you need to do is inside the material instance for the VAT you need to enable the Boolean parameter “Support Legacy Parameters and Instancing”. After this is enabled you can copy and paste the specific bound parameters from the .Json file into the material instance, and it should just work.

First Pass: renders Geometry, Lookup Table Texture, and optionally the Real-Time Data JSON file / the Unity Material file.

EDIT : Here is what the .Json file looks like showing each bound max outputs.

Here is where you input these in the material instance

Note : The values are different in both pictures as I just did a screen shot of a random material instance. You need to make sure your .Json file bounds outputs are copied exactly the same into the material instance, or else you will get some really crazy artifacts and bad results.

Thank you it worked!! It’s a little bit off with the bounds like a tiny teeny off but maybe I did something in the export, I’ll get a new render and try again

Glad to hear!

Yeah Unreal will display rounded numbers in the material instance as well. If it looks good without artifacts after copying the values over, then it should be 1:1.

Of course artifacts could come from other things when exporting VAT, though.