Alain wrote:

> Any path with at least a space in it MUST be enclosed on quotes. 
> Otherwise, the spaces are treated as separators.
> 

So that's how it works, Thanks Alain

-- 

Best Regards,
	Stephen

Post a reply to this message

> Alain wrote:
>
>> Any path with at least a space in it MUST be enclosed on quotes.
>> Otherwise, the spaces are treated as separators.
>>
>
> So that's how it works, Thanks Alain
>

That's the way it works for any ini files,not just POV-Ray's ones.
It's also the rule for shortcuts and registry entries to files and 
applications.

It goes back to the good old days of DOS and the 8.3 naming convention 
when spaces where not allowed at all in any file name.


Alain

Post a reply to this message

Thanks!

Alain <aze### [at] qwertyorg> wrote:

> >    I am getting nowhere.
> >    *** copy of the last section of my POVRAY.INI ***
> > ; Specify path to search for any files not found in current
> > ; directory.  Up to 10 such paths may be specified.
> > ; These were added by the install process with your installation
> > ; drive and directory already patched in.
> > ;
> >
> > Library_Path=G:\PGLTECH\Lifter Docs\
> > Library_Path=G:\WINNT\Fonts
> > Library_Path=G:\Program Files\POV-Ray for Windows v3.5\INCLUDE
> > ;SourceFile=G:\PGLTECH\Lifter Docs\build.pov ;; Unknown option, tries to open
> > THIS file
> > ;Input_File_Name=G:\PGLTECH\Lifter Docs\build.pov ;; makes zero difference
> > ;Input_File_Name=build.pov ;; makes zero difference
> > ; ** This file is G:\Program Files\POV-Ray for Windows v3.5\renderer\POVRAY.INI
> >    *** end copy ***
> >
> >    As you can see, i tried variations to no avail.
> >    So...what the heck do i do?
> >
>
> Any path with at least a space in it MUST be enclosed on quotes.
> Otherwise, the spaces are treated as separators.
>
> Library_Path=G:\PGLTECH\Lifter Docs\ and
> Library_Path=G:\Program Files\POV-Ray for Windows v3.5\INCLUDE
>
>      must be changed to:
> Library_Path="G:\PGLTECH\Lifter Docs\" and
> Library_Path="G:\Program Files\POV-Ray for Windows v3.5\INCLUDE"
>
> You don't need the commented out paths.
>
>
> Alain

Post a reply to this message

Nope!
  Still get run parse error cannot find file <path>\.POV so somewhere it would
seem that one needs to eXplicitly give POV filename.
  Sorry for the hassle.


Alain <aze### [at] qwertyorg> wrote:

> >    I am getting nowhere.
> >    *** copy of the last section of my POVRAY.INI ***
> > ; Specify path to search for any files not found in current
> > ; directory.  Up to 10 such paths may be specified.
> > ; These were added by the install process with your installation
> > ; drive and directory already patched in.
> > ;
> >
> > Library_Path=G:\PGLTECH\Lifter Docs\
> > Library_Path=G:\WINNT\Fonts
> > Library_Path=G:\Program Files\POV-Ray for Windows v3.5\INCLUDE
> > ;SourceFile=G:\PGLTECH\Lifter Docs\build.pov ;; Unknown option, tries to open
> > THIS file
> > ;Input_File_Name=G:\PGLTECH\Lifter Docs\build.pov ;; makes zero difference
> > ;Input_File_Name=build.pov ;; makes zero difference
> > ; ** This file is G:\Program Files\POV-Ray for Windows v3.5\renderer\POVRAY.INI
> >    *** end copy ***
> >
> >    As you can see, i tried variations to no avail.
> >    So...what the heck do i do?
> >
>
> Any path with at least a space in it MUST be enclosed on quotes.
> Otherwise, the spaces are treated as separators.
>
> Library_Path=G:\PGLTECH\Lifter Docs\ and
> Library_Path=G:\Program Files\POV-Ray for Windows v3.5\INCLUDE
>
>      must be changed to:
> Library_Path="G:\PGLTECH\Lifter Docs\" and
> Library_Path="G:\Program Files\POV-Ray for Windows v3.5\INCLUDE"
>
> You don't need the commented out paths.
>
>
> Alain

