 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
While browsing through some Povray links (for wiki maintenance) I came across
this page:
http://phi.lho.free.fr/artwork/POV-Ray/POV-Ray.en.html
And the following sentence caught my eye:
"It was before the coming of procedural handling of scenes, so to create complex
scenes with repetitive elements, we had to create external programs (in Basic,
C, whatever) that generated the POV-Ray file. Note that it is still doable, the
generator can be much faster than the internal parser..."
Is such a thing still possible? what would the data flow be then, if the scene
is not parsed?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mr wrote:
> Is such a thing still possible? what would the data flow be then, if the scene
> is not parsed?
I think the author refers to building content procedurally
using loops and macros instead of just describing the plain
geometry and textures in CSG. So, if you wish to create
10,000 spheres you can either use a #while loop, or you
can use an external program to create an include file
with 10,000 sphere {...} declarations.
The second way will usually be faster but rarely worth
the effort unless you need very complicated calculations
to generate your geometry.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christian Froeschlin wrote:
> The second way will usually be faster but rarely worth
> the effort unless you need very complicated calculations
> to generate your geometry.
Or unless someone has already written a generalized program specifically for
that sort of thing.
http://sourceforge.net/projects/lome/
--
Darren New, San Diego CA, USA (PST)
Yes, we're traveling together,
but to different destinations.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christian Froeschlin <chr### [at] chrfr de> wrote:
> Mr wrote:
>
> > Is such a thing still possible? what would the data flow be then, if the scene
> > is not parsed?
>
> I think the author refers to building content procedurally
> using loops and macros instead of just describing the plain
> geometry and textures in CSG. So, if you wish to create
> 10,000 spheres you can either use a #while loop, or you
> can use an external program to create an include file
> with 10,000 sphere {...} declarations.
>
> The second way will usually be faster but rarely worth
> the effort unless you need very complicated calculations
> to generate your geometry.
Thanks for making things clearer, but another thing got me a little confused:
"Bishop3D communicates with POV-Ray via POV-Ray's extension interface, providing
a seamless integration between the modeler and the renderer."
is this "extension interface" something precise or another term to designate
some aspect of various commonly used povray features?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mr wrote:
> "Bishop3D communicates with POV-Ray via POV-Ray's extension interface, providing
> a seamless integration between the modeler and the renderer."
>
> is this "extension interface" something precise or another term to designate
> some aspect of various commonly used povray features?
the windows version provides a mechanism for "GUI Extensions" which
allows other applications to integrate into the IDE. I've never used
Bishop3d but from its website it indeed seems to support this:
http://www.bishop3d.com/wiki/index.php?title=Manual:Setting_Bishop3D_POV-Ray_Communication_Manually
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 16/04/2010 7:47 PM, Christian Froeschlin wrote:
> Mr wrote:
>
>> "Bishop3D communicates with POV-Ray via POV-Ray's extension interface,
>> providing
>> a seamless integration between the modeler and the renderer."
>>
>> is this "extension interface" something precise or another term to
>> designate
>> some aspect of various commonly used povray features?
>
> the windows version provides a mechanism for "GUI Extensions" which
> allows other applications to integrate into the IDE. I've never used
> Bishop3d but from its website it indeed seems to support this:
>
>
http://www.bishop3d.com/wiki/index.php?title=Manual:Setting_Bishop3D_POV-Ray_Communication_Manually
>
>
You are right Christian. The "GUI Extensions" used by Bishop3D and Moray
can start PovRay and pass an INI file to it to run a Pov file. It can,
by some magical (to me) means, display the output image as it is being
rendered. (In Bishop3D it is not obvious how this is done but in Moray
it is automatically displayed.)
--
Best Regards,
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> You are right Christian. The "GUI Extensions" used by Bishop3D and Moray
> can start PovRay and pass an INI file to it to run a Pov file. It can,
> by some magical (to me) means, display the output image as it is being
> rendered. (In Bishop3D it is not obvious how this is done but in Moray
> it is automatically displayed.)
>
> --
>
> Best Regards,
> Stephen
I don't really see how usefull that is? I was hoping it would make some
rendering speed benefit or workflow maybe? Other than launching Pov? After
trying Bishop I am not sure. Did I miss something?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 18/04/2010 10:55 AM, Mr wrote:
>
>> You are right Christian. The "GUI Extensions" used by Bishop3D and Moray
>> can start PovRay and pass an INI file to it to run a Pov file. It can,
>> by some magical (to me) means, display the output image as it is being
>> rendered. (In Bishop3D it is not obvious how this is done but in Moray
>> it is automatically displayed.)
>>
>> --
>>
>> Best Regards,
>> Stephen
>
> I don't really see how usefull that is? I was hoping it would make some
> rendering speed benefit or workflow maybe? Other than launching Pov? After
> trying Bishop I am not sure. Did I miss something?
>
>
>
Probably not. The "GUI Extensions" is for use with modellers. Bishop3D
and Moray helped my workflow as I find it difficult to visualise the
scenes and the OpenGL view helps me a lot.
--
Best Regards,
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Don't get me wrong, I do like modelling softwares with GUI (I'm a Blender user)
but I don't see what a modeler using this POV extension would gain compared to a
modelling software that would just export a POV file and launch it via operating
system or python commands like Blender 2.5 currently does. (it can even preview
the file as it's being written depending on the file format)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 18/04/2010 4:26 PM, Mr wrote:
> Don't get me wrong, I do like modelling softwares with GUI (I'm a Blender user)
> but I don't see what a modeler using this POV extension would gain compared to a
> modelling software that would just export a POV file and launch it via operating
> system or python commands like Blender 2.5 currently does. (it can even preview
> the file as it's being written depending on the file format)
>
>
To be truthful neither do I. I assume that the native Pov extension has
Bishop3D can preview the file before it is written and both Bishop3D and
Moray can include SDL to be exported. Moray has some rudimentary mesh
creating/editing functions while Bishop3D does not. Both of them export
to PovRay either pure SDL or include mesh files.
If you are looking for some means to cut down the work that PovRay has
to do then I do not think that this extension is what you are looking for.
I might be corrected by others.
--
Best Regards,
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
