 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm writing an app that will run povray with command line switches etc....
Is there a way to determine how far along a render is, or a way to get feed
back from the output of POVRay for windows??
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Weber (mwe### [at] racal-pelagos xcomc) wrote:
> I'm writing an app that will run povray with command line switches etc....
> Is there a way to determine how far along a render is, or a way to get feed
> back from the output of POVRay for windows??
For Windows, I am not sure. Try redirecting the output and error streams
to files, then parse these files (with Perl for instance), or try with pipes.
For DOS, the probability of this being possible is increased. For Linux,
it becomes 100 %. For other systems, I do not know. Anyway, you can still use
the DOS command-line version of POV (which even renders faster than the Windows
one), and parse the output files.
Happy ray-tracing,
Roland.
--
bob### [at] casimirrezelenstfr -- Linux, POV-Ray, LaTeX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>For Windows, I am not sure. Try redirecting the output and error streams
>to files, then parse these files (with Perl for instance), or try with pipes.
>For DOS, the probability of this being possible is increased. For Linux,
>it becomes 100 %. For other systems, I do not know. Anyway, you can still use
>the DOS command-line version of POV (which even renders faster than the Windows
>one), and parse the output files.
If you use the DOS/Unix versions, you can pipe the actual pixels to a program.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Since the application is in Windows, I'll be using POVRay for windows. The
output of POVRay can be redirected to a file, but the statistics appears
only after the rendering is complete. I noticed that Lutz wrote a DLL to
improve the communciations between POVRAY and MORAY. hmmmm I wonder if
there's a way to tap into that???
povray.org admin team wrote in message <351### [at] newsstmuccom>...
>>For Windows, I am not sure. Try redirecting the output and error streams
>>to files, then parse these files (with Perl for instance), or try with
pipes.
>>For DOS, the probability of this being possible is increased. For Linux,
>>it becomes 100 %. For other systems, I do not know. Anyway, you can still
use
>>the DOS command-line version of POV (which even renders faster than the
Windows
>>one), and parse the output files.
>
>If you use the DOS/Unix versions, you can pipe the actual pixels to a
program.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 25 Mar 1998 07:14:25 -0800, "Mike Weber"
<mwe### [at] racal-pelagoscomx> wrote:
>Since the application is in Windows, I'll be using POVRay for windows. The
>output of POVRay can be redirected to a file, but the statistics appears
>only after the rendering is complete. I noticed that Lutz wrote a DLL to
>improve the communciations between POVRAY and MORAY. hmmmm I wonder if
>there's a way to tap into that???
Go check out the windows/guiext subdirectory in your POV source
directory. I'd tell you to go over to povray.windows.gui-extensions,
but it seems to have been a casualty of the recent changeover. There
wasn't much traffic there, anyway.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Go check out the windows/guiext subdirectory in your POV source
>directory. I'd tell you to go over to povray.windows.gui-extensions,
>but it seems to have been a casualty of the recent changeover. There
>wasn't much traffic there, anyway.
It's been replaced by povray.programming.
-- Admin
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
