yup i forgot to mention that i also mainly dont render in real anymore.. the
renderer is just plain too slow and the quality compared to renderman
compatible renderers is bad.. i mean for renderman compatible renderer
displacement is just a piece of cake while real nearly dies and still has no
comparable displacement resolution.. and even worse, the motion blur via
brute force method of rs is also not realy usefull for broadcast media since
you need atleast 16 timesamples which makes rendertimes go boom. and just
like you mentioned the ram consumption is terrific.
regarding uv editing: create a new uvset viewmodel and drop it to the
uveditor.. close it and reopen.. everything should work then.. its just that
rs confuses uv view models with normal view models sometimes causing strange
things to happen.
Gunnar
----- Original Message -----
From: "studio" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, April 11, 2008 11:43 AM
Subject: Re: Can We Export RS3D Camera Data ?
Sounded good , but tried it with 300K poly and got the same
saddened result at rendertime (see attached) . The plan was a
tutorial to show - import .DEM , UV map , render .
I forgot to mention that I can do some things very easily ,
such as stretch/bend/move the 300K poly mesh .
However , it won't render .
Trips into the UV Editor are trips into hell .
I'm sure these kinds of things can be resolved , as Arjo
suggested , by some simple coding techniques .
Maybe I'll put away this tutorial until then .
RS3D seems sometimes like a Ferrari , sometimes a truck .
bye for now
garry
