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