Hey everyone, especially Xander:
I've been trying to use the RIB export plugin to make a dandelion, but
for some reason, the cones have not been exporting correctly. This is
not a cone, but rather some sort of generic hyperboloid:
Hyperboloid 1 0 0 0 0 0 360
that basically looks like a disk. This is what is exported when I
attempt to export a cone thats not at the origin and is open.

Also, xander- seeing as Larry has fixed the DSO problems, it is
significantly easier to make procedural primitives(ie, SORs, Text, HF's,
SuperQ's, etc) that are all currently supported by the rendering plugin,
as well as the possibility of DSO textures. If you could support this
functionality, it'd increase the user group of moray significantly.

TIA,
Alex Magidow

--
You Know You've Been Raytracing Too Long When:
 You have ever said "I don't need no stinking modelers!!!"
Produced by Alex Magidow's Sig File Randomizer(YKYBRTTL jokes courtesy
of c.g.r.raytracing)

Post a reply to this message

Alex Magidow wrote:
> 
> Hey everyone, especially Xander:
> I've been trying to use the RIB export plugin to make a dandelion, but
> for some reason, the cones have not been exporting correctly. This is
> not a cone, but rather some sort of generic hyperboloid:
> Hyperboloid 1 0 0 0 0 0 360
> that basically looks like a disk. This is what is exported when I
> attempt to export a cone thats not at the origin and is open.

I noticed that the plugin on my HD is dated after the one on the web
page.  I uploaded it (now dated 15 May), so you should probably grab
that one.  I remember there were some problems with cylinders and cones
back then (especially closed ones) and I'm pretty sure they are fixed
now.

Note: There aren't any cones in a RIB file.  You can have a quadric
surface or polygons.  I chose the quadric route, as it will give the
smoothest result (depending on your RenderMan compliant renderer).  The
quadric that can be used is the Hyperboloid.  It should look like this:
  Hyperboloid 1 0 1 0 0 0 360

Note the "1" as the third argument.


> 
> Also, xander- seeing as Larry has fixed the DSO problems, it is
> significantly easier to make procedural primitives(ie, SORs, Text, HF's,
> SuperQ's, etc) that are all currently supported by the rendering plugin,
> as well as the possibility of DSO textures. If you could support this
> functionality, it'd increase the user group of moray significantly.

I agree - it's just a matter of a little time freeing up to get back to
being productive on it.

Xander

Post a reply to this message

Um, I just made a scene with 66 cones but replacing some sort of hyperboloid
with a:
Cone 1 1 360...The details on cones is in the ARMan, I'm pretty sure, but
don't quote me on it. Perhaps asking on the group might be helpful.

Also, when you export, could you add an option to change the coordinate system
to Y = up? It really messes up some of my shaders(the sky's horizon ended up
being on the far right...oops....

Thank you very much,
Alex Magidow

--
You Know You've Been Raytracing Too Long When:
 You have ever said "I don't need no stinking modelers!!!"
Produced by Alex Magidow's Sig File Randomizer(YKYBRTTL jokes courtesy of
c.g.r.raytracing)

Post a reply to this message

Alex Magidow wrote:
> 
> Um, I just made a scene with 66 cones but replacing some sort of hyperboloid
> with a:
> Cone 1 1 360...The details on cones is in the ARMan, I'm pretty sure, but
> don't quote me on it. Perhaps asking on the group might be helpful.

Maybe I should have been more specific - you get cones, but they have to
have a pointy end.  No frustrums.  So, I went the more general route.

> 
> Also, when you export, could you add an option to change the coordinate system
> to Y = up? It really messes up some of my shaders(the sky's horizon ended up
> being on the far right...oops....

To be honest, that would introduce several lines of code into every
place that a prim or texture is exported.  In addition, any transforms
that have to be exported might require some work.  That means
maintaining plenty of code for the sole purpose of toggling output
coordinates.  Just doesn't seem like it's worth the effort.

You either have to design with Y = up (just change the meaning of
front/side/top and rotate your camera 90 degrees...), or modify your
shaders.  Moray doesn't preclude you from designing that way - it just
defaults to a certain orientation.

Xander

Post a reply to this message

Alexander Enzmann <xan### [at] mitreorg> wrote:
: To be honest, that would introduce several lines of code into every
: place that a prim or texture is exported.

  Now we see the importance of modular programming... :)

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message