 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nieminen Juha <war### [at] punarastas cstutfi> wrote...
> Francois Dispot <woz### [at] club-internetfr> wrote:
> : OTOH being able to determine the size of a picture at render time can be
> : useful for special applications like automatic rendering of ttf fonts
> : samples.
>
> You don't need ini_option for this.
>
How? I think he's talking about using min_extent and max_extent so as to
render only what is within the bounding box of the object.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <389f1394@news.povray.org> , "Nathan Kopp" <Nat### [at] Koppcom>
wrote:
> You gave an example supporting your point using "+QR". This setting is
> actually THE reason that I created ini_option. In many of my test renders
> while I was working on enhancing POV's radiosity features, I was always
> opening up the render options dialog box to turn radiosity on and off.
I just gave it because it was the only feature I could come up with that
increases render time.
In general regarding radiosity - as you know from previous discussion - I
agree it should be turned on/off different in the future :-)
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nathan Kopp wrote:
> For setting the general size of the image (as opposed to aspect ratio),
> I've always used the GUI.
I have always used the same method for both image size and anti-aliasing
and I am comfortable with it. Quickres.ini serves it's purpose well in
this regard.
> * encapsulating the majority of a POV project within a single file: I know,
> ini_option doesn't even come close to succeeding at this. But it is a step
> in that direction. Of course, whether or not that is a step in the RIGHT
> direction is another question. Comments?
>
> Therefore, once those items are addressed in other ways (and most of them
> have already been discussed by the POV-Team), then ini_option will no longer
> be necessary. That is the reason I said it may not always remain. It will
> remain in MegaPov until it is no longer needed.
>
> -Nathan
The four areas that I would value this feature for are (in no particular
order of importance) -
1.) image output format i.e. tga, png, ...
2.) radiosity on/off - options
3.) animation options - clock, Initial_Frame, Final_Frame, Cyclic_Animation...
4.) automatic bounding on/off
Any other ini options that are available I use so seldom I can live
with adding them to an ini file when needed. The options listed above
however I use frequently enough that it would be nice to have them
available within the scene file I am working on.
Then again from a Windows only perspective if all of these options
were added as part of the GUI ( a drop down menu ) they too could be
eliminated having no reason for them at all. The only people that
lose in this scenario are those platforms where it might be impossible
to add them because there is no GUI available.
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <389F2908.CE8E89AE@pacbell.net> , Ken <tyl### [at] pacbellnet>
wrote:
> The four areas that I would value this feature for are (in no particular
> order of importance) -
>
> 1.) image output format i.e. tga, png, ...
Hmm, "sys"? ;-)
> 2.) radiosity on/off - options
Agreed.
> 3.) animation options - clock, Initial_Frame, Final_Frame, Cyclic_Animation...
Interesting, I never thought about that but it would make sense once the
need for re-parsing for animations is eliminated. It would however break the
QT movie output on Macs, but I could surely find a solution.
> 4.) automatic bounding on/off
Maybe a better bounding system would also do the job?
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken <tyl### [at] pacbellnet> wrote...
>
> 2.) radiosity on/off - options
As Thorsten hinted at, this is being addressed by the POV-Team and an
alternative solution (which does not require ini_option) has been
tentatively agreed upon.
> 3.) animation options - clock, Initial_Frame, Final_Frame,
Cyclic_Animation...
You are not able to use ini_option to set these options, since they must be
set before the POV file is parsed.
> 4.) automatic bounding on/off
This might be a nice option to specify in the POV file, since POV messes up
the automatic bounding in some scenes and not others, and it would be nice
to turn it off for those scene where it doesn't work without messing with
INI files where you might forget to turn it back on for other scenes.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> > 1.) image output format i.e. tga, png, ...
>
> Hmm, "sys"? ;-)
Well it is a platform independant option anyway isn't it ?
> > 3.) animation options - clock, Initial_Frame, Final_Frame, Cyclic_Animation...
>
> Interesting, I never thought about that but it would make sense once the
> need for re-parsing for animations is eliminated. It would however break the
> QT movie output on Macs, but I could surely find a solution.
I think those that do a lot of animation work would really appreciate this
one. As far as the QT problem Thorsten is wise and all knowing so finding
a solution should be no problem :)
> > 4.) automatic bounding on/off
>
> Maybe a better bounding system would also do the job?
This of course would be preferable. I never know for sure when manual
bounding will help out and usually only through trial and error do I
find out if it helps the render time. Still there are some games you
can play with manual bounding for special effects that it would be
nice to be able to disable it when you want to.
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nathan Kopp wrote:
>
> > - The type of rendering (size, antialiasing, etc) should specified
> outside
> > the scene, not inside.
>
> Why? Because "that's the way it's always been"? That by itself is not a
> good reason. (That reason, coupled with "users appreciate backwards
> compatibility and consistency", as Thorsten mentioned, is a pretty good
> reason, however.)
>
> -Nathan
I've always considered it obvious that the scene file describes the
_scene_ not the image.
Some kind of Allow_Scene_Ini_Options option strikes me as a good idea.
PoD.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trfde> wrote...
>
> In general regarding radiosity - as you know from previous discussion - I
> agree it should be turned on/off different in the future :-)
Yes, I remember that discussion. I had forgotten that I acutally did get
around to implementing that in MegaPov already. MegaPov users please see
section 10.2.10 of the MegaPov documentation.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 07 Feb 2000 12:20:24 -0800, Ken <tyl### [at] pacbellnet> wrote:
>
>
>Nathan Kopp wrote:
>
>> For setting the general size of the image (as opposed to aspect ratio),
>> I've always used the GUI.
>
>I have always used the same method for both image size and anti-aliasing
>and I am comfortable with it. Quickres.ini serves it's purpose well in
>this regard.
>
As long as one doesn't have files created with a multitude of
different aspect ratios, then "quickres.ini" does work pretty well,
for windows users at least. I happen to have files that I have created
for several different aspect ratios.
I can't simply render one of my files without having to find the
camera statement in each one, and determine the aspect ratio for the
image. Then I pick an appropriate height and width to enter into the
GUI by hand, because all too often, that particular aspect ratio isn't
supported by "quickres." Yes, I have a modified version of quickres
that includes other aspect ratios, but it is a pain to create
*several* new entries in this file for each aspect ratio that I want
to support. The resulting file also becomes awkward to scroll through,
because of the sheer number of presets I have incorporated.
It is much easier to simply write the height and width into the scene
file, near the top of the file, and then I never render it at the
wrong aspect ratio. If I want to change the size, I simply edit the
scene file, which is not awkward, since the size is specified near the
top of the file, easy to find.
As for aspect ratio, perhaps it would be possible to seperate it from
the actual image size in some way. Currently it is only possible to
set it indirectly. What if we could specify the scene Height and
Aspect Ratio, instead of Height and Width? The Aspect Ratio would be
set in the scene file, and you could set the Height from the command
line or "povray.ini." That way, no matter what size you rendered a
scene file at, it would have the proper aspect ratio. There would no
longer be the need for checking the camera statement in each scene
file before rendering, to determine the proper aspect ratio to
indirectly set via the Height and Width settings. Does anyone like
this idea?
later,
Glen Berry
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 7 Feb 2000 13:49:45 -0500, "Nathan Kopp" <Nat### [at] Koppcom>
wrote:
>Why? Because "that's the way it's always been"? That by itself is not a
>good reason. (That reason, coupled with "users appreciate backwards
>compatibility and consistency", as Thorsten mentioned, is a pretty good
>reason, however.)
>
Speaking in general, the "backwards compatibility" flag is waved by
*someone* almost every time a change is suggested. I say if a
particular change is for the better, then screw backwards
compatibility. If I have to change syntax on one of my older scene
files to accomodate a new version of POV, then so be it. I won't be
crying about it. I'll be too busy appreciating the new features or
improvements. I'd hope that most people have a similiar opinion.
Please note that this post isn't concerning the ini_option issue. I
just want to express this opinion openly in regards to *any* change
that is being considered by the POV-Team, or any of the programmers
making custom patches. Please, don't ever be afraid to try something
new.
thanks,
Glen Berry
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
