CKormann Posted January 11, 2021 Share Posted January 11, 2021 (edited) Hello, I'm trying out the new sparse pyro tools and really like them. However I am stuck at one point: The "pyrotrailsource" that feeds into the volume rasterize attribute node always produces these weird sources. It looks like the source is cut exactly in the middle in a low and high density field. The screenshot above is straight from the Shelf Tool "Aerial explosion". You can try it out yourself in H18.5. Sadly, the issue carries over into my custom explosions. This is how a customized source produces uncontrollable results in the combustion: Source: Result: Note that this issue is not caused by the shelf tool volume rasterize attribute. I created a fresh node: Same problem. I also checked all the particles outputted by the pyrotrailsource, they look fine and consistent. Any ideas would be much appreciated. Edited January 11, 2021 by CKormann Quote Link to comment Share on other sites More sharing options...
nuki Posted January 12, 2021 Share Posted January 12, 2021 (edited) #1 should just be a visualization problem. if you rasterize multiple attributes you'll have to tell houdini how to visualize them and it looks a lot like it's also visualizing some vector field (which visually only appears where values are above 0). Use a volumevisualization sop to define the visualization. And/Or a PyroPostProcess after your combustion sim. #2 can just be the viewport clamping your volume display. hit d in the viewport, navigate to the Texture tab and raise/untick the 3d texture 'limit resolution' parameter. Unless you're worried about the 'naked' flames in which case you can check the @flame value of your source there and adjust the smoke emit range in the pyro solver accordingly. Edited January 12, 2021 by nuki Quote Link to comment Share on other sites More sharing options...
evanrudefx Posted January 12, 2021 Share Posted January 12, 2021 (edited) did you try Normalize by Clamped Coverage setting on the volume rasterize attributes? that smooths it out. Also it doesn't visualize velocity very well if you are sourcing it. you can add a primitive node and select velocity and go to volume and adjust visualization then hide velocity. Edited January 12, 2021 by ejr32123 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.