I just downloaded the latest 'experimental build' of POV-Ray, from here (for my
Windows computer)...

https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8431463%2Bav74

I want to make sure that I'm installing it correctly (I downloaded the sse2
version):

It was originally compressed using the '7z' method, so I uncompressed it using
the 7zip app. The only item found in the new folder is the POV-Ray 'engine'
file...  pvengine32-sse2

I understand that it needs to (temporarily) replace v3.7's already-installed
engine file-- which is here (on my machine)... "C:\Program
Files\POV-Ray\v3.7\bin\pvengine32-sse2.exe"

So I moved the *original* pvengine32-sse2 file into a dummy temporary folder
there first (to hide it), then placed the new engine file in the 'bin' folder.

This seems to work OK, but is there any 'hidden detail' that I've neglected to
do? I just want to make sure that I've done the install correctly. Comments?

Post a reply to this message

Am 15.01.2016 um 23:26 schrieb Kenneth:
> I just downloaded the latest 'experimental build' of POV-Ray, from here (for my
> Windows computer)...
> 
> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8431463%2Bav74
> 
> I want to make sure that I'm installing it correctly (I downloaded the sse2
> version):
> 
> It was originally compressed using the '7z' method, so I uncompressed it using
> the 7zip app. The only item found in the new folder is the POV-Ray 'engine'
> file...  pvengine32-sse2
> 
> I understand that it needs to (temporarily) replace v3.7's already-installed
> engine file-- which is here (on my machine)... "C:\Program
> Files\POV-Ray\v3.7\bin\pvengine32-sse2.exe"
> 
> So I moved the *original* pvengine32-sse2 file into a dummy temporary folder
> there first (to hide it), then placed the new engine file in the 'bin' folder.
> 
> This seems to work OK, but is there any 'hidden detail' that I've neglected to
> do? I just want to make sure that I've done the install correctly. Comments?

You've done it precisely the way it's supposed to be done (except that
the official recommendation would be to rename the original .exe, but
moving it to a different directory serves the exact same purpose just as
well).

Post a reply to this message

Thanks! I'm looking forward to trying out the latest fixes and features.

Post a reply to this message

"Kenneth" <kdw### [at] gmailcom> wrote:
> Thanks! I'm looking forward to trying out the latest fixes and features.

You might want to add a note on your download page that the #version number in a
scene needs to be changed to #version 3.71 rather than the 'standard' 3.7, to
make use of the newest features. Of course, that might be obvious to others here
on the newsgroups; but it temporarily fooled me  :-0

Thanks for the hard work you've done!

Post a reply to this message

On 16-1-2016 7:08, Kenneth wrote:
> "Kenneth" <kdw### [at] gmailcom> wrote:
>> Thanks! I'm looking forward to trying out the latest fixes and features.
>
> You might want to add a note on your download page that the #version number in a
> scene needs to be changed to #version 3.71 rather than the 'standard' 3.7, to
> make use of the newest features. Of course, that might be obvious to others here
> on the newsgroups; but it temporarily fooled me  :-0
>

One thing you will notice right away, if you use backslashes to separate 
folders in file names, is a list of parse warnings. It is good policy to 
replace them with forward slashes, and it does not influence parsing in 
lower versions of POV-Ray.

-- 
Thomas

Post a reply to this message

Thanks, Thomas; I didn't know that.

Post a reply to this message

> I just downloaded the latest 'experimental build' of POV-Ray, from here (for my
> Windows computer)...
>
> https://github.com/c-lipka/povray/releases/tag/v3.7.1-alpha.8431463%2Bav74
>
> I want to make sure that I'm installing it correctly (I downloaded the sse2
> version):
>
> It was originally compressed using the '7z' method, so I uncompressed it using
> the 7zip app. The only item found in the new folder is the POV-Ray 'engine'
> file...  pvengine32-sse2
>
> I understand that it needs to (temporarily) replace v3.7's already-installed
> engine file-- which is here (on my machine)... "C:\Program
> Files\POV-Ray\v3.7\bin\pvengine32-sse2.exe"
>
> So I moved the *original* pvengine32-sse2 file into a dummy temporary folder
> there first (to hide it), then placed the new engine file in the 'bin' folder.
>
> This seems to work OK, but is there any 'hidden detail' that I've neglected to
> do? I just want to make sure that I've done the install correctly. Comments?
>
>
>
>
This looks good.
Another possibility would be to create a new folder, named something 
like /Experimental/, and run the experimental version from there.
You can create a distinct shortcut to the experimental version if you wish.
Uberpov use this aproatch.

Post a reply to this message

Am 16.01.2016 um 20:23 schrieb Alain:

> Another possibility would be to create a new folder, named something
> like /Experimental/, and run the experimental version from there.
> You can create a distinct shortcut to the experimental version if you wish.
> Uberpov use this aproatch.

Um... no, UberPOV /per se/ doesn't; the "standard" UberPOV release is
intended to be copied into the same folder as your POV-Ray binary. It
just uses a different filename.

There /is/ a stand-alone release of UberPOV, but that one goes even
further, not only installing into an entirely separate binary folder,
but also using different registry keys, a different folder for include
and sample files, a different master .ini file name, and other such
stuff. Plus, it doesn't even need official POV-Ray to be installed.

Post a reply to this message