Hi!

Is it possible to get variable content as an output after parsing a
scene for debug purposes?

regards

Hardy

Post a reply to this message

Erhard Ducke <pov### [at] temporaryforwardingcom> wrote:
> Is it possible to get variable content as an output after parsing a
> scene for debug purposes?

  Which variables?

-- 
                                                          - Warp

Post a reply to this message

Warp wrote:

>   Which variables?

Different identifiers that are changed e.g. in animations of recursive
structures. In most cases I need the current vectors or colors of
certain frames if possible as text output while the scene is rendered...

regards
Hardy

Post a reply to this message

Erhard Ducke <pov### [at] temporaryforwardingcom> wrote:
> Hi!
>
> Is it possible to get variable content as an output after parsing a
> scene for debug purposes?
>
> regards
>
> Hardy

I don't know about truely *after* but you can always convert things like
floats to strings and then put your #debug statements where they'll get
parsed right at the end of the parsing stage.  Or you can put those strings
into in-scene text objects.  Do you need it to be truely after?

Post a reply to this message

Erhard Ducke <pov### [at] temporaryforwardingcom> wrote:
> Warp wrote:
>
> >   Which variables?
>
> Different identifiers that are changed e.g. in animations of recursive
> structures. In most cases I need the current vectors or colors of
> certain frames if possible as text output while the scene is rendered...
>
> regards
> Hardy

How about having your scene write the info you want to a text-file.  The
file
should be there as soon as the scene has finished parsing and you can read
it while the render takes place

Post a reply to this message

FrogRay wrote:

> How about having your scene write the info you want to a text-file.  The
> file
> should be there as soon as the scene has finished parsing and you can read
> it while the render takes place

Yes, that would be great. As FrogRay wrote I have to convert the
identifier to a string and then write it to the log using #debug. Is
that right?

regards Hardy

Post a reply to this message

Erhard Ducke <pov### [at] temporaryforwardingcom> wrote:
> FrogRay wrote:
>
> > How about having your scene write the info you want to a text-file.  The
> > file
> > should be there as soon as the scene has finished parsing and you can read
> > it while the render takes place
>
> Yes, that would be great. As FrogRay wrote I have to convert the
> identifier to a string and then write it to the log using #debug. Is
> that right?
>
> regards Hardy


Yes, you'll still want to turn things into floats, (str() vstr() concat()
etc).   For file writing I think you can direct the #debug stream to a file,
but  I think Frogray was suggesting to use POV-Ray's file-i/o capabilities,
i.e. #fopen and #write instead of #debug.

Charles

Post a reply to this message

Erhard Ducke nous apporta ses lumieres en ce 21-03-2007 18:46:
> FrogRay wrote:

>> How about having your scene write the info you want to a text-file.  The
>> file
>> should be there as soon as the scene has finished parsing and you can read
>> it while the render takes place

> Yes, that would be great. As FrogRay wrote I have to convert the
> identifier to a string and then write it to the log using #debug. Is
> that right?

> regards Hardy
It can be done that way, or you can create your own file.
Use #open #write and #close to open/create the file, write values and close the 
file when you are finished filling it.

-- 
Alain
-------------------------------------------------
A clear conscience is usually the sign of a bad memory.

Post a reply to this message

Hi,

I think i'm now able to manage my problem...

Thanks for your time and brain!

regards Hardy

Post a reply to this message