As I can't keep up with the 3.5b versions ;) I'm still using 3.1 and Mega 7.0.

I'm sure that in Megapov7, one can include switches for the Width and Height
(+Wn & +Hn ?)  in the scene file but I cannot find an example of how it's done.
I have searched the docs, believe me ! but can't get the keywords Image_height
& width or +Wn to be recognized.  Will someone please give me the simple
code for use in the scene?

Also ... is it possible to specify AA depth and threshold in the scene?
I haven't been able to.
If not, what's the simplest method to use to change resolution and AA without
having to edit the Quickres INI every time?  Can i write my own INI and then
call it up to override the quickres.ini ?  I have zero experience with command
lines or useing sperate INI's.  Am reading up INI's right now.

One more Q ... am endeavoring to create some logos for a friend using 320x240
and 160x120.  At this res, what's the best AA threshold and depth to use ? They
don't take much time to render so I would like to shoot for the highest quality
Possible.
Tanks
--
Y

Post a reply to this message

"Y" <out### [at] huntelnet> wrote in message news:3bae2f5d@news.povray.org...
>
> I'm sure that in Megapov7, one can include switches for the Width and
Height
> (+Wn & +Hn ?)  in the scene file but I cannot find an example of how it's
done.
> I have searched the docs, believe me ! but can't get the keywords
Image_height
> & width or +Wn to be recognized.  Will someone please give me the simple
> code for use in the scene?

global_settings {
ini_option "+w320 +h240"
 }

> Also ... is it possible to specify AA depth and threshold in the scene?
> I haven't been able to.

Same way as above, only use +a0.3 for example, of course  :-)

> If not, what's the simplest method to use to change resolution and AA
without
> having to edit the Quickres INI every time?  Can i write my own INI and
then
> call it up to override the quickres.ini ?  I have zero experience with
command
> lines or useing sperate INI's.  Am reading up INI's right now.

Adding to the renderer\Quickres.ini file is as easy as going into the Tools
menu and selecting Edit secondary INI file.  I think that's better than
creating a new one, only my opinion of the moment though.

> One more Q ... am endeavoring to create some logos for a friend using
320x240
> and 160x120.  At this res, what's the best AA threshold and depth to use ?
They
> don't take much time to render so I would like to shoot for the highest
quality
> Possible.

+a0.1 +r4 might do okay and not take forever.  A jitter (+j1 is default) of
1.0 can sometimes foul up things by making grainy lines though so you might
want to lower it.
Everyone has their own preference.  I just like to also use +am2 instead of
+am1 because the description of how it works sounds good to me  :-)

Bob H.

Post a reply to this message

: +a0.1 +r4 might do okay and not take forever.  A jitter (+j1 is default) of
: 1.0 can sometimes foul up things by making grainy lines though so you might
: want to lower it.
: Everyone has their own preference.  I just like to also use +am2 instead of
: +am1 because the description of how it works sounds good to me  :-)
:
: Bob H.
:

Thanks Bob ... messed with it a bit and didn't find a lot of difference at
320x240 between am1 and am2 ... am2 does slow it up quite a bit but as
you say ... it sounds cooler ;)

Can all the switches be used in the global ini-options ?
Thanks again
--
Y

Post a reply to this message

Bob H. <omn### [at] msncom> wrote:
: global_settings {
: ini_option "+w320 +h240"
:  }

  Don't get used to that if you want to use pov3.5 some day.

  You can either write those on the command line (field in windows) or
make a scene-specific ini file (in windows it should be enough to open
that ini file and "render" it).

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

:   Don't get used to that if you want to use pov3.5 some day.
:
:   You can either write those on the command line (field in windows) or
: make a scene-specific ini file (in windows it should be enough to open
: that ini file and "render" it).
:
 - Warp -

Yup ... I saw that when I was taking it for a test run ...
--
Y

Post a reply to this message

"Y" <out### [at] huntelnet> wrote in message news:3bae8e82@news.povray.org...
>
> Thanks Bob ... messed with it a bit and didn't find a lot of difference at
> 320x240 between am1 and am2 ... am2 does slow it up quite a bit but as
> you say ... it sounds cooler ;)

Well hey, from the doc description it must be better  :-)

> Can all the switches be used in the global ini-options ?

Nope.... and I have no idea what can and can't be either except as the docs
say clock settings cannot be.  Direct quote: "Not all INI options can be
used. Specifically, those related to animation, output file, and shell-out
commands are not allowed."

Bob H.

Post a reply to this message

: Well hey, from the doc description it must be better  :-)

Interesting thread right here in this group ... "AA tweaking idea"
posted by Xplo Eristotle on 9/18.
Didn't see your nik in the thread so mayby you didn't see it.

: > Can all the switches be used in the global ini-options ?
:
: Nope.... and I have no idea what can and can't be either except as the docs
: say clock settings cannot be.  Direct quote: "Not all INI options can be
: used. Specifically, those related to animation, output file, and shell-out
: commands are not allowed."
:
: Bob H.
:
Yeah ... I saw that too. Just wondered about the output file ones.
--
Y

Post a reply to this message