Nieminen Mika wrote:
> 
> Alex Magidow <axi### [at] mninternet> wrote:
> : Its not just that- if, for example, someone did write an export to another
> : renderer, wouldn't it be better to have a general scripting language instead of
> : a POV-Ray based one?
> 
>   How do you use povray features not implemented in moray (for example some
> objects, colefax's include files, etc)?

Your questions lead me to believe that you haven't explored all of what
Moray already offers for POV-Ray.  Here are some thoughts...

You can put definitions/include files into MorayPOV.inc (by default in
the main Moray directory).  This doesn't give you any sort of visual
representation of the object/texture/whatever, but makes it possible
(with every version of Moray back to the DOS days) to add unique things
to all of your scene files.

For things specific to an individual scene, you pull down the menu
Scene|Settings,  select the "includes" tab, and enter the .inc files you
plan to use.  Since these .inc files can contain anything you want, you
can use them set the variables for whatever other .include files you
might want to use.

If you want a more general capability, write a really small scene
interface that adds information to the POV-Ray .ini file.  In the
PrintEvent(...) part of the interface, you respond to the event
MRY_NTC_END_POVINI by writing text to the file that is being built.

If you want even more functionality, start writing object interfaces for
the things you really care about.  This is, of course, why Moray has a
plugin interface.

Xander

Post a reply to this message