On 4/7/2012 4:11 PM, Stephen wrote:
> On 07/04/2012 10:03 PM, peter puzzelaar wrote:
>> Hope that this input is of some help
>
> I have a vague feeling that I have had a similar problem. In Pov3.5 can
> you go into the Tools menu and open Povray.ini and pvengin.ini?
>
> Otherwise, unless someone else can suggest a more direct method.
> I would uninstall all versions of PovRay and Moray.
> Install Pov 3.5 then install Moray and let Moray do its thing to connect
> to Pov 3.5.

> still does not work you might have to clean up the registry.
>
> After you get Moray and PovRay talking and rendering you can re-install
> Pov 3.6 and 3.7 if you want.
>
>
I have always felt that there needs to be a saner link between those 
things. Like, have POVRay listen on localhost for an FTP, then send the 
file to it that way, or something, so your are not trying to save the 
file some place, then tell POVRay where to look, and hoping things don't 
break. Since it would end up where it should in the first place, the 
problem goes away. Same with basic communications between them. The 
method used now is fiddly, impossible to adapt to another application 
(unless you can write the "specialized" communication module for that 
new application), requires a DLL to be plugged in, and breaks, if 
anything changes in either application, which mucks with the 
communications. An actual communication method, documented, and not 
reliant on "one-off" solutions would seem to be more adaptable.

There just has to be a more stable way to do it. imho

Post a reply to this message