How do you get two or more different trees into one scene file?

 I can get many of the same tree in the same scene, but what do you
use other than - object {TREE} - for the other versions?

Silly question, I know, but it's doing my head in...  ;)

  ~Steve~

Post a reply to this message

"St." <dot### [at] dotcom> wrote in message news:40b4ce49$1@news.povray.org...
> How do you get two or more different trees into one scene file?
>
>  I can get many of the same tree in the same scene, but what do you
> use other than - object {TREE} - for the other versions?
>
> Silly question, I know, but it's doing my head in...  ;)

I've never actually tried, but it sounds like you'll need to change the
#declare in the different .inc files from TREE to TREE1, TREE2 etc etc.

Dave.

Post a reply to this message

St. nous apporta ses lumieres ainsi en ce 2004/05/26 13:04... :

>How do you get two or more different trees into one scene file?
>
> I can get many of the same tree in the same scene, but what do you
>use other than - object {TREE} - for the other versions?
>
>Silly question, I know, but it's doing my head in...  ;)
>
>  ~Steve~
>
>
>  
>
Just change the random seed before object{Tree} will give you variations 
on the tree model.
Changing the other #define will, possibly radicaly, change the tree 
generated.

Alain

Post a reply to this message

"St." <dot### [at] dotcom> wrote:
> How do you get two or more different trees into one scene file?
>
>  I can get many of the same tree in the same scene, but what do you
> use other than - object {TREE} - for the other versions?
>

Not sure what you're doing... your subject says Povtree, but your question
appears to be regarding the tomtree macro.

If you mean how do you call the macro on different tree files created by
Povtree, you have to include them just prior to declaring the tree, i.e.

#include "treefile#1"
#declare Tree1 = object {TREE}

#include "treefile#2"
#declare Tree2 = object {TREE}

#include "treefile#3"
#declare Tree3 = object {TREE}

Since the treefile calls the macro, TREE is redefined each time.

If you include all the treefiles at once, all you get is the last TREE
included.

RG

Post a reply to this message

If you use mesh trees from POV-Tree you just have to name
your files differently:

#include "tree1.inc"
object{TREE}

#include "tree2.inc"
object{TREE}

If you use blob trees generated by TOMTREE macro you can
declare that like this:

#include "tree1.inc"
#include "TOMTREE-1.5.inc"
object{TREE}

#include "tree2.inc"
#include "TOMTREE-1.5.inc"
object{TREE}

Hope this helps.

Gena.


St. wrote:
> How do you get two or more different trees into one scene file?
> 
>  I can get many of the same tree in the same scene, but what do you
> use other than - object {TREE} - for the other versions?
> 
> Silly question, I know, but it's doing my head in...  ;)
> 
>   ~Steve~
> 
>

Post a reply to this message

"Gena" <gen### [at] yahoocom> wrote in message
news:40b58e82$1@news.povray.org...
> Hope this helps.

     Thanks Gena, all is ok now. :)  By the way, I don't know if it's
my machine or a bug, but sometimes I can't edit any parameters - I'm
getting very small fields down the list that you can't type in. To get
around this, I have to close PovTree, and open it again.

  w98
  384 RAM

   Thought you'd like to know.

     ~Steve~

>
> Gena.

Post a reply to this message

"gonzo" <rgo### [at] lansetcom> wrote in message
news:web.40b50b1d7f476edaa0c272b50@news.povray.org...

> Since the treefile calls the macro, TREE is redefined each time.
>
> If you include all the treefiles at once, all you get is the last
TREE
> included.

   That's exactly what I was doing. Bah!  Thanks Ron.  :)

     ~Steve~

>
> RG
>

Post a reply to this message

>      Thanks Gena, all is ok now. :)  By the way, I don't know if it's
> my machine or a bug, but sometimes I can't edit any parameters - I'm
> getting very small fields down the list that you can't type in. To get
> around this, I have to close PovTree, and open it again.
> 
>   w98
>   384 RAM

I haven't seen this problem before. I'll check that.
It could happen if you resized POV-Tree window (made
it smaller). But maybe there is something else. Next
time when you face this problem try to increase
POV-Tree window.

Gena.

Post a reply to this message

"Gena" <gen### [at] yahoocom> wrote in message
news:40b6132c$1@news.povray.org...
> >      Thanks Gena, all is ok now. :)  By the way, I don't know if
it's
> > my machine or a bug, but sometimes I can't edit any parameters -
I'm
> > getting very small fields down the list that you can't type in. To
get
> > around this, I have to close PovTree, and open it again.
> >
> >   w98
> >   384 RAM
>
> I haven't seen this problem before. I'll check that.
> It could happen if you resized POV-Tree window (made
> it smaller). But maybe there is something else. Next
> time when you face this problem try to increase
> POV-Tree window.

    Hi Gena, yes, that's exactly what I did - reduce the window. The
problem I have with the PovTree window as it is at a resolution of
800x600, (without resizing the window), is that it continues down past
my task bar and I can't see 'preview', etc., and I either have to get
rid of the task bar, or reduce the PovTree window.

  Hope this is of some help.

    Regards,

   ~Steve~


>
> Gena.
>

Post a reply to this message

>     Hi Gena, yes, that's exactly what I did - reduce the window. The
> problem I have with the PovTree window as it is at a resolution of
> 800x600, (without resizing the window), is that it continues down past
> my task bar and I can't see 'preview', etc., and I either have to get
> rid of the task bar, or reduce the PovTree window.

Got it. I thought that everyone now uses at least 1024*768
resolution :) Now it's clear why text fields were collapsed
and I'm afraid that there is not so much I can do with it :)
Thanks for the info anyway.

Gena.

Post a reply to this message