monomind Posted October 14, 2019 Share Posted October 14, 2019 (edited) Looks like VDB to spheres is working a bit different for me in V 17.5 The created spheres used to stay within the volume before but now it looks like some of them are exceeding the boundaries of the vdb. I've tried opening older files, they also work differently. Can anyone confirm this behavior, or if this is intentional or not? Not sure if a bug is going on on my end. V17.5.391 Edited October 14, 2019 by monomind Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 More obvious to see for a torus instead of a cube. I'm pretty sure this was not the behavior before. Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 Here is the houdini file, maybe someone can test and confirm. vdbfrompolygons_broken.hip Quote Link to comment Share on other sites More sharing options...
Andrea Posted October 14, 2019 Share Posted October 14, 2019 Same here in Houdini 17.5.293. I created the scene also from scratch and I get the same result, so it's not related just to your hip. Changing a little the parameters or decreasing the VDB resolution, helps. But seems random, I haven't noticed any correlation 1 Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 Created spheres used to stay in boundaries of the parent object before. I sadly don't have an older version of Houdini installed at the moment but maybe later today I can install and check - or maybe someone can do the same in an older version and check. Quote Link to comment Share on other sites More sharing options...
Andrea Posted October 14, 2019 Share Posted October 14, 2019 For sure this was also happening in Houdini 17 because of this I had to correct with a wrangle the pscale of the spheres after "VDB to spheres" 1 Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 (edited) How exactly do you correct it? If pscales are modified than the spheres don't fit any more. Edited October 14, 2019 by monomind Quote Link to comment Share on other sites More sharing options...
Andrea Posted October 14, 2019 Share Posted October 14, 2019 For each sphere I was looking at the distance to the surface of the geometry. If the pscale was bigger than the distance to the surface, then I set pscale to be this distance. Of course later I had to instance back again spheres to these points. 1 Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 Hm but then the distances between those resales points and everything else would fail (too much gap) - wouldn't make perfect fit any more am I wrong Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 Is this a bug? If it's here since V17 it can't be a bug I believe? Quote Link to comment Share on other sites More sharing options...
Andrea Posted October 14, 2019 Share Posted October 14, 2019 Doing what I mentioned before gives you a good collision geometry without extra stuff but of course the spheres are not perfectly close one to the other. I have always used this for getting correct collisions and ti was enough. To be honest I don't know if the spheres have ever been perfectly packed with no gaps Quote Link to comment Share on other sites More sharing options...
flcc Posted October 14, 2019 Share Posted October 14, 2019 (edited) As I have my old version always installed I test it. The most notable difference is on the large spheres. As on the old version the parameters are always activated I set it to have the same result as yours. Top to bottom H15, H16, H17 or 175 Edited October 14, 2019 by flcc Quote Link to comment Share on other sites More sharing options...
AslakKS Posted October 14, 2019 Share Posted October 14, 2019 Here is 17.5.350 Seems to be working correctly Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 Weird, so it's working correctly on 17.5.350 but not on the latest? Hm. Quote Link to comment Share on other sites More sharing options...
monomind Posted October 14, 2019 Author Share Posted October 14, 2019 Hm, is Houdini 17.5.350 a daily build? I can't find it in downloads page. @AslakKS Quote Link to comment Share on other sites More sharing options...
AslakKS Posted October 14, 2019 Share Posted October 14, 2019 Yeah, I believe it's a daily build. Quote Link to comment Share on other sites More sharing options...
monomind Posted October 15, 2019 Author Share Posted October 15, 2019 Wondering if it works correctly in any other stable 17.5 builds? Quote Link to comment Share on other sites More sharing options...
3dome Posted October 15, 2019 Share Posted October 15, 2019 just tried it in 17.5.173, default sized torus: vdbfrompolygons voxel size 0.1 works just fine but as soon as i lower it some spheres are not contained in the torus' shape anymore When I scale the torus up and leave the voxel size lower than 0.1 at some point it works again. Seems to be some sort of correlation/ratio that makes or breaks it Quote Link to comment Share on other sites More sharing options...
monomind Posted October 15, 2019 Author Share Posted October 15, 2019 (edited) @3dome yes, seems very random. What's more interesting to me is that it's not fixed since 17 Edited October 15, 2019 by monomind Quote Link to comment Share on other sites More sharing options...
jkunz07 Posted October 15, 2019 Share Posted October 15, 2019 This is an issue with the OpenVDB code being updated to 5.0, when I asked SideFX about it a while back they said they have let the OpenVDB team know about this issue. 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.