 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm looking for a list of valid or most common ranges of values for
parameters in a material/texture block. The documentation lists parameter
types (float, etc.) but I'd like to know the valid ranges instead. I've
just about finished writing a visual texture editor for the pov3.5 syntax
but i just need to define bounds on whichever parameters require them.
The simple answer would be that if it's not specified, then there isn't a
range but I'd rather not make assumptions.
Any help would be appreciated
Chris J
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christopher Johnson wrote:
>
> The simple answer would be that if it's not specified, then there isn't a
> range but I'd rather not make assumptions.
That's mostly correct, you can sometimes specify 'reasonable' ranges, for
example ior: 1-5, but you can always use other values as well - they might
lead to unexpected results though.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:3d82c9cd@news.povray.org Christopher Johnson wrote:
> I'm looking for a list of valid
Generaly, and this is one of the very nice things in POV-Ray, any value
is valid, unless specified differently in the documentation
> or most common ranges of values for
The range [0-1] is most used for maps and colors and some aspects of
finishes.
For other things like ior, dispersion and normal height etc. a common
range of values does not make sense.
> parameters in a material/texture block.
In case you want to set values with something like sliders, make them go
from 0-1 but allow the user to type in other values.
Ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Christoph Hormann" <chr### [at] gmx de> wrote in message
news:3D82F0B9.BA5D033F@gmx.de...
>
>
> Christopher Johnson wrote:
> >
> > The simple answer would be that if it's not specified, then there isn't
a
> > range but I'd rather not make assumptions.
>
> That's mostly correct, you can sometimes specify 'reasonable' ranges, for
> example ior: 1-5, but you can always use other values as well - they might
> lead to unexpected results though.
>
> Christoph
That's about what I figured, thanks
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"ingo" <ing### [at] tagpovrayorg> wrote in message
news:Xns### [at] povrayorg...
> in news:3d82c9cd@news.povray.org Christopher Johnson wrote:
>
> > I'm looking for a list of valid
>
> Generaly, and this is one of the very nice things in POV-Ray, any value
> is valid, unless specified differently in the documentation
>
> > or most common ranges of values for
>
> The range [0-1] is most used for maps and colors and some aspects of
> finishes.
> For other things like ior, dispersion and normal height etc. a common
> range of values does not make sense.
>
> > parameters in a material/texture block.
>
> In case you want to set values with something like sliders, make them go
> from 0-1 but allow the user to type in other values.
>
>
> Ingo
I was think along those lines but figured it wouldn't hurt to check before I
coded it.
Thanks
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 14 Sep 2002 01:31:41 -0400, "Christopher Johnson"
<age### [at] hotmailcom> wrote:
> I've
> just about finished writing a visual texture editor for the pov3.5 syntax
> but i just need to define bounds on whichever parameters require them.
While others already said that mostly all values are valid I want you propose
something. I have not seen your editor but perhaps you can add in your
application global setting:
[x] Use suggested values.
When it is turned on you can use for validation some file with appropriate
ranges defined. Anybody could change those suggested values for favourite if
the values can be set with scroller or something. For some settings I would
suggest selection lists with predefined named values like for example those
from consts.inc, glass.inc or http://seasoft.tecbox.com/Pov/NewIOR.html.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I had thought about adding predefined names to various settings. My only
problem with that is I've been trying to keep the design section as clean as
possible. It is a possibility though. I think I am going to make the
ranges adjustable via a config file ... just have to play around with some
variations to see what works ,functionally as well as structurally
thanks for the response.
Chris
"ABX" <abx### [at] abxartpl> wrote in message
news:kiuaoucq8l6bp4otf6ntv6gq7s8onfbbc6@4ax.com...
> On Sat, 14 Sep 2002 01:31:41 -0400, "Christopher Johnson"
> <age### [at] hotmailcom> wrote:
> > I've
> > just about finished writing a visual texture editor for the pov3.5
syntax
> > but i just need to define bounds on whichever parameters require them.
>
> While others already said that mostly all values are valid I want you
propose
> something. I have not seen your editor but perhaps you can add in your
> application global setting:
> [x] Use suggested values.
> When it is turned on you can use for validation some file with appropriate
> ranges defined. Anybody could change those suggested values for favourite
if
> the values can be set with scroller or something. For some settings I
would
> suggest selection lists with predefined named values like for example
those
> from consts.inc, glass.inc or http://seasoft.tecbox.com/Pov/NewIOR.html.
>
> ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
