ue5-style-guide icon indicating copy to clipboard operation
ue5-style-guide copied to clipboard

Niagara Naming Conventions and Best Practices

Open Allar opened this issue 4 years ago • 3 comments
trafficstars

I haven't been able to dive real deep into Niagara pipelines, so far all my current game dev experience has been on teams that have still been figuring it out.

I'm looking for any and all insight on how to manage, name, and really just best practices of all kinds. Literally anything useful in Niagara authoring that is helpful to know and conform to.

Please discuss here, on the Gamemakin Discord at https://discord.gg/Kdq5dth , or just create pull requests with your contributions. If possible, please include ways you've seen these in practice, pros and cons, possible alternates. Feel free to contact me through other secure means if you would like to talk behind an NDA or encryption.

Allar avatar Jul 08 '21 09:07 Allar

Got one right off the bat - never ever use spaces in Niagara variable or module names, you gonna have a bad time when you write a custom HLSL code/expression and try to reference that.

dunenkoff avatar Jul 08 '21 10:07 dunenkoff

Got one right off the bat - never ever use spaces in Niagara variable or module names, you gonna have a bad time when you write a custom HLSL code/expression and try to reference that.

b1f341c

Allar avatar Jul 08 '21 11:07 Allar

We use typical prefix. NS_ for Niagara system NE_ for Niagara emitter.

It works great.

Edit : More detailed answer here : https://github.com/Allar/ue5-style-guide/issues/31#issuecomment-876753902

lucastucious avatar Jul 08 '21 20:07 lucastucious