Post a reply to this message

Robert Baer wrote:
>   Nope!
>   Still get run parse error cannot find file <path>\.POV so somewhere it would
> seem that one needs to eXplicitly give POV filename.
>   Sorry for the hassle.
> 

Hi Robert, It is not a hassle.
I suggest that you uninstall Pov 3.5 and Moray completely, saving any 
files you want then reinstall them. I had problems installing Pov 3.5 on 
Win 7 so I right clicked povwin35.exe and went to properties. In the 


I did the same for Moray and allowed Moray to configure PovRay. When 
Moray starts allow it to set the default settings for PovRay. (You 
should have an entry in PVENGINE.INI like this:)
[GUIExtensions]
UseExtensions=1
ExtDLL15=C:\Graphics\Moray For Windows\MorayCtrl.dll
ExtDLL16=C:\Graphics\Moray For Windows\Plugins\AnimGuiExt.dll



[Hint] In Moray configuration Alt + 0.
Compatibility Tab, select always render to backdrop
Interface Tab, select Raytrace to OpenGL backdrop

This will show you the PovRay output file in the camera viewport when it 
is being rendered.

In the Moray folder there should be a folder called POVScn. Here you 
will find the files that Moray exports to PovRay. Look for 

you will see that near the bottom of the list is the line 
Input_File_Name = YourScene.pov. This is the command to PovRay to render 
the scene.
While you have YourScene.ini open in PovRay you should be able to render 
your scene by clicking RUN

I hope this helps.



-- 

Best Regards,
	Stephen

Post a reply to this message

Alain wrote:


>> So that's how it works, Thanks Alain
>>
> 
> That's the way it works for any ini files,not just POV-Ray's ones.
> It's also the rule for shortcuts and registry entries to files and 
> applications.
> 
> It goes back to the good old days of DOS and the 8.3 naming convention 
> when spaces where not allowed at all in any file name.
> 
> 


in paths. There is something lurking in the back of my mind for when you 
use concat.

-- 

Best Regards,
	Stephen

Post a reply to this message

> Alain wrote:

>
>>> So that's how it works, Thanks Alain
>>>
>>
>> That's the way it works for any ini files,not just POV-Ray's ones.
>> It's also the rule for shortcuts and registry entries to files and
>> applications.
>>
>> It goes back to the good old days of DOS and the 8.3 naming convention
>> when spaces where not allowed at all in any file name.
>>
>>
>

> in paths. There is something lurking in the back of my mind for when you
> use concat.
>

Simple, a single "\" is used as an escape character. This allow you to 
use "\n" to isue a line feed for example. Thus, any single \ not 
followed by a valid operator will be ignored. Worst, it can cause some 
unforseen behaviour or make some characters disapears.

There is a problem with some applications. Some applications 
automaticaly change any "\" to "\\", and when they found a "\\", dumbly 
change it to "\\\\", then to "\\\\\\\\" if you edit the same entry a 
second time...


Alain

Post a reply to this message

I will try fiddling around as you suggest.
  Thanks.


Stephen <mca### [at] aolDOTcom> wrote:
> Robert Baer wrote:
> >   I am getting nowhere.
> >   *** copy of the last section of my POVRAY.INI ***
> > ; Specify path to search for any files not found in current
> > ; directory.  Up to 10 such paths may be specified.
> > ; These were added by the install process with your installation
> > ; drive and directory already patched in.
> > ;
> >
> > Library_Path=G:\PGLTECH\Lifter Docs\
> > Library_Path=G:\WINNT\Fonts
> > Library_Path=G:\Program Files\POV-Ray for Windows v3.5\INCLUDE
> > ;SourceFile=G:\PGLTECH\Lifter Docs\build.pov ;; Unknown option, tries to open
> > THIS file
> > ;Input_File_Name=G:\PGLTECH\Lifter Docs\build.pov ;; makes zero difference
> > ;Input_File_Name=build.pov ;; makes zero difference
> > ; ** This file is G:\Program Files\POV-Ray for Windows v3.5\renderer\POVRAY.INI
> >   *** end copy ***
> >
> >   As you can see, i tried variations to no avail.
> >   So...what the heck do i do?
> >
> >
>
> Hi Robert,


> library paths have quotes around the path.
> E.g. Library_Path="E:\Graphics\B3D Data\Scenes\Tena Chep\Dream". And
> these only refer to the folder not a file.
>

> PovRay along with the scene.pov file. So there is no need to put them in

>
> What happens if you try to render a simple scene with say just a box,
> camera and a light source? Because this would not need other files, it
> should render OK.
>
> Moray will export two files in the directory (folder) the Moray scene is
> saved in. If this scene is not rendered then open both the

> the active tab press RUN. PovRay should render this without any extra

> If not look in the PovRay messages window/tab and look for error messages.
>
> Before you do, in PovRay, Options > Script I/O Restrictions > Allow
> Read, Restricted Write
> And
> Options > Editor Window, select Auto-Reload Error file
> This will jump the focus to any like in the Pov file that causes an error.
>
> BTW there is a separate group for Moray on these newsgroups called moray.win
>
>
> --
>
> Best Regards,
>  Stephen

Post a reply to this message

No go; there is no file named "scene.ini" anywhere on my HD, nor a file called
"scene.pov".
  However there is a file called "PreviewScene.pov" and modifying that does
nothing.
  As an aside, i see no instructions as to how to register Moray so i will
noodle around to find the moray.win NG.

Stephen <mca### [at] aolDOTcom> wrote:
> Robert Baer wrote:
> >   I am getting nowhere.
> >   *** copy of the last section of my POVRAY.INI ***
> > ; Specify path to search for any files not found in current
> > ; directory.  Up to 10 such paths may be specified.
> > ; These were added by the install process with your installation
> > ; drive and directory already patched in.
> > ;
> >
> > Library_Path=G:\PGLTECH\Lifter Docs\
> > Library_Path=G:\WINNT\Fonts
> > Library_Path=G:\Program Files\POV-Ray for Windows v3.5\INCLUDE
> > ;SourceFile=G:\PGLTECH\Lifter Docs\build.pov ;; Unknown option, tries to open
> > THIS file
> > ;Input_File_Name=G:\PGLTECH\Lifter Docs\build.pov ;; makes zero difference
> > ;Input_File_Name=build.pov ;; makes zero difference
> > ; ** This file is G:\Program Files\POV-Ray for Windows v3.5\renderer\POVRAY.INI
> >   *** end copy ***
> >
> >   As you can see, i tried variations to no avail.
> >   So...what the heck do i do?
> >
> >
>
> Hi Robert,


> library paths have quotes around the path.
> E.g. Library_Path="E:\Graphics\B3D Data\Scenes\Tena Chep\Dream". And
> these only refer to the folder not a file.
>

> PovRay along with the scene.pov file. So there is no need to put them in

>
> What happens if you try to render a simple scene with say just a box,
> camera and a light source? Because this would not need other files, it
> should render OK.
>
> Moray will export two files in the directory (folder) the Moray scene is
> saved in. If this scene is not rendered then open both the

> the active tab press RUN. PovRay should render this without any extra

> If not look in the PovRay messages window/tab and look for error messages.
>
> Before you do, in PovRay, Options > Script I/O Restrictions > Allow
> Read, Restricted Write
> And
> Options > Editor Window, select Auto-Reload Error file
> This will jump the focus to any like in the Pov file that causes an error.
>
> BTW there is a separate group for Moray on these newsgroups called moray.win
>
>
> --
>
> Best Regards,
>  Stephen

Post a reply to this message

Robert Baer wrote:
>   No go; there is no file named "scene.ini" anywhere on my HD, nor a file called
> "scene.pov".
>   However there is a file called "PreviewScene.pov" and modifying that does
> nothing.
>   As an aside, i see no instructions as to how to register Moray so i will
> noodle around to find the moray.win NG.
> 


know what you have saved the scene as.
If you have not saved the Moray scene then the files will be exported as 
Untitled.pov and Untitled.ini.

One other thing to check. Make sure that Moray is pointing to the 
correct version of PovRay. From the menu: Render > Render Options. Check 

C:\Graphics\POV-Ray for Windows v3.5\bin\pvengine.exe


-- 

Best Regards,
	Stephen

Post a reply to this message