So we are trying to create some trees using the treez plugin and ran into a problem in the chor.
If you dropped a model into the chor more than once and it had hair on it, it gets connecting lines.

To make sure it was not the treez plugin, we brough in a sphere, applied hair to it and dropped it in the chor 2 times like so.....

[attachmentid=20456]

Pressing the 8 or 0 key (wireframe) causes these strange lines to join the 2 models, like so....
[attachmentid=20457]

Is it taboo to drop more than one copy of a model with hair in the chor?

If we save the model under a different name and (tree-1, tree-2 etc..) you can bring then in with out conflict.

A report has been filed, but if anyone knows of a work around........

David

It doesn't occur if you drag them in wireframe mode. But if you go into shaded mode, it seems to "spoil" the chor and it then occurs in wireframe mode too. You then have to open a new chor.
So, if you can work in wireframe it should be cool. I don't think they render though....it's just realtime...possibly related to error 39.

I rarely just stay in wire-frame or shaded mode.

My apprehension comes from putting too many of these in the chor. I "seemed" to really slow things down, once the 2nd copy (actually the first copy, 2nd instance of the model in the chor) was dropped in.

We did what you did (Ken) when you encountered error 39.

Thanks,
David

I think you found the work-around.

I have noticed this since ver 11.1. But not with all hairy models. I had thought it was the way the model had been created (with sweeper, or duplicate or copy paste stuff) - but it looks like you've just got a simple sphere there.

Nancy,
It is a work around, but seems strange (and adds unnecessarily to the project file size) to have too do it this way. We'll have at least 20 of the modeled trees in the chor. The combination of tree hair, panels and trees with hair will be pretty intense I think.

I don't remember importing more than one copy of anything with hair on it in V11 or 12.

Guess I could try to purchase a 3ds prop from *&^%@squid.

I will advise.
David

I've had this problem as well. For the most part it doesn't render, but sometimes it will. I've noticed when working on the TWO forest sets that changing the light direction will cause this anomally to render. I found that refresh does not fix the problem, but if I rotate the tree in question, then refresh the screen and render, it usually goes away, but not always. It's was driving me nuts.

Arrgg, reminds of a Pirate joke.

I reported it and it has been asigned, so hopefully there will be a resolution.
David