I am running Windows Ultimate 7, 64 bit on a dual CPU computer.  I already have
PovRay 3.5 installed in a Architectural program.

Do I uninstall the old PovRay 3.5 in the Architectural program first and then
install the updated version "PovWin362-64bit.msi," or can I install the update
over top of the old one?

Which update is best for this system, the PovWin362-64bit.msi or the Beta
Pov-Ray 3.7 for Windows?

Are the Pov-Ray 3.7 for Windows 32 or 64 bits?

Appreciate any help I can get. ;-)

ahed

Post a reply to this message

ahed wrote:

> Do I uninstall the old PovRay 3.5 in the Architectural program first and then
> install the updated version "PovWin362-64bit.msi," or can I install the update
> over top of the old one?

You can uninstall 3.5 or you can keep them side-by-side. If the
architectural program expects 3.5 to be installed it will likely
not work with newer versions.

> Which update is best for this system, the PovWin362-64bit.msi or the Beta
> Pov-Ray 3.7 for Windows?

Definitely 3.7, it will make best use of your dual CPU for rendering

> Are the Pov-Ray 3.7 for Windows 32 or 64 bits?

Both are available at http://www.povray.org/beta/

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> ahed wrote:
>
> > Do I uninstall the old PovRay 3.5 in the Architectural program first and then
> > install the updated version "PovWin362-64bit.msi," or can I install the update
> > over top of the old one?
>
> You can uninstall 3.5 or you can keep them side-by-side. If the
> architectural program expects 3.5 to be installed it will likely
> not work with newer versions.
>
> > Which update is best for this system, the PovWin362-64bit.msi or the Beta
> > Pov-Ray 3.7 for Windows?
>
> Definitely 3.7, it will make best use of your dual CPU for rendering
>
> > Are the Pov-Ray 3.7 for Windows 32 or 64 bits?
>
> Both are available at http://www.povray.org/beta/

Thanks for your reply,

If I keep the 3.5 installed in the architectural program, should I install the
3.7 in the same directory or install it in a separate directory, and if I
install in a separate directory, do you think the architectural program will be
able to access the 3.7?

Thanks again for you help, really appreciated

Ahed

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> ahed wrote:
>
> > Do I uninstall the old PovRay 3.5 in the Architectural program first and then
> > install the updated version "PovWin362-64bit.msi," or can I install the update
> > over top of the old one?
>
> You can uninstall 3.5 or you can keep them side-by-side. If the
> architectural program expects 3.5 to be installed it will likely
> not work with newer versions.
>
> > Which update is best for this system, the PovWin362-64bit.msi or the Beta
> > Pov-Ray 3.7 for Windows?
>
> Definitely 3.7, it will make best use of your dual CPU for rendering
>
> > Are the Pov-Ray 3.7 for Windows 32 or 64 bits?
>
> Both are available at http://www.povray.org/beta/


Thanks for your reply,

If I keep the 3.5 installed in the architectural program, should I install the
3.7 in the same directory or install it in a separate directory, and if I
install in a separate directory, do you think the architectural program will be
able to access the 3.7?

Thanks again for you help, really appreciated

Ahed

Post a reply to this message

On 03/02/2012 8:13 PM, ahed wrote:
> Thanks for your reply,
>
> If I keep the 3.5 installed in the architectural program, should I install the
> 3.7 in the same directory or install it in a separate directory, and if I
> install in a separate directory, do you think the architectural program will be
> able to access the 3.7?

Does your architectural program use the PovRay GUIExtensions which is 

version of 3.7.
I would install 3.7 in a separate dictionary and point your 
architectural program to that exe.
What I did to get Bishop3D to work with PovRay was: Install 3.7 64bit, 
then copy the bin folder somewhere. Uninstall the 64 bit version, then 
install the 32 bit version of 3.7 and set up the PovRay GUIExtensions 
for that. That means Bishop3D will use PovRay 3.7 for rendering. But I 
can still start the 64 bit version manually and load the INI file to 
render the scene if I want.
Remember that if your architectural program is designed to use PovRay 
3.5 the syntax is slightly different in 3.7 and you may need to modify 
the generated Pov file to take full advantage of PovRay 3.7


-- 
Regards
     Stephen

Post a reply to this message

Stephen <mcavoys_at@aoldotcom> wrote:
> On 03/02/2012 8:13 PM, ahed wrote:
> > Thanks for your reply,
> >
> > If I keep the 3.5 installed in the architectural program, should I install the
> > 3.7 in the same directory or install it in a separate directory, and if I
> > install in a separate directory, do you think the architectural program will be
> > able to access the 3.7?
>
> Does your architectural program use the PovRay GUIExtensions which is

> version of 3.7.
> I would install 3.7 in a separate dictionary and point your
> architectural program to that exe.
> What I did to get Bishop3D to work with PovRay was: Install 3.7 64bit,
> then copy the bin folder somewhere. Uninstall the 64 bit version, then
> install the 32 bit version of 3.7 and set up the PovRay GUIExtensions
> for that. That means Bishop3D will use PovRay 3.7 for rendering. But I
> can still start the 64 bit version manually and load the INI file to
> render the scene if I want.
> Remember that if your architectural program is designed to use PovRay
> 3.5 the syntax is slightly different in 3.7 and you may need to modify
> the generated Pov file to take full advantage of PovRay 3.7
>
>
> --
> Regards
>      Stephen

This is what in the Povray directory inside the architectural program:

PovRay - ini - PVEngine.INI and pvtools =
  ------------------
PVEngine.ini =

[Permitted Input Paths]
1=%INSTALLDIR%
2=C:\WINNT\Fonts

[Permitted Output Paths]
1=%INSTALLDIR%\Renderer\ReRun
2=%INSTALLDIR%\Insert Menu

[General]
CheckNewVersion=0
SendSystemInfo=0
  --------------
No sign of "PovRay GUIExtensions".

I played around a little and installed the 3.7 win64 bit, where it wanted to go
then I removed the 3.5 and replased it with a copy of 3.7.  The architectural
program is still working. ;-)

I am looking forward to learning to use the PovRay 3.7, at this point I don't
know if it is working or not, as I never heard about this program before.

Have a great weekend

aned

Post a reply to this message

On 04/02/2012 9:24 PM, ahed wrote:
> No sign of "PovRay GUIExtensions".
>
> I played around a little and installed the 3.7 win64 bit, where it wanted to go
> then I removed the 3.5 and replased it with a copy of 3.7.  The architectural
> program is still working.;-)
>
> I am looking forward to learning to use the PovRay 3.7, at this point I don't
> know if it is working or not, as I never heard about this program before.
>
> Have a great weekend

Thank you and have a good weekend yourself.
You have come to the right place to learn about PovRay.

As you probably know PovRay only renders your image from a sctipt 
generated by your architectural program. Which one is it by the way?
The entry in [GUIExtensions] allows your program to start PovRay and to 
tell it which file to parse and render. My entry is:

[GUIExtensions]
UseExtensions=1

ExtDll17=C:\Program Files (x86)\Bishop3D\Bishop3DPovComm.dll
ExtDll18=C:\Graphics\Moray For Windows\MorayCtrl.DLL

This allows the modellers Bishop3D and Moray to communicate with PovRay.
Both of these programs amend the pvengine.ini file when they are 
installed or via their preferences or settings menu.

If you have any questions to not hesitate to ask

-- 
Regards
     Stephen

Post a reply to this message