FXCore
FXCore
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Houdini 16 geometry not backwards compatible? March 5, 2017, 3:53 p.m.
Thanks for the link, I couldn't get google or the forum search to turn up anything on the subject.
The thread seems to be hip file related though and 15 -> 16. I can understand there being minor changes to point order as nodes have to change or we'd never have any progress haha but to break the bgeo format seems unusual.
If this issue is related I would expect that the alembic file would fail to read as well but for it actually works so I wonder what it is about the new 16 bgeo that breaks the 15.5 read.
edit - Didnt see that post till after posting -brbreadingawesome
okay cool! bummer that it can't be read in 15.5.480 though.. I don't think I can convince IT to update the farm haha.
We'll see I guess.
Thanks so much for the help guys.
The thread seems to be hip file related though and 15 -> 16. I can understand there being minor changes to point order as nodes have to change or we'd never have any progress haha but to break the bgeo format seems unusual.
If this issue is related I would expect that the alembic file would fail to read as well but for it actually works so I wonder what it is about the new 16 bgeo that breaks the 15.5 read.
edit - Didnt see that post till after posting -brbreadingawesome
okay cool! bummer that it can't be read in 15.5.480 though.. I don't think I can convince IT to update the farm haha.
We'll see I guess.
Thanks so much for the help guys.
Houdini 16 geometry not backwards compatible? March 5, 2017, 3:26 p.m.
It seems geometry files written from Houdini 16 cannot be opened using Houdini 15.5+
I am currently deving some geometry using houdini 16 because the tools I need are not available in 15. Our farm cannot be updated due to current production and so I am attempting to output the base layer of the effect as bgeo files so that I can do the simulation work and rendering in 15.
Houdini 16 can read the bgeo files just fine. However, Houdini 15.5.480 returns an error saying the files cannot be read. Bgeo.sc returns the same error. Alembic works but I'd rather not have to deal with a 2gb+ alembic monolith. My current work around is to import the alembic using 15 and unpack convert and rewrite the files to bgeo.sc that Houdini 15 can read. This just seems like a silly step, hoping there is a simpler way.
Has anyone had similar problems and/or seen any documentation about changes to the format?
Hoping this is just user error on my part >.<
I am currently deving some geometry using houdini 16 because the tools I need are not available in 15. Our farm cannot be updated due to current production and so I am attempting to output the base layer of the effect as bgeo files so that I can do the simulation work and rendering in 15.
Houdini 16 can read the bgeo files just fine. However, Houdini 15.5.480 returns an error saying the files cannot be read. Bgeo.sc returns the same error. Alembic works but I'd rather not have to deal with a 2gb+ alembic monolith. My current work around is to import the alembic using 15 and unpack convert and rewrite the files to bgeo.sc that Houdini 15 can read. This just seems like a silly step, hoping there is a simpler way.
Has anyone had similar problems and/or seen any documentation about changes to the format?
Hoping this is just user error on my part >.<
Constraint problem with deforming active and deforming static packed RBD's June 15, 2016, 3:38 p.m.
Down the rabbit hole we go.
I have two packed rbd objects and one static object for collision purposes.
Of the two rbd packed objects, one is set to static deforming and the other is set to active deforming.
Think of a shape shifting egg shell with a section of it that gets broken.
My goal is to constrain the AD to the SD using springs and or glue and then hit them with the static object breaking some of the constraints.
The problem is none of the constraints(No matter the type) travel with the objects as they deform unless I use set always and overwrite them each frame. If I don't, once the RBDs begin to move, springs get stretched to crazy lengths and become unstable, glue just sits in place and does nothing and hard constraints just explode.
I've had the best luck with springs so far. Overwriting them each frame seems to keep things together and apply forces in a somewhat predictable manner. However, overwriting them each frame makes trying to delete the constraints both in sops or a solver within dops seemingly impossible. The constriant solver manages to pick up the springs and attach them to their respective pieces no matter how or where I delete them.
Perhaps someone has set up something similar to this and found a work around to having to overwrite the springs each frame? Really stuck on this one.
Any help would be very much appreciated.
I have two packed rbd objects and one static object for collision purposes.
Of the two rbd packed objects, one is set to static deforming and the other is set to active deforming.
Think of a shape shifting egg shell with a section of it that gets broken.
My goal is to constrain the AD to the SD using springs and or glue and then hit them with the static object breaking some of the constraints.
The problem is none of the constraints(No matter the type) travel with the objects as they deform unless I use set always and overwrite them each frame. If I don't, once the RBDs begin to move, springs get stretched to crazy lengths and become unstable, glue just sits in place and does nothing and hard constraints just explode.
I've had the best luck with springs so far. Overwriting them each frame seems to keep things together and apply forces in a somewhat predictable manner. However, overwriting them each frame makes trying to delete the constraints both in sops or a solver within dops seemingly impossible. The constriant solver manages to pick up the springs and attach them to their respective pieces no matter how or where I delete them.
Perhaps someone has set up something similar to this and found a work around to having to overwrite the springs each frame? Really stuck on this one.
Any help would be very much appreciated.