Does anyone know why if I want to do a scene with alot of trees or plants or something of that sort, the more of them I get the slower my computer goes? I just tried a picture and when I got to 67 trees my computer finally froze lol I have 397 megs of ram too..

I just created a scene by multireplicating 67 trees and the file size was 2 meg. Are you creating 67 unique trees? If so, do you need to? With the sheer amount, individualizing trees may be unnescessary. Simply rotating a duplicate tree will fool the eye into believing it to be different from the one next to it. I've created very convincing jungle scenes using this method and the end product was only 7 meg.

Trees are fairly complex models, especially 67 of them...that would slow down ANY pc. Unless you are willing to wait the extra rendering time, try a work-around. If rotating duplicate trees works, then use that or there is rendering trees on 2d faces, or multimple rendering and then compositing, if you can do that. And, there is always add more ram, scenes with high poly counts need more ram to not freeze up. Any other work-arounds I'm forgetting? Agent Smith

Contact Me | Gallery | Freestuff | IMDB Credits | Personal Site
"I want to be what I was when I wanted to be what I am now"

all them leaves bring my pooter to its knees.. : ( not sure if it's just the textures, or the poly count from them

LOL well i usually replicate dont have the patience to create 67 individual trees the problem is up untill about tree number 10 im ok then after that it gets loooong i think by the time i coppied the last 6 trees it took 45 minutes just to copy.......

Do you have any problems with other applications? When you save the file, how large is it? If this is Demo5, then it is likely a problem with dumming down the demo. If it is full Bryce5, then it might be a hardware problem. Are you running on Mac or PC. If running on Mac, allocate as much RAM as possible to Bryce in the OS. If running on PC, your RAM may be having problems with your motherboard. Make sure your largest chip is in the primary slot and that it isn't PC133 when it should be PC100 and vice versus. It could also be that you have set to branch and leaf ratios too high. Running out of suggestions quickly...

Also is your nano-view window set to wireframe or render. If it's set to render this will slow down your comp as it renders after each move and copy. Also try setting the unselected trees to a lower wireframe resolution.

I use a Mac, so I do this- I'm not familiar with pcs: allocate max ram to program-use virtual memory (I bump 640 MB to 1000) ...also allow "show object as box" instead of wireframe to ease strain.(drawing that many wireframes can lock up your machine) use 2d trees in background when possible.

Another option is to use terrains to make tree like objects(there is a tutuorial for this on the bryce content cd) for the forground up close trees, and to break appart single tree models(un group them) and scatter the parts to make the forest. Textureing spheres and blocks to look like foliage in and trees in the far back look good to.

Tirjasdyn
http://michellejnorton.com

check you settings in byrce especially antialiasing. check defrag (it may be time to do that) check available disk space (getting low) only use 3d trees in the foreground make 2D objects (as suggested above by agent smith) from photos of trees. properly masked and if your camera doesn't move you can't easily tell. you can even rotate the images a few degrees, rescale and reverse them to give the illusion of more unique trees. also distant trees could be one large 2d object used as a background (mask could be a bear - solid??). also 67 trees? wow that's a lot. when you get done let's see what you get.