Hey All,
Ok I think I found a bug in Houdini. I am getting a Data error that runs through the node chain in my network when I do booleans followed by PolyExtrudes. The corruption happens at render time back into the SOP level of nodes all the way down the chain. Making me having to ditch entire chains of modeling. Any suggestions for a quick fix?.
Cheers,
Nate Nesler
P.S. I have remodeled the same thing about 3 or 4 times now.
Data Corruption in SOPs along the Node Chain
3046 2 1- MatrixNAN
- Member
- 405 posts
- Joined: July 2005
- Offline
- keyframe
- Member
- 1529 posts
- Joined: July 2005
- Offline
Hey Nate,
I've encountered a similar situation under different circumstances. The polysplit sop made me cry on so many occassions.
I find that under heavy poly modelling conditions it is best to occassionaly cut off the procedural head in order to preserve the body. Errr, so to speak…
In other words, once you have reached a certain threshold of operations, ie: you've completed 20 or so poly modelling operations, write out the file to a geometry file (which you can easily do by right clicking on the sop -> Save geometry), then slap down (or put down if you prefer less agressive modelling) a file sop, pipe in the file you just wrote out, and then continue modelling. All *SHOULD* be well.
It's FAR from ideal, but you know… gotta do what you gotta do right?
This is all assuming of course, that you have no intention of animating things that far up the chain.
Hope this helps,
Cheers,
G
I've encountered a similar situation under different circumstances. The polysplit sop made me cry on so many occassions.
I find that under heavy poly modelling conditions it is best to occassionaly cut off the procedural head in order to preserve the body. Errr, so to speak…
In other words, once you have reached a certain threshold of operations, ie: you've completed 20 or so poly modelling operations, write out the file to a geometry file (which you can easily do by right clicking on the sop -> Save geometry), then slap down (or put down if you prefer less agressive modelling) a file sop, pipe in the file you just wrote out, and then continue modelling. All *SHOULD* be well.
It's FAR from ideal, but you know… gotta do what you gotta do right?
This is all assuming of course, that you have no intention of animating things that far up the chain.
Hope this helps,
Cheers,
G
- MatrixNAN
- Member
- 405 posts
- Joined: July 2005
- Offline
Hey Gene,
Thanks I will do that too. I also came up with an easier solution however it might not be as safe and concrete as your own. I found locking the nodes where I don't need to have the back input anymore works fine. Of course you can not use the network to power your animation below the lock point. Anyhow that stopped the whole corruption problem I had. I will do your suggestion too because man when that thing corrupts it nailed all my backup files right down the line. Its weird it did not do it until I hit render. I will have to report this to sidefx. They can probably reproduce the error without much difficulty. Thanks for your input. The funny thing is the model is not even heavy yet.
Cheers,
Nate Nesler
Thanks I will do that too. I also came up with an easier solution however it might not be as safe and concrete as your own. I found locking the nodes where I don't need to have the back input anymore works fine. Of course you can not use the network to power your animation below the lock point. Anyhow that stopped the whole corruption problem I had. I will do your suggestion too because man when that thing corrupts it nailed all my backup files right down the line. Its weird it did not do it until I hit render. I will have to report this to sidefx. They can probably reproduce the error without much difficulty. Thanks for your input. The funny thing is the model is not even heavy yet.
Cheers,
Nate Nesler
-
- Quick Links