After dragging a Niagara system with a Grid3D fluid emitter into my viewport, I can’t see the red bounding box associated with said fluid emitter. “Draw Bounds” is set to “on”, however, flipping that toggle makes no difference in my viewport.
Steps to Reproduce
create a stock niagara particle system in UE 5.6 and add a grid3d niagara fluid emitter to said system. Drag that system into your viewport. While it is expected to see a red bounding box of your fluid system in the viewport, I currently do not. I can see it in the Niagara settings window, just not in the main viewport.
Hi,
Sorry about the delay, and thank you for the report. I am trying to reproduce the behavior you described, and I am indeed observing some oddities on “Grid3D_DrawBoundsOverlay v1.0”, which is used by “Grid3D_Gas_CONTROLS_*” family of emitters. However, in my tests, the bad rendering of the bounding box occurs both on the Niagara Editor Preview tab and on the Level Viewport. Also, the behavior seems to be correct on other Grid3D emitters, some of which use
“Grid3D_DrawBoundsOverlay v2.0” for the drawing, while others use “Grid_3D_Gas_UpdateEmitter v2.3” or “Grid3D_SetBounds v2.0” for the same purpose.
Can you please confirm on which Grid3D emitters exactly are you observing the bad behavior you described?
Also, if the emitter you are trying to use includes module “Grid3D_DrawBoundsOverlay v1.0”, a possible workaround might be to do one or both of the following upgrades:
A. Upgrade module “Grid3D_DrawBoundsOverlay” to v2.0, then set the “NumCellsX,Y,Z” inputs to the outputs from module “Grid3D_InitRT” with the same names
B. If the emitter also uses module “Grid3D_SetBounds”, you can upgrade it to v2.0, then set its “UnitToWorld” input to the output from module “Grid3D_CreateUnitToWorldTransform” with the same name. Also link its “Draw Bounds” input to “Emitter.Override.GridBoundsOverlay” (the same originally used by module “Grid3D_DrawBoundsOverlay”)
Some additional notes:
- You can check the version of a module that is currently in use by an emitter by selecting the module in the stack and looking on the header row of the Details Panel. If the module has a newer version available, you should see a “crossed-arrows” icon next to the trash can icon, activation checkbox and info icon. Hovering over that icon will show version information.
- Upgrading a module must be done on the original emitter (not a descendant). If you don’t want to make changes to the built-in emitter, you can make a copy of it first. Alternatively, you can right-click the header row of the in-use child emitter node, then click “Remove Parent Emitter”. This will detach your version of the emitter from its original hierarchy, allowing you to change it freely (but stopping any inheritance of changes made to ancestors).
I hope this is helpful. Please let me know the exact emitters that are behaving badly for you, and also if one of these workarounds help you overcome the issue.
Best regards,
Vitor