 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I cant get POV to find my image maps, further I have no clue why.
Can somone explain to me what exactly I have to do to make this work?
the path for my image maps is : C:\Program Files\POV-Ray for Windows
v3.1\User\Image maps. What do I have to do to the .INI file and on the
command line? is therer anthing else I need to do?
While Im here I want to make the sky fade from blue to black as it goes
up. How is this accomplished?
-Drew
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Drew wrote:
>
> I cant get POV to find my image maps, further I have no clue why.
> Can somone explain to me what exactly I have to do to make this work?
> the path for my image maps is : C:\Program Files\POV-Ray for Windows
> v3.1\User\Image maps. What do I have to do to the .INI file and on the
> command line? is therer anthing else I need to do?
Open pov and choose the tools menu. Select edit master povray.ini.
Add the following line to the bottom of the ini file
Library_Path=C:\Program Files\POV-Ray for Windows v3.1\User\Image maps
Don't worry if there is already another Library_Path= statement in
the file. Just add yours below it and then re-start the program.
It should now search for your image in that directory before giving
up and asking you where it is.
You can also include a path in your image map statement like this:
pigment {
image_map { tga "c:\pov\includes\images\Image.tga" }
}
> While Im here I want to make the sky fade from blue to black as it goes
> up. How is this accomplished?
> -Drew
A simple gradient pigment pattern will accomplish this for you.
sky_sphere {
pigment { gradient y
color_map {
[0 rgb < 0, 0, 1 >]
[1 rgb < 0, 0, 0 >]
}
}
}
Also look in the docs under the tutorial section describing the use of
sky spheres. It contains more examples and some of the different options
you should be aware of.
Regards,
--
Ken Tyler
mailto://tylereng@pacbell.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I recently had a library path problem too so I'm interested
in any response you may get.
As far as fading from black to blue try "gradient". There's
an example in:
Insert->Ready Made Scenes->Basic Scene
The sky sphere goes from blue to white.
--
...coffee?...yes please! extra sugar,extra cream...Thank you.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just to make a note here. I've used more than 10 library paths and have
been able to use any new additional path once the Povray.ini has been
edited and saved without need to close and restart POV-Ray for Windows
v3.1e. The Scene help file says library paths are limited to 10 and
appears to be in error about this.
Anyone care to acknowledge this?
Ken wrote:
>
> Open pov and choose the tools menu. Select edit master povray.ini.
>
> Add the following line to the bottom of the ini file
>
> Library_Path=C:\Program Files\POV-Ray for Windows v3.1\User\Image maps
>
> Don't worry if there is already another Library_Path= statement in
> the file. Just add yours below it and then re-start the program.
> It should now search for your image in that directory before giving
> up and asking you where it is.
>
> You can also include a path in your image map statement like this:
>
> pigment {
> image_map { tga "c:\pov\includes\images\Image.tga" }
> }
>
> --
> Ken Tyler
>
> mailto://tylereng@pacbell.net
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/homepage.htm
mailto://inversez@aol.com?Subject=PoV-News
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob Hughes wrote:
>
> Just to make a note here. I've used more than 10 library paths and have
> been able to use any new additional path once the Povray.ini has been
> edited and saved without need to close and restart POV-Ray for Windows
> v3.1e. The Scene help file says library paths are limited to 10 and
> appears to be in error about this.
> Anyone care to acknowledge this?
If by that you mean you want me to add more than ten library paths
to my ini file and then design a scene that will use one source file
from each directory just to back up you statement I would like to go
on record as saying I support you on this without feeling a need to
verify it thank you very much.
Perhaps that was/is a limitation with Win 3.0 and the newer win 95/98
have no such bottlenecks built in. Or maybe not.
--
Ken Tyler
mailto://tylereng@pacbell.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>been able to use any new additional path once the Povray.ini has been
>edited and saved without need to close and restart POV-Ray for Windows
>v3.1e.
I believe I typed everything in correctly, but the additional
pathname didn't work for me.
Restart? I didn't think to do that. I'll have to try again and see what
happens.
--
...coffee?...yes please! extra sugar,extra cream...Thank you.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yes, it's true. More than 10 Library_Path= lines works. I just had to test
this out to be positive. I created 12 new folders each with it's own
include file containing a 'text' statement of the numbers 1 thru 12 and
then forgot I had to also have the path to my fonts as well so they
totaled 13 in all. POV-Ray 3.1e has no problem using that many and I was
thinking I had heard 20 was the new limit, however I'm satisfied with the
13 paths possible so far. Oh, and no restarting of POV-Ray either, just
the saving of Povray.ini does fine.
Ken wrote:
>
> Bob Hughes wrote:
> >
> > Just to make a note here. I've used more than 10 library paths and have
> > been able to use any new additional path once the Povray.ini has been
> > edited and saved without need to close and restart POV-Ray for Windows
> > v3.1e. The Scene help file says library paths are limited to 10 and
> > appears to be in error about this.
> > Anyone care to acknowledge this?
>
> If by that you mean you want me to add more than ten library paths
> to my ini file and then design a scene that will use one source file
> from each directory just to back up you statement I would like to go
> on record as saying I support you on this without feeling a need to
> verify it thank you very much.
>
> Perhaps that was/is a limitation with Win 3.0 and the newer win 95/98
> have no such bottlenecks built in. Or maybe not.
>
> --
> Ken Tyler
>
> mailto://tylereng@pacbell.net
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/homepage.htm
mailto://inversez@aol.com?Subject=PoV-News
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob Hughes wrote:
>
> Yes, it's true. More than 10 Library_Path= lines works. I just had to test
> this out to be positive. I created 12 new folders each with it's own
> include file containing a 'text' statement of the numbers 1 thru 12 and
> then forgot I had to also have the path to my fonts as well so they
> totaled 13 in all. POV-Ray 3.1e has no problem using that many and I was
> thinking I had heard 20 was the new limit, however I'm satisfied with the
> 13 paths possible so far. Oh, and no restarting of POV-Ray either, just
> the saving of Povray.ini does fine.
I am glad you were able to confirm that. I know intuitively that changes
to the master povray.ini file needs no restart as it is read each time
a render is started. The same is not true of the secondary.ini file which
I do on occasion edit to add or remove graphic resolutions and AA settings
for unique circumstances. It seems to be read into memory and forgotton
until you close the program and restart. This is evidenced by the glaring
ommision of changes made to the file in the drop down resolution menu.
--
Ken Tyler
mailto://tylereng@pacbell.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 06 May 1999 03:02:50 -0500, Bob Hughes <inv### [at] aol com> wrote:
>Yes, it's true. More than 10 Library_Path= lines works. I just had to test
>this out to be positive. I created 12 new folders each with it's own
>include file containing a 'text' statement of the numbers 1 thru 12 and
>then forgot I had to also have the path to my fonts as well so they
>totaled 13 in all. POV-Ray 3.1e has no problem using that many and I was
>thinking I had heard 20 was the new limit, however I'm satisfied with the
>13 paths possible so far. Oh, and no restarting of POV-Ray either, just
>the saving of Povray.ini does fine.
Looking at povray.h for the 3.1e source code, I see that the limit has
been raised to 25.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Look what I found !
This quote is from the section "Using INI files" of the scene docs:
"The only exception is the +L switch for setting library paths. Up to ten
unique paths may be specified."
And this quote comes from "Library Path" the Parsing Options section :
"Up to twenty unique paths may be specified."
Can we assume that 10 is the limit in a command line and 20 in an povray.ini
? The remaining five (according to the source and Mr.. Parker) could they be
for extra paths in extra .ini/command line options that we choose to make ?
>Yes, it's true. More than 10 Library_Path= lines works. I just had to test
>this out to be positive. I created 12 new folders each with it's own
>include file containing a 'text' statement of the numbers 1 thru 12 and
>then forgot I had to also have the path to my fonts as well so they
>totaled 13 in all. POV-Ray 3.1e has no problem using that many and I was
>thinking I had heard 20 was the new limit, however I'm satisfied with the
>13 paths possible so far. Oh, and no restarting of POV-Ray either, just
>the saving of Povray.ini does fine.
>
>
>Ken wrote:
>>
>> Bob Hughes wrote:
>> >
>> > Just to make a note here. I've used more than 10 library paths and have
>> > been able to use any new additional path once the Povray.ini has been
>> > edited and saved without need to close and restart POV-Ray for Windows
>> > v3.1e. The Scene help file says library paths are limited to 10 and
>> > appears to be in error about this.
>> > Anyone care to acknowledge this?
>>
>> If by that you mean you want me to add more than ten library paths
>> to my ini file and then design a scene that will use one source file
>> from each directory just to back up you statement I would like to go
>> on record as saying I support you on this without feeling a need to
>> verify it thank you very much.
>>
>> Perhaps that was/is a limitation with Win 3.0 and the newer win 95/98
>> have no such bottlenecks built in. Or maybe not.
>>
>> --
>> Ken Tyler
>>
>> mailto://tylereng@pacbell.net
>
>--
> omniVERSE: beyond the universe
> http://members.aol.com/inversez/homepage.htm
> mailto://inversez@aol.com?Subject=PoV-News
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
