Quantcast
Viewing all articles
Browse latest Browse all 11560

Re: Computer specs for rendered animation

My experience with rendering in Pro e / creo has been poor.

 

One tip, when you are rendering , pull up your systems performance monitoring app and keep an eye on memory usage, it creeps up the longer the clip until it crashes around 95%.

 

Switch to 64 bit, add more memory, try to keep the clips short is what I found works best in Pro e/ Creo.

 

I find the rendering capacities in Pro e / creo is lacking behind industry standards.

 

We should have the option to send it to a rendering machine on a network to number crunch it.

 

I am currently using Daz3d to do mine. far more options, far better animation control, send to network capacities to render.

 

I export the componets from Pro e/ Creo as wavefront (obj) , import into hexagon, reassambly the model and than re export as wavefront (obj )   (pro e/Creo wavefront obj isn't right for daz3d for some reason ) .

 

I then import into Daz3d, far better animation control then in creo, support for external rendeing engines (luxrender, reality 2 ) so the job can be sent to a dedicated rendering PC or render farm to churn out.

 

I am in the middle of doing one now, I am planning to post a how too do it on here when I am done.


Viewing all articles
Browse latest Browse all 11560

Trending Articles