I have started to write a pluging for Moray with the Fullmoon scripting
plugin, but I'm having some difficulties.

First some background.
I'm useing Moray3.3a, Pov 3.5b8 icl and vc, Megapov0.7,and Pov3.1g but not
with isosurface of cource.
I have already emailed Andre de Leiradella about some questions on his
Fullmoon plugin.

I have posted some pictures in moray.binaries, that go with some of what i'm
talking about.
Part of my code output from Moray is:

// Pov_code002
#include "functions.inc"

// Isosurface001
#declare foo__ = function { 0 }
isosurface {
   function {
      sqrt(x^2 + y^2 + z^2) - 1.4*f_noise3d(x,y,z)
   }
   contained_by {box{-1,1} }
   threshold 0
   accuracy 0.01

material { Material1 }
scale <1,1,1>
rotate <0,0,0>
translate <0,0,0>
}

I know I can #include from elsewere in Moray, I only put that there for
something to output. How do I make sure that an object(Pov_code) is placed
at the top of a generated pov file? Sometimes when I create an object it
appears at the bottom of the code.
Can someone suggest a default function I can use when the isosurface object
is created? This is the first time i've started to look into the docs on
them and there's alot to read :-)
So far i've only coded down to accuracy for the isosurface output code, the
rest will follow as I have time.

About the pictures in moray.binaries.
The Pov_code object just passes on anything I put in the textbox, there is
no syntax error checking.
The Isosurface object picture is the rendered picture, not a preview. Only a
wireframe of the contained_by box is show, even in OpenGL only wireframe.
Fullmoon does not support solid drawing. At the moment the wireframe box is
hard coded as box{-1,1}.

Comments or suggestions welcome.

Stephen

--
My perception of reality may differ from yours.

Post a reply to this message

Hi Stephen, you recently wrote in moray.win:

> How do I make sure that an object(Pov_code) is placed at the 
> top of a generated pov file? 
Well, I can't tell you how to do it in FullMoon, but the Plugin SDK
has events that say where they are in the output process. The SDk
function is PrintEvent() and you get the possibility to write to the
POV file whenever these events occur. The events are:
MRY_NTC_BEGIN_POVEXPORT - the POV scene file for POV-Ray has just been
opened. 
MRY_NTC_BEGIN_POLYEXPORT - the PI scene file for Polyray has just been
opened. 
MRY_NTC_END_EXPORT - the scene file for the raytracer is about to be
closed. 
MRY_NTC_BEGIN_CAMERAS - the cameras are about to be written to the
scene file. 
MRY_NTC_END_CAMERAS - the cameras have just been written to the scene
file. 
MRY_NTC_BEGIN_LIGHTS - the lights are about to be written to the scene
file. 
MRY_NTC_END_LIGHTS - the lights have just been written to the scene
file. 
MRY_NTC_BEGIN_TEXTURES - the textures are about to be written to the
scene include file. 
MRY_NTC_END_TEXTURES - the cameras have just been written to the scene
include file. 
MRY_NTC_BEGIN_REFERENCED_OBJS - the referenced objects are about to be
written to the scene file. 
MRY_NTC_END_REFERENCED_OBJS - the referenced objects have just been
written to the scene file. 
MRY_NTC_BEGIN_OBJECTS - the objects are about to be written to the
scene file. 
MRY_NTC_END_OBJECTS - the objects have just been written to the scene
file. 

Hope that helps.

Regards,

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

Lutz Kretzschmar <lut### [at] stmuccom> wrote in message
news:jtn71u009fn1qopjm2i23ms2in7ha9njmh@4ax.com...
[snip]
> Well, I can't tell you how to do it in FullMoon, but the Plugin SDK
> has events that say where they are in the output process. The SDk
> function is PrintEvent() and you get the possibility to write to the
> POV file whenever these events occur. The events are:

Thanks for the reply, but I think i'll stay with Fullmoon for a little
longer. I may have found a solution using a transparent object and a union,
see new picture in m.b

Stephen

--
My perception of reality may differ from yours.

Post a reply to this message