Attached Link: http://www.fotografroger.com/test/error-image.jpg

Help me.

I use a PIII 800, 400 Mb internal memory, Geforce2 3d card, WinXP

Unfortunately this is unfixable. This only happens when you have lots of trees close together. I don't know why though.

This is a guess; It HAS to be because these B5 trees are made out of metaballs (or metasomething). Metaballs will affect each other WAY before their wireframes are actually touching one another. Just a theory. AgentSmith

Is a sound theroy Agent, trees are basically metaballs, and this prob never got fixed during beta testing:-(

The image is to dark for me to see the problem, ( unless that's the problem ) AgentSmith & Clay I've never had any trees attracted to one another because their made from metaballs.

Xygar, You can eliminate this problem by using 2-D planes. There is a very good tutorial for alpha planes in Vue. It can easily be applied to Bryce. Makes for smaller files, too.

Look to the middle left Stephen, there are chunks missing from the trunks of the trees.

Question are you using the 5.01 patch? I thought that fixed the bug.

Thanks Clay... I turned off my lamp for computer desk and now I see. Looks like missing or inverted polygons, never seen it before. Seems odd that it only seems to be happening at the haze or fog line.

More like un-attracted. Yeah, I had to save the pic and then bring it up and lighten it. It's the problem with middle parts of the tree trunk missing.

I've seen this happen before. If you check the scene from overhead, there is probably some overlap of the top parts of the tree. When you move them further apart, it will stop. At least it does for me. For some reason, from the instances I've seen, it usually does this on duplicated or replicated trees of about the same height. You can shrink a tree to a height lower than the branches of the tree and stick it under the branches of the larger tree without problem. It just seems to happen when any part of two trees overlap anywhere.

If you do - Ill remove - when your done lets see the render!!!

Thanks for all the help. Wow So many replys. I am very grateful! I will try the 5.01 path and see if it helps and read the tutorial about 2D planes. It is sad if it doesnt work because I wanted to make a spooky swamp and I wanted it to be really densed. (many trees if "densed" is not the right word) And it is ok to have fun with my picture just as long as you dont take credit for it. I will soon add some pictures in my gallery and of course this picture (if it works) will be there to. Thanks again all.

turning down the spatial optimalisation might help. it increases render-times, but polygon-loss will decrease. this problem with bits of geometry missing is also common when using lot's of metaballs and then it helps to turn down the spatial optimalisation.

"spatial optimalisation" Never heard of that before, what is it. As for the trees I've never had this problem and as you know I've made a few scenes with lots of trees tightly packed together. Strange things going bump in the night with Bryce 5. Does anyone know if the program is actually haunted? Catlin

I don't believe 5.01 fixes this. I have noticed it in some of my tree'd works and the only thing to help is repositioning. If someone else can find a way around this, PLEASE let me know!

Xygar, I've noticed some other people will render parts of their scenes and then combine them all in a program like photoshop. If the other things don't work, you might try rendering a few trees at a time, export the pictures, and combine them elsewhere. I think this picture will look great when you get it finished. Lin

Hey xygar, do you know what type of tree you are using there? This may sound silly, but perhaps some trees are more apt to mess up like this than others, or to a higher degree because of their geomtry. This might explain why some people run into this problem, and others don't; they're using different trees. Stranger things have happened in Bryce. AgentSmith

Thanks tjohn, so that's what it is. I mostly render scenes with clustered checked, funny how you can use a thing and never acknowledge it's name. No wonder all my school report cards always said ...... "daydreams too much".

"daydreams too much" I have heard that about me very often when I was younger. I think daydreaming is normally a good thing.

So do I Raraz I think it means we have creative minds. It's just too bad teachers generally don't recognise this as fact. Sad really. :( Catlin

Hmm... I never got "daydreams" too much, but I remember one teacher marking down a picture I drew because it wasn't realistic enough, then the next year a different teacher admiring a different student's creatively colored whale, while mine was a typical looking whale. I think this where I started losing respect for teachers. Lin

I lost that respect when I couldn't get the teachers to understand how an internal combustion engine worked. I was eight years old and found it easy to understand they where waaay older and didn't understand. That's when I first realised that I don't need teachers that much in order to learn stuff.

At school the careers officer said I should take up nursing because I have diabetes and paid no attention to the fact that I had high grades in art and had said on the form I filled in that that's what I wanted to study when I left school. I think I lost respect for my teachers, or most of them, by the age of 14 mainly because of their stupid assumptions about people and their lust for control. Had a bad time at school, can you tell. :) Catlin

Rayraz, I think I can top that. My teacher, when I was about 6 or 7 insisted that I had spelled my sister's name wrong. Her name is Jeanna (like a kid would make that up) but the teacher insisted it was wrong. Catlin, I took one of those career type tests which said I would make a good bartender. Did anyone explain to you why having diabetes would make you a good nurse? Why not a doctor? Is there something about the nursing profession they don't tell the rest of us? I learn much more quickly if someone explains the whatever to me. Unfortunately, too many people are fond of the 'discovery' method of teaching. I usually end up discovering I'm very angry at the teacher. Ten minutes of 'do this, this and this and this is why you do it' is a lot more effective for me. Works well when I have to teach someone else too. Lin

The teacher told you that you spelled the name wrong?! Names can be written in so many ways that you can't ever tell someone that the name isn't correct according to the spelling rules. That would mean half the people living on this planet write their names wrong! It's just like in nurseryschool. That's something I'll never forget. We had to give the names of objects on pictures and I told the teacher that the picture showed a sunflower. The teacher told me I was wrong. I was supposed to say it was just a flower. But because I had learned what a sunflower looked like just a few hours ago I knew I was right. The whole thing always amazed me ever since 8) The math teacher I have now is one of the few teachers I'd call really good.

How they messed with our little minds! :) Glad you like your math teacher. One of my math teachers also coached softball. I don't remember much of the math I learned in that class, but I heard a lot about softball. Fortunately I had a decent geometry teacher so my math skills aren't a total write off. :) Lin

With math using the knowledge is the hardest thing. Understanding it is easy for me, but figuring it out myself is hard. But that can be fun too. Now if only I get a reasonable grade next time. My last one was a 3.6 (out of 10) and when I redid it I got a 3.3! Luckily the best one counts. If I mess up again it can't be because of the teacher. He is realy helping me out and I'm trying real hard now myself. I still make lots of errors, but if I find that out now I won't do it wrong when I have my examinations. I've never been really good at softball, but this year I've made a bit of progress, so it's still fun. I've got to learn how to hit the ball right every time. If I hit the ball right it goes really far, but I often hit it wrong.