![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Very cool.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I took a quick look at this and was VERY impressed! I've tried to use the
tomtree macro, but because it would take (sometimes) hours to get a new
render based on any changes, I found myself only using the examples. This
is a GREAT way to get around that, and view changes very quickly, even
though it's not a full render.
For those who enjoy creating outdoor scenes, this is fantastic!
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Does it support UDO output? If not, this would be a killer feature.
Karl
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Karl Pelzer wrote:
> Does it support UDO output? If not, this would be a killer feature.
>
Why do you need it in POV-Tree?
Gena.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Gena Obukhov schrieb:
> Why do you need it in POV-Tree?
>
> Gena.
>
...just to import these brilliant trees into Moray. Or did I miss
something...??
Karl
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Very detailed tree can take a lot of memory after loading it to
Moray. I think you won't be able effectively manipulate by
such tree in Moray. I don't know details of Moray (never used it)
but if it doesn't use OpenGL any transformation will need a lot
of time.
It's very easy to add trees from POV-Tree to your scene because
it "grows" from <0, 0, 0> and occupies 1 unit box.
Anyway I don't plan to implement UDO export. If anybody is
interested in exporting files in different formats he/she can
add such functionality to POV-Tree when the source files
will be available (in a week or so).
Gena.
Karl Pelzer wrote:
> Gena Obukhov schrieb:
>
> > Why do you need it in POV-Tree?
> >
> > Gena.
> >
> ...just to import these brilliant trees into Moray. Or did I miss
> something...??
>
> Karl
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Wasn't it Karl Pelzer who wrote:
>Gena Obukhov schrieb:
>
>> Why do you need it in POV-Tree?
>>
>> Gena.
>>
>...just to import these brilliant trees into Moray. Or did I miss
>something...??
I'm not familiar with UDO or Moray, but I have written a little Perl
script that can convert the mesh files created by POV-Tree into OBJ
format, which can be used in a large number of modelling and rendering
systems. Does Moray read OBJ?
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Williams wrote:
>
> Wasn't it Karl Pelzer who wrote:
> >Gena Obukhov schrieb:
> >
> >> Why do you need it in POV-Tree?
> >>
> >> Gena.
> >>
> >...just to import these brilliant trees into Moray. Or did I miss
> >something...??
>
> I'm not familiar with UDO or Moray, but I have written a little Perl
> script that can convert the mesh files created by POV-Tree into OBJ
> format, which can be used in a large number of modelling and rendering
> systems. Does Moray read OBJ?
Moray does not read OBJ but 3DWin does and can export to UDO.
--
Ken Tyler
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Gena Obukhov" <obu### [at] mail com> wrote:
>
> Very detailed tree can take a lot of memory after loading it to
> Moray. I think you won't be able effectively manipulate by
> such tree in Moray. I don't know details of Moray (never used it)
> but if it doesn't use OpenGL any transformation will need a lot
> of time.
In fact, UDO files need not to represent your trees accurately. If fact,
good UDO file should provide just a very basic information about how your
model looks (or, if more exactly, what is its geometry, so that you would be
able to scale/rotate/locate it in the Moray properly). It is accompanying
INC files (containing actual SDL code) that contain the full model; UDO
files [often] contain just a rough approximation.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Vadim Sytnikov wrote:
>
>
> In fact, UDO files need not to represent your trees accurately. If fact,
> good UDO file should provide just a very basic information about how your
> model looks (or, if more exactly, what is its geometry, so that you would be
> able to scale/rotate/locate it in the Moray properly). It is accompanying
> INC files (containing actual SDL code) that contain the full model; UDO
> files [often] contain just a rough approximation.
>
>
>
Yup! That's the way it could work. I remember Johannes Hubert's "Tree
Designer" which supported UDO output.
@ Gena
How about a poll in the Moray groups?
http://news.povray.org/moray.win/
Maybe more Moray Users would be intereseted in UDO output.
Karl
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |