Hello SideFX!

Congratulations on the latest H22 release. I noticed in the user docs that the Dense Pyro solver seems to be getting deleted / depreciated with the following nodes being removed:

"Pyro Solver Dop... Smoke object DOP... Smoke Solver DOP... etc."

That means I need to redo my course - Pyro I - and update the other pyro courses accordingly. Pyro I revolves around the original dense pyro shader workflow for new users.

From my understanding, the dense pyro solver was also the primary solver that used OpenCL. So, with this depreciation, which solver is going to be primary option to use with GPU acceleration? Sparse isn't compatible at the moment. And, from what I can tell, that leaves the minimal solver and COPs as the other options.

More broadly, I can see there being much new user confusion as to how to approach pyro and dops in general. We have simulations happening in SOPs. We have it happening in DOPs. And now we have it happening in COPs. Although I understand they have similar ingredients via the source volumes... and that pyro, on a fundamental level is mostly consistent in how it works in general... looking at it from a new user's standpoint is a bit of a problem because there isn't a clear and consistent pathway to approaching pyro simulations at the moment. Many ideas have happened over the years, and it's all scattered around the program at the moment.

So where exactly are you guys going with things? I'll sometimes throw in some custom microsolvers with DOPs, but that seems to be out the window with COPs. COPs is cool, but I'm not sure how those limitations compare to the dense OpenCL solver. Should a new user be leaning more into COPs because that's where you'll be migrating other solvers eventually? Should they be using the pre-packaged SOP node workflows? or should they be learning about good 'ol DOPs so that they have the ability to get more advanced with customized setups one day with a deeper understanding of how it all works? These are the sorts of questions I'm trying to consider before re-making a course.

Obviously, learning about all of these topics is ideal, but for the new user, it can become overwhelming. It's better to lean into one direction at first. And the direction I guide people in depends on where your team is heading with these ideas.


Thanks for any insight!

- Tyler

tbay312
From my understanding, the dense pyro solver was also the primary solver that used OpenCL. So, with this depreciation, which solver is going to be primary option to use with GPU acceleration? Sparse isn't compatible at the moment. And, from what I can tell, that leaves the minimal solver and COPs as the other options.

Pyro Solver SOP, while having 3 solve modes: Sparse, Dense (OCL on/off), Minimal, all of them are handled by Pyro Solver (Sparse) DOP

in other words Smoke Object (Sparse) and Smoke/Pyro Solver (Sparse) DOPs have Enable Sparse Solving checkbox, which when it's Off will be able to use OCL as it will solve in dense mode

so while it's a bit different from the old dense Pyro Solver DOP and some useful features may be missing, it's understandable that keeping 2 very similar dense solvers may seem redundant

tamte

tbay312
From my understanding, the dense pyro solver was also the primary solver that used OpenCL. So, with this depreciation, which solver is going to be primary option to use with GPU acceleration? Sparse isn't compatible at the moment. And, from what I can tell, that leaves the minimal solver and COPs as the other options.

Pyro Solver SOP, while having 3 solve modes: Sparse, Dense (OCL on/off), Minimal, all of them are handled by Pyro Solver (Sparse) DOP

in other words Smoke Object (Sparse) and Smoke/Pyro Solver (Sparse) DOPs have Enable Sparse Solving checkbox, which when it's Off will be able to use OCL as it will solve in dense mode

so while it's a bit different from the old dense Pyro Solver DOP and some useful features may be missing, it's understandable that keeping 2 very similar dense solvers may seem redundant

Ahh I see. So based on that, the dense mode + OpenCL is not being removed because it's just integrated into the Sparse solver?

that's correct, the older Smoke Object and Smoke/Pyro Solver DOPs that docs mention as deprecated are already ophidden in H22

but the available Smoke Object (Sparse) and Smoke/Pyro Solver (Sparse)can handle Sparse, Dense and Dense OCL solve (and Minimal if part of more elaborate setup such as the one used in Pyro Solver SOP wrapper )

Good to know! Thank you for pointing that out Tamte.