  | 
  | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
povray emits 120 lines of text per render, and not a one of them tells 
me which of my 21 copies of povray.ini it is reading. :(
I booted Windows, and am trying to change my default size from 800x600 
to 720x480.
-- 
dik
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
Le 18-03-08 à 15:50, dick balaska a écrit :
> povray emits 120 lines of text per render, and not a one of them tells 
> me which of my 21 copies of povray.ini it is reading. :(
> 
> I booted Windows, and am trying to change my default size from 800x600 
> to 720x480.
> 
It use the one found in :
/Users/%CurrentUser%/My documents/POV-Ray/v3.7/ini
You can safely delete those located anywhere else.
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
Am 08.03.2018 um 21:50 schrieb dick balaska:
> povray emits 120 lines of text per render, and not a one of them tells
> me which of my 21 copies of povray.ini it is reading. :(
> 
> I booted Windows, and am trying to change my default size from 800x600
> to 720x480.
Try the "Edit master POVRAY.INI" menu item from the "Tools" menu.
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
Am 2018-03-08 21:19, also sprach clipka:
> Am 08.03.2018 um 21:50 schrieb dick balaska:
>> povray emits 120 lines of text per render, and not a one of them tells
>> me which of my 21 copies of povray.ini it is reading. :(
>>
>> I booted Windows, and am trying to change my default size from 800x600
>> to 720x480.
> 
> Try the "Edit master POVRAY.INI" menu item from the "Tools" menu.
> 
I thought of that.  If only qtpov had such a thing. ;)
I thought of changing povconsole.exe (per se, actually povrayws64.exe) 
to tell me the location of the master .ini with the version command so I 
can get at that.
BTW, I stopped working on the integration of qtpov/povray because I have 
a leak in my povrayws64.exe.  That leak will exist after the 
integration, so I thought to tackle it first.  Prior to noticing the 
leak, I upgraded from Qt 5.9 to 5.10 and valgrind died. :(  So I have no 
easy way of chasing that down. I keep upgrading hoping one of these 
times it fixes valgrind.  google tells me I am the only person that 
valgrind crashes on startup since 2006.
It seems that my leak is Linux only. I wondered, because povwin doesn't 
leak.  I think that's somehow a clue.
-- 
dik
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   |