[Kevin Cook]

No, I’ve never heard of it but I’ll look into it. I’m fairly new to C4D (coming from a Lightwave background) so I’m sure there are things I could do better/differently to optimize the file. BTW…I do have a fair amount of objects that have a boolean/nurb/symmetry object etc. that I will eventually apply the “current state to object” to it, which will probably decrease the file size?

My main culprit is that every seat is a modeled object. For the most part, I used render instances which I’m assuming helps it render faster but it may not help in file size? And like I said, I will eventually break down my file into smaller segments of the stadium but I’m not ready to do that yet.

[Kevin Cook]

System specs:
Mac Pro
2 x 2.93 ghz quad core intel xeon
12 gigs of ram
ATI Radeon HD 4870

The file is remarkably easy to manuever, for how big it is. I just turn off a lot of objects when I’m working. It renders pretty fast, I rendered a 900 frame 360 camera move over the weekend and it took just a little bit over 24 hours. When I turn on global illum it looks awesome but it slows the renders down by about 4x so I won’t be using that too much, or at least until I can set up a network render farm.

[Kevin Cook]

Yeah, it’s a little crazy. I’m building a highly detailed sports stadium. My ultimate goal is to break it up into sections after it’s built but for now, it’s still a work in progress and I’d rather not break it up until it’s finished.