And if anyone dares to say that Cinema renders fast again, ill kick that persons butt! :)
It cracked at the bottom scene, and refused to render it, so ive had to render two different scenes, and piece them together. Im all thrilled, since i still have a few more things to add. :)

Hehe, I bet those models are beginning to get big now, or have cinema4d some magic way of ceeping it small? ;). The details are looking avesome. And me are NOT getting bored :O)

Actually, i find it amusing(well...), that Bryce can render scenes over a Gig without problem, but a freakin 81 Mb scene in Cinema is impossible. I also might add that this was the image size it refused to render. I need one 5000 pixels high for the final render.

can I make a suggestion, make the duplicate sections, instances using the duplicate function. are the upper and lower hexagon sections mirrors. The bottom ones do not need to be greeblied/textured. The cubes at the axial core, are they single projected through or duplicates? cinema does render faster, unless we start asking it to do either something arcane or beyond the capacity of the RAM in the machine ...and what are your render settings? drop me a line Richard

what are you using for a light setup? Soft shadows? depending on your shadow map settings you could do this. Try with hard. Diffuse doesn't happen in space at least not with sunlight, depending on the reflective surface it can but this should not be a major scenic concewrns in a space shot.

I have scenes get well past that amount so it is not the image size. Did you use soft shadows with a central radial? A radial requires 6 shadow maps and depending on the resolution you asked for in conjunction with your model size could cause your issues.

You know youre asking me technical questions right? Im an idiot when it comes to that. :) Well, i use soft shadows, but its giving me the look i want, so i dont want to change that. 3 omnis, with only one of them casting shadows, and stochastic radiosity, which i think is the big problem. Apart from the radiosity, its all default settings. But ive divided these into two scenes, so at least it does render them now. Im going to use postwork and compositioning for the rest. Im not exactly happy about making changes in the models now, since there are some changes between the upper and bottom part of the arrays, and most of the stuff is finished. Whats left to add, is a couple of docking arms, lights/textures and a few ships.

Message edited on: 10/30/2004 17:39

The thing is, if it can't be seen in any way it just adds to the model size and render complexity. You're not an idiot, (unless idiots are extremely talented and brilliant IMHO - grin) Not sure if the radiosity has any real value in the modelling stage and depending on the samples, etc, stocastic can really slow you down. If you want to e-mail me a screen cap of your render steeings I may be able to help optimize them. I have played a bit with radiosity and GI.

Asking Rochr technical questions...teehee... The man is the Pinball Wizard of 3D...freakin CRAZY. Barely knows how it works, but he can make it do whatever the heck he wants. Wow. What amazes me is that almost everything in this image is a primitive, or a just barely modified primitive...'cept for the swoopy bridge deals...Wow. There are looking awesome, Rochr...Seriously, if you don't win I might have to get in my big old Buick and drive to wherever those judges live... To have tea and crumpets, of course... Yes...crumpets of DOOM!!! Muahaha!

Thanx man. If fair game cant do it, try violence. :D Incarnadine, Thats why there are only walls on the visible sides. :) The radiosity helps, at least me, to see the shape of the models a lot better, since Cinema by default make the edges look kinda smooth. Also, this is actually the lighting ill use for the final scene. The backdrop will be made in Photoshop.

Message edited on: 10/30/2004 18:03

very tasty! but at this level of detail I can see you having a big file unless you instance some of these repeated assy's. How many Mb RAM do you have?

Looks fantastic Rudy! I'm really looking forward to the completed pic.

Rudy, when this page was loaded, i scrolled down and shouted WOW so loud that my cat scared off into the tinyest corner of my home! A very cool job indeed. I dont know much about render sizes and pixelloads (or whatever has been talked about in the above posts ^^) but i can see this is starting to become an awsome project! CZ

Not bored here either - keep posting as many wips as you want :) Some of those "high end" render engines that do radiosity and things from what I've seen seem to generate and store a lot of data as they render... so as they render, they eat up more and more and more ram, whereas bryce doesn't seem to do that. I wonder if thats what c4d is doing... I know when I rendered something simple in Daz|studio (not that its a high end renderer, just a different one to bryce) it kept eating up ram as it went until it killed the program at about 40% rendered.

Thanx guys. :) Yeah, RAM is probably part of the problem as well. Right now, i have 512 MB RDRAM PC800. I dont want to buy more of these %##)@/ expensive things, because ill be building a new machine soon. I manage, just have to do some creative thinking to put everything together seamlessly. :)

That's why I work with 1 Gb and I do understand the price issue (same stuff!) I did a couple of tests last night regarding cinema's radfiosity techniques (standard vs stochastoc) using Robert the robot. 1152x864 Standard required 2 hr 39 min. Stochastic was not finished when I got up this morning (7 hr 15 min) I would still strongly recommend not using it in a space image especially at the final render size you want. Fake it.

marvellous i love seeing the modelling work, sometimes more than a finished image, desperately waiting the end result.