Whe I say

display=1

in my povray.ini file on my SGI octane (well mine as long as I'm here:)
I don't get the picture being rendered on the display, but the file
seems outputeed fine, any hints from SGI POV users?

Post a reply to this message

Maneesh Yadav wrote:
> 
> Whe I say
> 
> display=1
> 
> in my povray.ini file on my SGI octane (well mine as long as I'm here:)
> I don't get the picture being rendered on the display, but the file
> seems outputeed fine, any hints from SGI POV users?

Never use a ini file. Try the command line. Something like:

x-povray +imyfile.pov +l/here/are my/includes +d +v +w400 +h300 +x +p
+a0.3

It works for my O2 under IRIX 6.3


All the Best,

Marc
-- 
Marc Schimmler

Post a reply to this message

Marc Schimmler <sch### [at] icauni-stuttgartde> wrote:
: Never use a ini file.

  Why not? It helps a lot. You can put all those parameters you always use
inside povray.ini (like +l... +d +v +x +p) and so you don't have to type them
all the time.
  Of course the povray.ini has to be in the working directory...
  I don't remember if you can copy povray.ini to .povray in your home
directory...

: x-povray +imyfile.pov +l/here/are my/includes +d +v +w400 +h300 +x +p
: +a0.3

  With a proper povray.ini you could type only:

x-povray -i myfile -w400 -h300 +a

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Mika wrote:
> 
> Marc Schimmler <sch### [at] icauni-stuttgartde> wrote:
> : Never use a ini file.
> 
>   Why not? It helps a lot. You can put all those parameters you always use
> inside povray.ini (like +l... +d +v +x +p) and so you don't have to type them
> all the time.
>   Of course the povray.ini has to be in the working directory...
>   I don't remember if you can copy povray.ini to .povray in your home
> directory...
> 
> : x-povray +imyfile.pov +l/here/are my/includes +d +v +w400 +h300 +x +p
> : +a0.3
> 
>   With a proper povray.ini you could type only:
> 
> x-povray -i myfile -w400 -h300 +a
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

I often play around with parameters. Could be anti-aliasing, resolution
or the mosaic size. I would have to change the parameters inside the
ini-file, so most of the time I just bring back the last command in the
shell with one keystroke and the change the variable. I found it more
comfortable (I tried the ini-file). It's easier than to have another
editor open (which is annoying on my small 15" monitor at home). It just
works fine for me.

Marc
-- 
Marc Schimmler

Post a reply to this message

Marc Schimmler <sch### [at] icauni-stuttgartde> wrote:
: I often play around with parameters. Could be anti-aliasing, resolution
: or the mosaic size. I would have to change the parameters inside the
: ini-file, so most of the time I just bring back the last command in the
: shell with one keystroke and the change the variable.

  I really don't understand what are you talking about.

  Are you aware that any setting you set in the command line will override
the one in the ini file? And that you can have settings in the ini file _AND_
the command line?
  For example, if your povray.ini file have these parameters:

-w160 -h120 +d +v +p +x +b50

and you now type this command:

x-povray -i scene -w320 -h240 +a0.1

povray will then render the image using these settings:

-i scene -w320 -h240 +a0.1 +d +v +p +x +b50

  Moreover, if you want to turn _off_ some parameter, you can do it using
'-' instead of '+'. For example, if you don't want to display the image,
you can specify the option '-d' at the command line and the image will not
be displayed regardless of your ini file settings.

  It surely is a _lot_ more comfortable to have the common settings which
you always use into povray.ini and specify only the ones that change all
the time at the command line.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Mika wrote:
> 
> Marc Schimmler <sch### [at] icauni-stuttgartde> wrote:
> : I often play around with parameters. Could be anti-aliasing, resolution
> : or the mosaic size. I would have to change the parameters inside the
> : ini-file, so most of the time I just bring back the last command in the
> : shell with one keystroke and the change the variable.
> 
>   I really don't understand what are you talking about.
> 
>   Are you aware that any setting you set in the command line will override
> the one in the ini file? And that you can have settings in the ini file _AND_
> the command line?
>   For example, if your povray.ini file have these parameters:
> 
> -w160 -h120 +d +v +p +x +b50
> 
> and you now type this command:
> 
> x-povray -i scene -w320 -h240 +a0.1
> 
> povray will then render the image using these settings:
> 
> -i scene -w320 -h240 +a0.1 +d +v +p +x +b50
> 
>   Moreover, if you want to turn _off_ some parameter, you can do it using
> '-' instead of '+'. For example, if you don't want to display the image,
> you can specify the option '-d' at the command line and the image will not
> be displayed regardless of your ini file settings.
> 
>   It surely is a _lot_ more comfortable to have the common settings which
> you always use into povray.ini and specify only the ones that change all
> the time at the command line.
> 

No, I had not been aware of the override mode which is indeed nice but
from my experience common settings can bring in you in trouble very fast
if you are not always aware what your settings are.

Marc 
-- 
Marc Schimmler

Post a reply to this message

Marc Schimmler wrote:

> No, I had not been aware of the override mode which is indeed nice but
> from my experience common settings can bring in you in trouble very fast
> if you are not always aware what your settings are.
> 
> Marc
> --
> Marc Schimmler

   Although I am using the windows build and in consequence don't
bother with the command line one thing I do like is to maintain the
same default settings for almost all of my scenes. It is comforting to
know that when I type something into a scene file and hit the render button
I pretty much know exactly how it will appear. If you play with a bunch
of command line options every time you render a scene you are not going
to be as certain a particular piece of code will work the same in every
scene or each time you render the same file.
  I like continuity. About the only thing I set differently is the render
resolution and the aa settings whether on or off and what level. These
are all contained in an ini file and can be choosen from a drop down menu.
Life is tough in the windows version :)
  Even when I was using v2.2 in dos I had my favorite .def files I used
repeatedly and they were pretty much short cuts to the way I use the windows
version now. This was before any kind of .ini file was supported by the
program.

-- 
Ken Tyler
  
mailto://tylereng@pacbell.net
http://home.pacbell.net/tylereng/links.htm

Post a reply to this message

Likewise here, back in the *.def file days I had (archived away now)
about three dozen different ones to do various resolutions with or
without aa and the same for animations of many typical frame numbers,
etc. All these *.def files were used on the command-line and I too used
over-riding of the parameters if need be.
With the change over to *.ini files I did the same and am pretty sure
others must also since it is the quickest way to a specific type of
render.
What was this original topic again? Oh yeah, "display=1" not making a
image onscreen. No idea why not ;)


Ken wrote:
> 
>   Even when I was using v2.2 in dos I had my favorite .def files I used
> repeatedly and they were pretty much short cuts to the way I use the windows
> version now. This was before any kind of .ini file was supported by the
> program.
> 

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto://inversez@aol.com?Subject=PoV-News

Post a reply to this message

Marc Schimmler <sch### [at] icauni-stuttgartde> wrote:
: No, I had not been aware of the override mode which is indeed nice but
: from my experience common settings can bring in you in trouble very fast
: if you are not always aware what your settings are.

  I have always used default settings in povray.ini for all and everyone of
my scenes and I have _never_ got into trouble. I know what I want and I use.
It would be a real pain if I had to type every option every time in the
command line.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
:    Although I am using the windows build and in consequence don't
: bother with the command line

  Actually the command line field is very handy (to me at least). I don't
even know where do you set the antialiasing level, mosaic preview, radiosity
rendering, etc. It's just easier to type all those in the command line
field.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Mika wrote:
> 
> Ken <tyl### [at] pacbellnet> wrote:
> :    Although I am using the windows build and in consequence don't
> : bother with the command line
> 
>   Actually the command line field is very handy (to me at least). I don't
> even know where do you set the antialiasing level, mosaic preview, radiosity
> rendering, etc. It's just easier to type all those in the command line
> field.

I set up my antialiasing level in the secondary tools .ini file, I don't use
mosaic preview, and the radiosity I turn on in the master povray.ini file with
a single line that say's radiosity = on. When not in use I comment it out.

-- 
Ken Tyler
  
mailto://tylereng@pacbell.net
http://home.pacbell.net/tylereng/links.htm

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
: I set up my antialiasing level in the secondary tools .ini file, I don't use
: mosaic preview, and the radiosity I turn on in the master povray.ini file with
: a single line that say's radiosity = on. When not in use I comment it out.

  It surely is easier to modify the command line field than the .ini file...
I choose the command line field. :)

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Mika wrote:
> 
>   I have always used default settings in povray.ini for all and everyone of
> my scenes and I have _never_ got into trouble. I know what I want and I use.
> It would be a real pain if I had to type every option every time in the
> command line.
> 

I don't retype every option. I just get the last povray command from the
history and alter the command line from render to render as needed.

Marc

Post a reply to this message

Marc Schimmler <mar### [at] icauni-stuttgartde> wrote:
: I don't retype every option. I just get the last povray command from the
: history and alter the command line from render to render as needed.

  But you have to retype them every time you start using povray.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Mika wrote:
> 
> Marc Schimmler <mar### [at] icauni-stuttgartde> wrote:
> : I don't retype every option. I just get the last povray command from the
> : history and alter the command line from render to render as needed.
> 
>   But you have to retype them every time you start using povray.
> 

On my Linux at home the history is stored so I can recall the last
render there. I haven't managed this under IRIX 6.3 so that's true in
one case. 
But it's just a line. :-)

Marc
-- 
Marc Schimmler

Post a reply to this message

Marc Schimmler wrote:
> 
> Nieminen Mika wrote:
> >
> > Marc Schimmler <mar### [at] icauni-stuttgartde> wrote:
> > : I don't retype every option. I just get the last povray command from the
> > : history and alter the command line from render to render as needed.
> >
> >   But you have to retype them every time you start using povray.
> >
> 
> On my Linux at home the history is stored so I can recall the last
> render there. I haven't managed this under IRIX 6.3 so that's true in
> one case.
> But it's just a line. :-)
> 
> Marc
> --
> Marc Schimmler

