Am 21.11.2013 13:01, schrieb James Holsenback:
> On 11/21/2013 06:11 AM, James Holsenback wrote:
>> uberpov --version now at least id's proper
>
> hmmm ... take it back!
>
>> uberpov --version
>> uberpov: cannot open the system configuration file
>> /usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
>> UberPOV 3.7.0.unofficial
>
> shouldn't that be 1.3.7 ... VERSION file in root of build dir has:
>
> 1.37.0.0-alpha
>
> so that means ~uberpov/unix/VERSION is correct ... could it be line 88
> in ~uberpov/source/backend/povray.h ????

No, that line is fine. In some places the program does tell the user 
what official version of POV-Ray it is based on.

Found the culprits though; Git master should be ok now.

Thanks for finding those buggers, I'd probably never have seen them myself.

Post a reply to this message

On 11/21/2013 07:39 AM, clipka wrote:
> Am 21.11.2013 13:01, schrieb James Holsenback:
>> On 11/21/2013 06:11 AM, James Holsenback wrote:
>>> uberpov --version now at least id's proper
>>
>> hmmm ... take it back!
>>
>>> uberpov --version
>>> uberpov: cannot open the system configuration file
>>> /usr/local/etc/uberpov/1.37/uberpov .conf: No such file or directory
>>> UberPOV 3.7.0.unofficial
>>
>> shouldn't that be 1.3.7 ... VERSION file in root of build dir has:
>>
>> 1.37.0.0-alpha
>>
>> so that means ~uberpov/unix/VERSION is correct ... could it be line 88
>> in ~uberpov/source/backend/povray.h ????
>
> No, that line is fine. In some places the program does tell the user
> what official version of POV-Ray it is based on.
>
> Found the culprits though; Git master should be ok now.
>
> Thanks for finding those buggers, I'd probably never have seen them myself.
>

yer welcome ... was it on purpose that I can't view files in uber on 
perforce

Post a reply to this message

On 20-11-2013 18:10, clipka wrote:
> Happy POVing!

This is GREAT!

I am now playing around with the sample scene files before trying out on 
my own scenes, but it looks fantastic.

Keep up the good work!

Thomas

Post a reply to this message

On 11/21/2013 07:39 AM, clipka wrote:
> Am 21.11.2013 13:01, schrieb James Holsenback:
> Found the culprits though; Git master should be ok now.

uberpov --version
uberpov: cannot open the user configuration file 
/home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
UberPOV 1.37.0.0-alpha


OK ... id's proper now. uberpov.conf made it to 
/usr/local/etc/uberpov/1.37/ but nada in users .uberpov directory

Post a reply to this message

Am 21.11.2013 13:50, schrieb James Holsenback:

> yer welcome ... was it on purpose that I can't view files in uber on
> perforce

Of course. I wouldn't want /you/ sniffing around in there ;-)

Seriously, I have no idea how I'd even be able to change the permissions.

Post a reply to this message

Am 21.11.2013 14:30, schrieb James Holsenback:
> On 11/21/2013 07:39 AM, clipka wrote:
>> Am 21.11.2013 13:01, schrieb James Holsenback:
>> Found the culprits though; Git master should be ok now.
>
> uberpov --version
> uberpov: cannot open the user configuration file
> /home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
> UberPOV 1.37.0.0-alpha
>
>
> OK ... id's proper now. uberpov.conf made it to
> /usr/local/etc/uberpov/1.37/ but nada in users .uberpov directory

Did you make install?

If not, then this is to be expected.

Post a reply to this message

Am 21.11.2013 14:51, schrieb clipka:
> Am 21.11.2013 14:30, schrieb James Holsenback:
>> On 11/21/2013 07:39 AM, clipka wrote:
>>> Am 21.11.2013 13:01, schrieb James Holsenback:
>>> Found the culprits though; Git master should be ok now.
>>
>> uberpov --version
>> uberpov: cannot open the user configuration file
>> /home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
>> UberPOV 1.37.0.0-alpha
>>
>>
>> OK ... id's proper now. uberpov.conf made it to
>> /usr/local/etc/uberpov/1.37/ but nada in users .uberpov directory
>
> Did you make install?
>
> If not, then this is to be expected.

Uh... forget that statement. If you hadn't done make install, there 
would be nothing in /usr/local/etc..., would there.

But it also means you installed as root; could there possibly be an 
.uberpov directory now in the root's home directory?

What does POV-Ray proper do in that situation, anyway?

Post a reply to this message

Am 21.11.2013 14:30, schrieb James Holsenback:
> On 11/21/2013 07:39 AM, clipka wrote:
>> Am 21.11.2013 13:01, schrieb James Holsenback:
>> Found the culprits though; Git master should be ok now.
>
> uberpov --version
> uberpov: cannot open the user configuration file
> /home/ash/.uberpov/1.37/uberpov.conf: No such file or directory
> UberPOV 1.37.0.0-alpha

As a side note, this message is just a warning; UberPOV should be able 
to run just fine without a ~/.uberpov/1.37/uberpov.conf, except that it 
prints this message. Same as POV-Ray does when it misses its 
~/.povray/3.7/povray.conf file.

You might want to check though whether UberPOV accidently wrote an 
uberpov.conf somewhere into ~/.povray, or even replaced POV-Ray's .conf 
file. That would be seriously bad.

Post a reply to this message