Sun, Feb 16, 6:31 PM CST

Renderosity Forums / Carrara



Welcome to the Carrara Forum

Forum Coordinators: Kalypso

Carrara F.A.Q (Last Updated: 2025 Feb 13 6:48 pm)

 

Visit the Carrara Gallery here.

Carrara Free Stuff here.

 
Visit the Renderosity MarketPlace - Your source for digital art content!
 

 



Subject: metropolis


brycetech ( ) posted Fri, 23 February 2007 at 5:32 PM · edited Mon, 22 July 2024 at 4:52 PM

file_369843.jpg

some images of the future

:)
BT


brycetech ( ) posted Fri, 23 February 2007 at 5:32 PM

file_369844.jpg


brycetech ( ) posted Fri, 23 February 2007 at 5:32 PM

file_369845.jpg


brycetech ( ) posted Fri, 23 February 2007 at 5:32 PM

file_369846.jpg


ominousplay ( ) posted Fri, 23 February 2007 at 7:10 PM

Man, I hope not.

Never Give Up!


Kixum ( ) posted Fri, 23 February 2007 at 9:25 PM

Very nice.

A power render of amazing proportions!

-Kix


danamo ( ) posted Sat, 24 February 2007 at 1:21 AM

Very nicely done. I would hate to live under the pall of that noxious haze.


brycetech ( ) posted Sat, 24 February 2007 at 2:18 PM

carrara crashed
sigh

so I restarted it and vow not to touch the computer for any reason til its done.  It got caught in an infinite loop...one of the processors went to 100% and the render "box" wouldn't finish.  When I tried to restart it from the last finished frame, the "haze" didnt look the same and it was obvious where the first render had been going and changed to the second pass, so I had to start ALL over.

sigh again
Ive tried "creating real instances" (big mistake)..each render went from 36 minutes to 5+ hours each.

so the replicator is the only way to do it.  I guess the time its taking between each render pass is to map the textures to each object.

so, until next weekend (or so), I wont have any more images of this to show.

BT


danamo ( ) posted Sat, 24 February 2007 at 3:06 PM

ARRGHH! Sorry to hear that!


KevinSparling ( ) posted Sun, 25 February 2007 at 9:14 AM

I notice my processor goes to 100% alot when rendering. Is there anyway to avoid this? or is it even a bad thing? I have AMD 64 x2 dual core.


brycetech ( ) posted Sun, 25 February 2007 at 10:48 AM

100% is ok
btw, it happened again...exact same frame, exact same location.  Its where the camera crosses the infinite plane of the clouds...ie, they are on the same plane (camera and cloud).  Im wondering if the math for that portion is not causing a problem (two infinites in the same place)

I was going to let it run to see if it would eventually either error out or go on, but my power went out about 10 minutes after it hit that spot.  Sooooo..back to the drawing board (again)

sigh

BT


brycetech ( ) posted Sun, 25 February 2007 at 5:02 PM

well
it simply will not render past that frame.  There is a line of white at the top of the frame above the sky. It stops there and will not progress any further.  The rest of the image renders, but one cpu hangs there on that line so it never finishes.

As an attempt to work around this, Im going to make the camera point downwards faster so as to avoid that line of "infinity", therefore always pointing at the replicated city block objects.  

Carrara is max-ing out the cpu, then it runs about 5 minutes then it passes it to another cpu and then that one will run..and so on and so forth.

While making this tho I have a suggestion to improve the replicator.  That being, a set degree of rotation for a replicated object.  The problem with city blocks is that eventually you see a pattern.  If the replicator would allow you to set 90 degree increments as a rotate factor that would be assigned randomly to each block, it would align properly and no pattern would exist as each one would be randomly rotated between 90, 180, 270 and 0 degrees.

:)
back to the drawing...err..render board.

BT


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.