 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscape net> wrote:
>
> One thing that might be useful is to include some reminders and usage info for
> output to the debug stream.
> I often
> #declare Verbose = true;
> in my scene, and then any macros or parts of the scene where I want to get data
> from check for that variable and then I get everything I want with just one
> "switch".
>
> I do the same thing with any weird command syntax that I use - I just output or
> include in the comments a working line of code using that command.
That's a new trick to me; I thought Verbose was only for
use in an .ini file (I'm running Windows.) Could you explain how you use it or
how you make it work? I tried simply sticking #declare Verbose=on in the
middle of a scene file, but didn't see anything different(?) in the message
stream after the render. I'm *obviously* not 'getting it'... :-( Is it used in
conjunction with #debug somehow? Do other .ini parameters need changing too?
Thanks. This looks to be quite useful!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] gmailcom> wrote:
> That's a new trick to me; I thought Verbose was only for
> use in an .ini file (I'm running Windows.)
Ha! And there's something _I_ was unaware of. :O
> Could you explain how you use it or
> how you make it work? I tried simply sticking #declare Verbose=on in the
> middle of a scene file, but didn't see anything different(?) in the message
> stream after the render. I'm *obviously* not 'getting it'... :-( Is it used in
> conjunction with #debug somehow? Do other .ini parameters need changing too?
>
> Thanks. This looks to be quite useful!
It's not an internal POV-Ray thing - I write it into the macro or SDL myself.
If I have a complicated scene, there may be a lot of
#if (Verbose)
#debug blah blah blah value1 value2 vectorA, etc
#end // end if Verbose
sprinkled throughout the scene,
and if I write a macro, I'll spit out messages that it's been included, that
it's just gotten invoked, what variables it's working with, what their values
are, a help/man-page style usage example, end when the macro exits.
It's just a better and "more convenient" way for me to get documentation and see
what's going on without having to track down a separate ini or mcr file or open
a help page or search through the code to see what the heck I mis-coded (again)
THIS time.
Sorry for the confusion
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
>
> It's not an internal POV-Ray thing - I write it into the macro or SDL myself.
>
> If I have a complicated scene, there may be a lot of
> #if (Verbose)
> #debug blah blah blah value1 value2 vectorA, etc
> #end // end if Verbose
>
> sprinkled throughout the scene,
>
(***laughing out loud***)
OH, so *that's* what it means!! Thanks for clarifying. I haven't been so
thoroughly confused since I tried to understand the true nature of gravity. :-P
It just so happens that, right before I saw your post, I had been working with
POV-Ray's own "Verbose" command. So I naturally assumed... uh...
Had a good laugh over that one. :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sorry for the delay - it's been a positively tumultuous week or two, and I
have to juggle files back and forth on a USB stick...
Here's a short scene that writes SVG objects directly to file.
Post a reply to this message
Attachments:
Download 'make_svg.pov.txt' (13 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Another update.
Mike
Post a reply to this message
Attachments:
Download 'wp_graphical_projection_examples_20170514.zip' (358 KB)
|
|
| |
| |
|
|
|
|
| |