I'll save you guy's some time here:

Warp: Yes !
Marc:  No !

Warp: Why !
Marc: Because !

Warp: Yes !
Marc:  No !

Warp: Why !
Marc: Because !

Warp: Yes !
Marc:  No !

Warp: Why !
Marc: Because !

Warp: Yes !
Marc:  No !

Warp: Why !
Marc: Because !

Warp: Yes !
Marc:  No !

Warp: Yes !
Marc:  No !

Warp: Why !
Marc: Because !

Warp: Yes !
Marc:  No !

-- 
Ken Tyler
  
mailto://tylereng@pacbell.net
http://home.pacbell.net/tylereng/links.htm

Post a reply to this message

No! :-)

Marc
-- 
Marc Schimmler

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
: I'll save you guy's some time here:

: Warp: Yes !
: Marc:  No !

  I would like to comment that I am right and he is wrong ;)

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Just to add to an increasingly lengthy thread here, I have DOSKEY loaded
to move around in the commandline history. Does quite well for ease of
redoing past things, I just haven't used the povray.exe for some time
now. However it gets plenty of use while using these DOS utilities and
programs I have here.


Nieminen Mika wrote:
> 
> Ken <tyl### [at] pacbellnet> wrote:
> : I'll save you guy's some time here:
> 
> : Warp: Yes !
> : Marc:  No !
> 
>   I would like to comment that I am right and he is wrong ;)
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

-- 
 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 <inv### [at] aolcom> wrote:
: Just to add to an increasingly lengthy thread here, I have DOSKEY loaded
: to move around in the commandline history. Does quite well for ease of
: redoing past things, I just haven't used the povray.exe for some time
: now. However it gets plenty of use while using these DOS utilities and
: programs I have here.

  Doskey doesn't store its history in a file, so you still have to type all
the parameters every time.
  What's the big deal with the povray.ini-file anyways? I don't see the
problem.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Um, yes, everytime the computer is restarted doskey resets. Good for the
duration of the session though. All I need do is tap the up or down
arrow keys, then the left/right arrow keys to move into and edit a
previously used command line.
About the INIs, I have one to do most anything that is common and others
that I edited for custom setups.


Nieminen Mika wrote:
> 
> Bob Hughes <inv### [at] aolcom> wrote:
> : Just to add to an increasingly lengthy thread here, I have DOSKEY loaded
> : to move around in the commandline history. Does quite well for ease of
> : redoing past things, I just haven't used the povray.exe for some time
> : now. However it gets plenty of use while using these DOS utilities and
> : programs I have here.
> 
>   Doskey doesn't store its history in a file, so you still have to type all
> the parameters every time.
>   What's the big deal with the povray.ini-file anyways? I don't see the
> problem.
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

-- 
 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 <inversez> wrote:
: Um, yes, everytime the computer is restarted doskey resets. Good for the
: duration of the session though. All I need do is tap the up or down
: arrow keys, then the left/right arrow keys to move into and edit a
: previously used command line.

  Tip: If your command is very far, you can use a shortcut to get it faster:
Type the beginning of the command and press F8.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Hey thanks, didn't know that. I don't read things about Doskey inner
workings and that's more than I ever thought it could do as it seems
rather limited in functionality.


Nieminen Mika wrote:
> 
> Bob Hughes <inversez> wrote:
> : Um, yes, everytime the computer is restarted doskey resets. Good for the
> : duration of the session though. All I need do is tap the up or down
> : arrow keys, then the left/right arrow keys to move into and edit a
> : previously used command line.
> 
>   Tip: If your command is very far, you can use a shortcut to get it faster:
> Type the beginning of the command and press F8.
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

-- 
 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 <inversez> wrote:
: Hey thanks, didn't know that. I don't read things about Doskey inner
: workings and that's more than I ever thought it could do as it seems
: rather limited in functionality.

  I recommend you to read the help text on doskey. You can also make alias
commands with it.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message