I'm using POV to render certain scenes from within another application. POV
is activated by a CreateProcess() call with an argument line similar to:
"pvengine +GApov.log +Q8 +W64 +H64 +FS -D +A +Iin.pov +Oout.bmp /EXIT"
The problem is that POV stops in the parsing part when activated this way.
The last thing in both the message window and the log file says
"parsing..." and nothing further happens (but the process runs).
The strange thinig is that if I write the exact same command line in the
command line window, POV renders just fine (and exits). When starting POV
by and and running the same .pov file it also works fine.
---
I recently "donwgraded" from Windows XP back to Windows 2000 Pro due to all
kinds of problems. The approach worked in WinXP (and in Win2kPro before I
upgraded to WinXP), but now I'm having problems...
Does anyone have a clue what's happening. And is there a way to find it out?
-
Rune Winsevik
NORWAY
On Tue, 14 Jan 2003 08:48:34 EST, "Rune Winsevik" <nomail@nomail> wrote:
> I'm using POV to render certain scenes from within another application. POV> is activated by a CreateProcess() call with an argument line similar to:>> "pvengine +GApov.log +Q8 +W64 +H64 +FS -D +A +Iin.pov +Oout.bmp /EXIT"
have you tried to use 'start' command with parameters at begining of your
command ? helped ?
ABX
ABX wrote:
>On Tue, 14 Jan 2003 08:48:34 EST, "Rune Winsevik" <nomail[at]nomail> wrote:>> I'm using POV to render certain scenes from within another application. POV>> is activated by a CreateProcess() call with an argument line similar to:>>>> "pvengine +GApov.log +Q8 +W64 +H64 +FS -D +A +Iin.pov +Oout.bmp /EXIT">>have you tried to use 'start' command with parameters at begining of your>command ? helped ?>>ABX
It turned out that this happened only when I was debugging our app
(with td32). I would sure like to know why, but I guess it's no crisis
any more...
-Rune
