Is there a simple way in Moray to import a POV inc file of texture
definitions??  I have an include file with several HUNDRED texture
definitions that I want to import for use with Moray.

--
Calin
http://www.calin.com
calin at calin dot com

Post a reply to this message

Hi ZuluNiner, you recently wrote in moray.win:

> Is there a simple way in Moray to import a POV inc file of texture
> definitions??  
Simple? No, sorry. Actually there isn't any way, really.

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

Post a reply to this message

There exists somewhere (ask uncle ken) a povtomdl.exe utility (works with
POV3.0 definitions only)
Philippe

>Is there a simple way in Moray to import a POV inc file of texture
>definitions??  I have an include file with several HUNDRED texture
>definitions that I want to import for use with Moray.
>
>--
>Calin
>http://www.calin.com
>calin at calin dot com
>
>
>
>

Post a reply to this message

I don't supposed you'd consider that as a future feature??

or possibly an external tool to convert texture definitions from POV inc to
library files??  Or even simply the ability to ADD a texture to an existing
library (and add new libraries.)
--
ZuluNiner
(aka Calin/Runesinger)
ZuluNiner at fuckyou dot co dot uk


Lutz Kretzschmar <lut### [at] stmuccom> wrote in message
news:373### [at] 194174214110...
> Hi ZuluNiner, you recently wrote in moray.win:
>
> > Is there a simple way in Moray to import a POV inc file of texture
> > definitions??
> Simple? No, sorry. Actually there isn't any way, really.
>
> - Lutz
>   email : lut### [at] stmuccom
>   Web   : http://www.stmuc.com/moray

Post a reply to this message

Ph Gibone wrote in message <372f1c9d.0@news.povray.org>...
>There exists somewhere (ask uncle ken) a povtomdl.exe utility (works with
>POV3.0 definitions only)


I think it is POV 2.0 ony, and the "somewhere" is Thomas Baier's site if I
am not mistaken (now hosted on the stmuc server...)

Johannes.

Post a reply to this message

If you know how to do POV-Code(Or, if you are even lazier, use the same
names), just use the .inc file to texture each object. If you don't want
to do much work, just have it replace whatever texture name you gave it
in moray with the texture name you want to use.

ZuluNiner wrote:

> Is there a simple way in Moray to import a POV inc file of texture
> definitions??  I have an include file with several HUNDRED texture
> definitions that I want to import for use with Moray.
>
> --
> Calin
> http://www.calin.com
> calin at calin dot com



--
Given a lever long enough, one can move the world with little force
      MJ Engh

Post a reply to this message

>I think it is POV 2.0 ony,

I didn't check, but I know that I have imported a lot of texture in Moray
with this program!
Anyone interested by the MTX files ?
>and the "somewhere" is Thomas Baier's site if I
>am not mistaken (now hosted on the stmuc server...)
>
You're not mistaken
Philippe

Post a reply to this message

Hi ZuluNiner, you recently wrote in moray.win:

> I don't supposed you'd consider that as a future feature??
Probably not. I don't have the time to write a POV-Ray parser from
scratch (which is what I'd have to do). However, this would be a
perfect task for the Plugin SDK.

> or possibly an external tool to convert texture definitions from POV inc to
> library files??  Or even simply the ability to ADD a texture to an existing
> library (and add new libraries.)
I'm not sure what you mean by Library. But if you mean Moray Texture
Libraries (i.e. *.MTX files), then you *can* add to them and create
new ones, etc. We are also working on better texture library
management for the next version of Moray.

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

Post a reply to this message

Lutz Kretzschmar wrote:
> 
> Hi ZuluNiner, you recently wrote in moray.win:
> 
> > I don't supposed you'd consider that as a future feature??
> Probably not. I don't have the time to write a POV-Ray parser from
> scratch (which is what I'd have to do). However, this would be a
> perfect task for the Plugin SDK.
> 
> > or possibly an external tool to convert texture definitions from POV inc to
> > library files??  Or even simply the ability to ADD a texture to an existing
> > library (and add new libraries.)
> I'm not sure what you mean by Library. But if you mean Moray Texture
> Libraries (i.e. *.MTX files), then you *can* add to them and create
> new ones, etc. We are also working on better texture library
> management for the next version of Moray.
> 
> - Lutz
>   email : lut### [at] stmuccom
>   Web   : http://www.stmuc.com/moray


Lutz,

  Have you by any chance seen the C++ programming library called ParPov ?


  A brief discription from the home page of the program source.

---------
   ParPov is a free (GNU), object-oriented library written in C++ for
parsing Scene Files of the Persistence of Vision Ray-Tracer (POV-Ray).
It will read a scene written in version 1-3 syntax and creates a structure
of C++-Objects, representing all details of the original description. You
can query those objects and use the information for conversion to other
formats or for many other uses. Pov2Rib is also a freely available progam,
which allows you to convert scene files from POV-Ray to a RenderMan Interface
Bytestream (RIB). The tool is the first application of libParPov. 
---------

This is the first work I have seen that actually parses Pov files and
converts it to usable data. More information can be found at the link
below.

http://www9.informatik.uni-erlangen.de/~cnvogelg/pov2rib/index.html


Regards,

-- 
Ken Tyler

mailto://tylereng@pacbell.net

Post a reply to this message

Hi Ken, you recently wrote in moray.win:

> Have you by any chance seen the C++ programming library called ParPov ?
I've heard of it.

[Later]

I just checked out the website. Although technically it may be
feasable, the fact that it is under the GNU license means I have to
release source code of any programs I incorporate it into, right?

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

Post a reply to this message