This is probably not the reason for it but I do have to ask for my own knowledge. I’m primarily a C# programmer, so the dot behind the 0, is that a special syntax for something?
In other news, I’ve done a bit of digging and most of the time when this issue occurs there’s a data mismatch somewhere.
This is definitely a bug then. This has been a recurring bug that only shows itself during builds. I was looking through the issue tracker and noticed this has been an issue with certain parameter changing with Niagara systems for a while on and off.
Just an example (this one recent 5.0EA with Vector2 param changes)
Another from 2019 for bools
Unfortunately I don’t have any workarounds for this one. So it looks like we’re going to have to make a bug report.
I recently fixed it by deleting the check(Offset != INDEX_NONE); from engine code… Kind of “Do as I say, not as I do” situation, since it shouldn’t be fixed this way.
Also, if you’re using a material parameter collection driven niagara parameter collection, make sure that you got all of your NPC params in MPC with matching types.