#World Builder
2 messages in this thread
>> Rendering a complex scene at 752×480 is a time NightMare. <<
>Well, it seems slow with dense vegatation and lakes etc. It took 1.5 hours for
a 720×480 sample image, >with no anti-aliasing
This is my biggest gripe so far, Martin. I can't even think of doing animation
with rendering times like this, so I guess I'll just have still backgrounds
while my subjects move around <g>. I do like the way you can custom make the
scenery by drawing the lines — it seems very intuitive for me, and I was able
to make the Devil's Tower in about five minutes (and the rendering, with trees,
stones, etc. took about an hour!).
I'd be interested in any techniques you come up with to shorten rendering times
— I hate to have scenery without water or vegetation (it reminds me too much
of Nevada!).
> but we have that 30 day money-back guarantee thing from Digimation.
Gee, is that only for high-end multimedia moguls such as yourself, or do I have
that, too? (They never said anything about it). Not that I'm seriously
considering returning it, but it's always nice to know about options
(particularly if I just can't live with these long rendering times).
Mike,
>> I'd be interested in any techniques you come up with to shorten rendering
times — I hate to have scenery without water or vegetation (it reminds me too
much of Nevada!). <<
I'm trying to think of a way of speeding things up. The anti-aliasing is
absurdly slow (double, triple, quadrupling the render time) – they need to come
up with a faster way. 3ds does it efficiently, I don't know why Animatek can't.
Maybe render without anti-aliasing and then use a batch anti-aliasing routine –
does anyone know of one?
>> Gee, is that only for high-end multimedia moguls such as yourself, or do I
have that, too? (They never said anything about it). <<
No we're not a special case <g>. That's supposed to be standard Digimation
policy.