 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello
If I understood right giving povray the -GA argument should turn off
all console messages. I tried
povray +Iscene.pov -GA
but all messages appear on the console. povray even tells that
everything is turned off (which is very polite but a bit weird).
<povray-output>
...
Redirecting Options
All Streams to console..........Off
Debug Stream to console.........Off
Fatal Stream to console.........Off
Render Stream to console........Off
Statistics Stream to console....Off
Warning Stream to console.......Off
...
</povray-output>
All messages go through stderr with -GA *enabled* or not.
Why do messages streams not take their way through stdout?
And why do the stream to console flags do not affect the
output at all?
Does anyone has clue about this?
Sebastian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> povray +Iscene.pov -GA
>
> but all messages appear on the console. povray even tells that
> everything is turned off (which is very polite but a bit weird).
This is a known bug in the 3.6 series that has been already
discussed in this group. If you want a fix, you can try the Unix
frontend patch (latest version is 0.2.1) described in some recent
messages here.
> Why do messages streams not take their way through stdout?
Because stdout can be used to output the rendered image,
using e.g. 'povray +o-'. Check the user manual.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>> povray +Iscene.pov -GA
>>
>> but all messages appear on the console. povray even tells that
>> everything is turned off (which is very polite but a bit weird).
>
>
> This is a known bug in the 3.6 series that has been already
> discussed in this group. If you want a fix, you can try the Unix
> frontend patch (latest version is 0.2.1) described in some recent
> messages here.
Ah yes, I'll give it a try.
Thank you very much.
Sebastian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 31 Jan 2006 17:27:06 +0100, Sebastian H. wrote:
> Hello
>
> If I understood right giving povray the -GA argument should turn off
> all console messages. I tried
>
> povray +Iscene.pov -GA
>
> but all messages appear on the console. povray even tells that
> everything is turned off (which is very polite but a bit weird).
>
> <povray-output>
> ...
> Redirecting Options
> All Streams to console..........Off
> Debug Stream to console.........Off
> Fatal Stream to console.........Off
> Render Stream to console........Off
> Statistics Stream to console....Off
> Warning Stream to console.......Off
> ...
> </povray-output>
>
> All messages go through stderr with -GA *enabled* or not.
> Why do messages streams not take their way through stdout?
> And why do the stream to console flags do not affect the
> output at all?
> Does anyone has clue about this?
>
> Sebastian
povray -iscene.pov 2>/dev/null
The "2>" forces stderr to be redirected instead of stdout.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 31 Jan 2006 17:27:06 +0100, Sebastian H. wrote:
"...giving povray the -GA argument should turn off all console messages. I
tried but all messages appear on the console. Povray even tells everything
is turned off. All messages go through stderr, -GA *enabled* or not."
Try, taking care for the Ampersand:
xterm -T DEBUGWINDOW -e tail -f ./DEBUG.txt &
povray +GD./DEBUG.txt ./INPUT.pov
Lines in INPUT.pov like e.g.:
#debug concat( "nHALLO SEBASTIAN: ", str(clock,0,0), "n" )
will produce their output in DEBUGWINDOW and, nearly, nothing else. Does
work for pov3.6 on SuSE9.0
Best regards: WellenZillich
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
SORRY: Replace "n" with "\n":
xterm -T DEBUGWINDOW -e tail -f ./DEBUG.txt &
povray +GD ./DEBUG.txt ./INPUT.pov
Lines in INPUT.pov like e.g.:
#debug concat( "\nHUHU: Linebreak after two:", "one,"two","\n","three")
will produce output in DEBUGWINDOW.
Best Regards: WellenZillich
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
WellenZillich wrote:
> SORRY: Replace "n" with "\n":
>
> xterm -T DEBUGWINDOW -e tail -f ./DEBUG.txt &
> povray +GD ./DEBUG.txt ./INPUT.pov
>
> Lines in INPUT.pov like e.g.:
> #debug concat( "\nHUHU: Linebreak after two:", "one,"two","\n","three")
> will produce output in DEBUGWINDOW.
Hmm, interesting idea though I would prefer a fifo instead of invoking
tail. However this does not cure the problem with the current inability
of linux-POV-Ray to turn off stderr output. This requires a patch as
mentioned somewhere else.
Regards,
Sebastian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 08 Apr 2006 10:24:59 +0200, Sebastian H. wrote:
> WellenZillich wrote:
<<snippage>>
> tail. However this does not cure the problem with the current inability
> of linux-POV-Ray to turn off stderr output. This requires a patch as
<<snippage>>
povray -iyour_pov_file 2>/dev/null
"2>" redirects stderr. Redirecting it to /dev/null
effectively turns it off.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
bob <bob### [at] almost bestwebnet> wrote on SebastianH. & WellenZillich:
Sebastian H. wrote:
"...giving povray the -GA argument should turn off all console messages. I
tried but all messages appear on the console. Povray even tells everything
is turned off. All messages go through stderr, -GA *enabled* or not."
bob wrote:
povray -iyour_pov_file 2>/dev/null
"2>" redirects stderr to /dev/null & turns it off.
No question bob is right and console messages could be get rid off this way.
BUT: Working around the problem this way would cause the next questions
concerning textconsole output switches GD, GF, GR, GS, GW. My "Catching the
debug stream" should have been read as the pragmatic answer to the first4me
important one of these not yet asked questions.
Apropos FIFO: Yet anybody really has tried get it2work? Seems not2be doable
as easy as first thought by me, regrettable.
Regards from the ascending branch:
Wellenzillich
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
