 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Greetings,
Just downloaded Moray a couple of days ago. I'm using Rhino to model,
then I dump out the results to Moray for material assignment, scene
placement, etc. Rhino exports directly to .udo, and I have noted that
while the .udo file itself is of a reasonable size, an .inc file is also
produced which is usually enormous. It has not been unusual for it to
be 10-15 meg + for a single object!
While I'm not too concerned about filling up my hard drive, I'm
wondering if this is a normal result. I've recently become interested
in competing in the IRTC, if a single object is 10 or more meg, I can
visualize an entire scene utilizing over a gig of .inc files. This
would of course make uploading sources for the competion .... painful.
Any input??
Regards
J R
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
That is probably because your objects have a ton of triangles or polygons.
You might want to render such elaborate objects natively, in rhino, or
export them to a different modeler/renderer that supports nurbs(such as
BMRT), which should save a lot of size.
Johannes Riechart wrote:
> Greetings,
>
> Just downloaded Moray a couple of days ago. I'm using Rhino to model,
> then I dump out the results to Moray for material assignment, scene
> placement, etc. Rhino exports directly to .udo, and I have noted that
> while the .udo file itself is of a reasonable size, an .inc file is also
> produced which is usually enormous. It has not been unusual for it to
> be 10-15 meg + for a single object!
>
> While I'm not too concerned about filling up my hard drive, I'm
> wondering if this is a normal result. I've recently become interested
> in competing in the IRTC, if a single object is 10 or more meg, I can
> visualize an entire scene utilizing over a gig of .inc files. This
> would of course make uploading sources for the competion .... painful.
>
> Any input??
>
> Regards
>
> J R
--
Given a lever long enough, one can move the world with little force
MJ Engh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alex,
Thanks for the tips. Problem is, as a renderer Rhino is not much use other
than for simple visualization. Not a slam, but modeling is the focus of that
program. And as for BMRT, I have looked at it, briefly. I began to read up
about things like coding shaders and compiling them and whatnot. Ouch.
Unfortunately Mr. Gates has me spoiled about such things Point and Click. Is
BMRT as linuxy-geeky as it looks? Don't get me wrong, linuxy-geeky would be
the preferred modus operandi, I just haven't reached that level of
enlightenment yet.
Alex Magidow wrote:
> That is probably because your objects have a ton of triangles or polygons.
> You might want to render such elaborate objects natively, in rhino, or
> export them to a different modeler/renderer that supports nurbs(such as
> BMRT), which should save a lot of size.
>
> Johannes Riechart wrote:
>
> > Greetings,
> >
> > Just downloaded Moray a couple of days ago. I'm using Rhino to model,
> > then I dump out the results to Moray for material assignment, scene
> > placement, etc. Rhino exports directly to .udo, and I have noted that
> > while the .udo file itself is of a reasonable size, an .inc file is also
> > produced which is usually enormous. It has not been unusual for it to
> > be 10-15 meg + for a single object!
> >
> > While I'm not too concerned about filling up my hard drive, I'm
> > wondering if this is a normal result. I've recently become interested
> > in competing in the IRTC, if a single object is 10 or more meg, I can
> > visualize an entire scene utilizing over a gig of .inc files. This
> > would of course make uploading sources for the competion .... painful.
> >
> > Any input??
> >
> > Regards
> >
> > J R
>
> --
> Given a lever long enough, one can move the world with little force
> MJ Engh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ya know, if you can't cope with those big files, you can always give me your copy
of Rhino<G>
Actually, I think there are several interfaces for use with BMRT- do a look
through the website(www.bmrt.org), and you ought to find something. The worst
part of BMRT is the need for shaders, which is what turned me off- and the
rendering times! Its REALLY slow.
Heres an interface:
http://www.wfmm.com/ribtickler/screenshots.html
and I think this is a shader helper:
http://www.butz.org/~butz/tkmatman/
Hope that helps.
Johannes Riechart wrote:
> Alex,
>
> Thanks for the tips. Problem is, as a renderer Rhino is not much use other
> than for simple visualization. Not a slam, but modeling is the focus of that
> program. And as for BMRT, I have looked at it, briefly. I began to read up
> about things like coding shaders and compiling them and whatnot. Ouch.
> Unfortunately Mr. Gates has me spoiled about such things Point and Click. Is
> BMRT as linuxy-geeky as it looks? Don't get me wrong, linuxy-geeky would be
> the preferred modus operandi, I just haven't reached that level of
> enlightenment yet.
>
> Alex Magidow wrote:
>
> > That is probably because your objects have a ton of triangles or polygons.
> > You might want to render such elaborate objects natively, in rhino, or
> > export them to a different modeler/renderer that supports nurbs(such as
> > BMRT), which should save a lot of size.
> >
> > Johannes Riechart wrote:
> >
> > > Greetings,
> > >
> > > Just downloaded Moray a couple of days ago. I'm using Rhino to model,
> > > then I dump out the results to Moray for material assignment, scene
> > > placement, etc. Rhino exports directly to .udo, and I have noted that
> > > while the .udo file itself is of a reasonable size, an .inc file is also
> > > produced which is usually enormous. It has not been unusual for it to
> > > be 10-15 meg + for a single object!
> > >
> > > While I'm not too concerned about filling up my hard drive, I'm
> > > wondering if this is a normal result. I've recently become interested
> > > in competing in the IRTC, if a single object is 10 or more meg, I can
> > > visualize an entire scene utilizing over a gig of .inc files. This
> > > would of course make uploading sources for the competion .... painful.
> > >
> > > Any input??
> > >
> > > Regards
> > >
> > > J R
> >
> > --
> > Given a lever long enough, one can move the world with little force
> > MJ Engh
--
Given a lever long enough, one can move the world with little force
MJ Engh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alex Magidow wrote:
> Ya know, if you can't cope with those big files, you can always give me your copy
> of Rhino<G>
NEVER!!!
Thanks for the links, I will investigate further.
Regards,
JR
Post a reply to this message
Attachments:
Download 'us-ascii' (1 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Try playing with the poly settings use a lower poly count or try the
advanced settings under export. I know it's a simple answer but if you want
to use hi poly models that's the price you pay.
Nathan R. Zwalsh
nrz### [at] fatnet net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Johannes,
the size of the .inc file you export from Rhino depends on the mesh
settings
in Rhino. So it exports by default in a high quality/high polygon count,
you
should mesh your objects prior to export manually.
Then select your meshes and export to udo like usually.
In case you don't know how to do it: command is mesh, it opens the
polygon
mesh options with a slider, or go to detailed control. To play with the
first
parameter, max. angle, gives you scale independant control.
Rhino's help covers the possibilities.
Check out with the preview. Before you inspect the mesh in a shaded
view,
don't forget to hide the nurbs object. I personally set all variables to
zero and work
with the Max. distance, edge to surface only. This is scale dependant,
but
having the overall length of the object or the detailed section,
prediction
of
poly count works good.
For accurate meshing, Any megs may be, but a nice thing is, zipped, the
.inc files fold down to around 7-15%.
For example, I have a 68 meg inc file here, that's zipped 7 meg,
another,
32 meg to 2.4 meg.
You should plan out on your scene to mesh the smaller objects on less
detail
to keep it workable.
smb
Johannes Riechart wrote:
> Greetings,
>
> Just downloaded Moray a couple of days ago. I'm using Rhino to model,
> then I dump out the results to Moray for material assignment, scene
> placement, etc. Rhino exports directly to .udo, and I have noted that
> while the .udo file itself is of a reasonable size, an .inc file is also
> produced which is usually enormous. It has not been unusual for it to
> be 10-15 meg + for a single object!
>
> While I'm not too concerned about filling up my hard drive, I'm
> wondering if this is a normal result. I've recently become interested
> in competing in the IRTC, if a single object is 10 or more meg, I can
> visualize an entire scene utilizing over a gig of .inc files. This
> would of course make uploading sources for the competion .... painful.
>
> Any input??
>
> Regards
>
> J R
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Johannes Riechart wrote:
>
>
> Alex Magidow wrote:
>
>> Ya know, if you can't cope with those big files, you can always give
>> me your copy
>> of Rhino<G>
>
> NEVER!!!
>
> Thanks for the links, I will investigate further.
>
> Regards,
> JR
ROFL!!!!
Post a reply to this message
Attachments:
Download 'us-ascii' (1 KB)
|
|
| |
| |
|
|
|
|
| |
|
|
