Naturally, I'd like to hear about any bugs you find. There will be a section on the download page that will describe the recommended procedure for bug reporting that will maximize the chances of it getting fixed.
Vrml2pov is written in C++ without (I think) any reference to system-specific libraries, and does not have a windowed user interface, so the code should be quite portable, with a few command line switches to control the behaviour of the program. I have provided compiled binaries for PC/Windows and SGI. A note about the parser: I wrote my own VRML parser because I wanted to write in C++, to follow the very latest VRML97 specification, and because some of the parsers out there that I tried failed to parse even simple samples that I fed to them. It should work with VRML V2.0 files, but will not take VRML V1.0.
This program aims to convert a VRML file into a static POV scene. Thus, everything in the VRML file having to do with time, animation, events, and routes is ignored. So, basically it is only the VRML Shape nodes that get transferred into the POV scene, although there are many other nodes that are necessarily read along the way. Not every standard VRML node has any correlation to a POV object, and of those that do, not every one is currently implemented. But I think a large majority of VRML scenes should be covertible by the current version of vrml2pov.
There are a few standard nodes that I want to mention here, that are not implemented yet, but that will likely be added in the not-too-distant future:
If anyone comes up with some other nice examples, please feel free to share them - I'd like to have some cool stuff here other than just chemistry...
This is a cool
bacteriochlorophyll protein (PDB entry 3BCL) created with Molscript's molauto
program and rendered with Molscript.
Here's the
Molscript-generated VRML file viewed with Cosmo. (from this VRML file)
And finally, the POV
version. The main point here is that the shape and color of the VRML objects are
converted quite faithfully into POV. However, VRML's and POV's lighting models
are quite different, so the color intensity, and especially the material
apperance, will likely not be an exact match. But it should be pretty close, and
POV users can of course manually tinker with the finish statements to make it
right. (Here's the POV file)
This is a
Molscript representation of the insulin molecule (that I was using to learn to
use Molscript), showing the backbone helices and the disulfide bonds that hold
the two peptides together.
... and the
Cosmo version (or in VRML) ...
... and the POV version
(or the POV file) .
This is a
sample that I borrowed directly from the Molscript image gallery.
It is the ras p21 enzyme (PDB entry 1CRQ), rendered with Molscript. Users of
Molscript should pay particular attention to the README file's discussion of
backface culling, which is required for the rendering of 2-color helix ribbons
like those shown here.
... and the Cosmo version
(or in VRML) ...
... and the POV version
(or the POV file).
This is a tRNA molecule
created with the Ribbons software
package. It is one of the demo molecules that comes with the latest version.
This is the final POV rendering of the molecule - Ribbons does some fancy things
with animated viewpoints in the VRML file, so the corrleation of viewpoints
between the Ribbons console and the VRML (and thus POV) output is not as direct
as with Molscript.
This is the LEGAL file for vrml2pov version 0.7. These are the legal terms to which you implicitly agree when using vrml2pov for any purpose: Vrml2pov is written and copyrighted (C) 1998-2003 by Paul Thiessen, paul@ChemicalGraphics.com This software is copyrighted freeware. The binary program, either distributed by the author or compiled from the source code as distributed, may be used for any purpose without incurrence of any fees or royalties. The author may not be held responsible in any way for any losses that occur via the use of this software. The author makes no guarantee as to the efficacy of this software. Support, if any, is provided at the sole discretion of the author. Neither the compiled program nor any portion of the source code may be sold for profit, nor distributed without the author's explicit permission. The source code is protected by U.S. copyright laws. Permission to use portions of the source code in academic or non-profit applications may be granted upon request to the author, and at the author's discretion. If permission is granted, appropriate credit to the author must be given. The source code, whole or in part, MAY NOT be used in any commercial (for- profit) application without the payment of a (negotiable) fee to the author. Requests for commercial use of the code will be handled individually and should be made directly to the author.Now, with that out of the way, let's get on with it!
Enjoy!