Inside Sabertooth
Learn how Sabertooth uses 3ds Max to create 3D interactive projects, including HBO Go’s Game of Thrones interactive experience
  • 1/3
You are here: Forum Home / Autodesk 3ds® Max® / Animation / Animated Sequence File Limitations?? Need help please
  RSS 2.0 ATOM  

Animated Sequence File Limitations?? Need help please
Rate this thread
 
63276
 
Permlink of this thread  
avatar
  • Ekon
  • Posted: 04 January 2012 10:08 AM
  • Total Posts: 9
  • Joined: 04 January 2012 09:39 AM

Hello.

I’m currently trying to run some animation clips using Max 2011. My scene is organized in containers, so that the file size is only as big as 32 MB. The total number of polys (containers loaded) is around 7 million. Most of the geometry is solved in proxies. My file opens and saves quite normal (fast).

My problem comes when I try to run a 300frames “Animated Sequence File” in 720x480 output to JPEG’s. The process takes a very long time even when the CPU / RAM usage is not quite high. Actually I haven’t yet completed the process because I always think something is wrong after some time. The frames are actually created, but Max gets not responsive and the machine slows down.

It’s hard to grasp that this is so, when I’m not really trying to render production; no GI, no reflections or glossies, etc.

My machine:
i7 2.8 GHz
8 GB DDR3 RAM
Nvidia Quadro FX 580

Thanks in advance.



Replies: 0
avatar
  • Location: West Midlands, England, UK
  • Total Posts: 14435
  • Joined: 06 August 2007 11:06 PM
  • Permlink of this post

I doubt the problem is with the image sequence, much more likely the scene itself. More information like which renderer, what settings, what type of lighting etc will help give folks a better idea od what may be the problem.

And do yourself a favour - never render to a lossy format like jpeg. Always use a lossless format (tga, tif, png).



Max 4.2 through 2013.
XP-64 (SP2)
NVidia 9800GTX-512 (Driver 266.58).
Core 2 Quad Q6600 2.4GHz, 8Gb Ram, DX9.0c.

Replies: 0
avatar
  • Samab
  • Posted: 04 January 2012 09:23 PM

A render at that resolution without a complex lighting and material setup should not be a big deal for an i7 machine.

The process takes a very long time

What do you call a very long time? It’s a fact of life that rendering takes time, some people have unrealistic expectations about how long things actually take. My scenes vary from taking 2 seconds to 2 hours per frame to render depending on complexity and type of render. Some wait several hours for a single frame.



Replies: 2
/img/forum/dark/default_avatar.png

Thanks for the reply Samab and Steve. I think that viewport preview, which is what I’m calling Animated Sequence File as it is in Max should be really fast because there are not a lot of calculations to do. More than 30min for 300 frames at the mentioned resolution seems like a lot to me. And the Max hanging issue afterwards is also a red flag. This must be the heaviest scene I’ve done, so maybe that’s why I can’t identify the problem(s) myself.

I’m using Vray for production, but this is not a Vray related problem since all I’m doing now is viewport previews. I read about Quicksilver but I don’t seem to find it here. Is it a feature that needs a separate install?

Thanks for the help guys.

Author: Ekon

Replied: 05 January 2012 02:33 AM  
/userdata/avatar/avatar_51065.jpg

Sorry, I misunderstood you, I thought it was a final production render to a sequence of files, not a “Make Preview” as we used to call it.
That is a bit slow, about 6 sec per frame on a preview, but it depends on the scene complexity, viewport settings and GPU. Nitrous is meant to be fast, but it lets you have all sorts of realistic setting that will slow you down.
Quicksilver is a hardware renderer in it’s self, which is included with Max as standard. You can choose it from Assign Renderer. Not sure how well it will work on a Vray scene, it’s more mr friendly. Though it is not what I would call a real production renderer, more a glorified preview. Not sure is it’s any faster than Nitrous, I don’t use either.
If I’m doing a preview, it’s with fast basic settings, to me that’s the point of a preview. If I’m doing a production render, it’s usually full-fat mental ray.

Author: Samab

Replied: 05 January 2012 03:02 AM  
avatar
  • Ekon
  • Posted: 05 January 2012 07:26 AM

Well, apparently one of the containers was causing the problem. It has a big bunch of plants as vray proxies and some heavy boulders. I suddenly could not open this file and the erratic behavior came back. So, I inherited the container in a fresh file, made local contents, deleted the container and re-saved, of course, turned the polycount on the boulders way down. So, either something was wrong with the file or the boulders were playing up.

I did more previews of the general scene with no problems; I hope that was it.

Thanks guys.



Replies: 0