Jump to content
Sign in to follow this  
DELTAadmin

Speeding up

Recommended Posts

Good morning, could anyone of u help me in this issue:

I am loosing speed, when the modeling progress requires more nodes to attach. Is there any trick on how to cook the nodes, or how to hybernate the nodes which doesn't require more work on themselves?

I've tryed saving geometry to disc, and reloading that into the network, or collapsing the nodes mentioned into a subnetwork, but after a point these can not help.

I work on a full figure, a statute, with much detail, It contains about 16000 vertices, but now the workflow is slowing.

Thanx for your help.

Share this post


Link to post
Share on other sites

Meanwhile I have found a would-be solution, I will experince with it.

1. Method: Lock the node above the present one, itt will cook everything and save that to this node.

2.Delete History saves all previous nodes into the now activated node.

Other advices?

Share this post


Link to post
Share on other sites

Hey there

Yeah, what you're doing is certainly one of the methods of doing it.

Personally I'm a fan of saving the geometry to disk and reading it in with a file SOP. This allows me to keep my network just in case.. (in case of what I'm not sure, but you never know :P)

As long as your network isn't being displayed in any way (templates, footprints) or being referenced by anything else then it shouldn't cook and shouldn't slow things down too much.

Cheers

Marc

Share this post


Link to post
Share on other sites

Thanx for the reply, Locking the node above the present one seems to be the best method, coupled with collapsing into subnetworks, the experimentation'd showed it.

Share this post


Link to post
Share on other sites

another thing i thought of is that if you are commonly hitting the render button to see your model real quick in mplay, then you might notice some slowdowns. I *think* mplay saves your images to ram, so if you have a bunch of things rendered without closing it, then you might have all those images sitting and taking up ram.

it's unlikely that this is it and hard locking or exporting\reimporting is your best option, but i thought i'd mention it.

Share this post


Link to post
Share on other sites

Locking a SOP does require Houdini to store a copy of the geometry though so if you have multiple sops in a chain, make sure only one of them is locked.

Share this post


Link to post
Share on other sites

Yeah, saving out geometry is pretty flexible. I keep the name of the saved .bgeo object the same as the current file so I can remember which particular .hipnc it belonged to. So if I'm working on Mymodel56.hipnc, I'd save the geometry as Mymodel56.bgeo. Then later when you're up to Mymodel89.hipnc and the network is getting too big you'd save again as Mymodel89.bgeo...you get the picture. This way you don't loose any steps and you could string together all of the SOPs from the seperate networks to get one complete network, (assuming you have enough RAM).

For example you'd open up Mymodel56.hipnc, then open another Houdini session with Mymodel89.hipnc and copy/paste all the SOPs from that file and attach them to the network in Mymodel56.hipnc. Now you have the whole thing from the first polygon to the finished model, great for educational purposes, or just to make yourself feel special :D

Share this post


Link to post
Share on other sites

Don't lock any paint, sculpt or edit SOPs. You will loose all your painting or editing changes when you unlock them. They will revert back to when you just put them down.

If your SOP chain consists of nothing but paints, sculpts or edits, then insert a null SOP and lock that.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×