POV-Ray for Windows v3.7 beta 37a (64-bit)

ini file requires extension, whereas 3.6 did not.

i.e., Input_File_Name=scene worked under 3.6, but the beta requires
Input_File_Name=scene.pov

Post a reply to this message

On 22.06.10 01:57, jberry02 wrote:
> POV-Ray for Windows v3.7 beta 37a (64-bit)
>
> ini file requires extension, whereas 3.6 did not.
>
> i.e., Input_File_Name=scene worked under 3.6, but the beta requires
> Input_File_Name=scene.pov

Hmm, you say ini file and show and example scene file. Please provide a 
clear report saying what you expect and what happens instead.

	Thorsten

Post a reply to this message

On 6/22/2010 11:32 AM, Thorsten Froehlich wrote:
> On 22.06.10 01:57, jberry02 wrote:
>> POV-Ray for Windows v3.7 beta 37a (64-bit)
>>
>> ini file requires extension, whereas 3.6 did not.
>>
>> i.e., Input_File_Name=scene worked under 3.6, but the beta requires
>> Input_File_Name=scene.pov
>
> Hmm, you say ini file and show and example scene file. Please provide a
> clear report saying what you expect and what happens instead.
>
> Thorsten

No, he showed the example syntax he provided is used for INI files. See 
"3.1.2.5.2  Input File Name".

Also, the docs say "If you do not have an extension then .pov is 
assumed", which I assume is the problem he's reporting.

-- 
http://isometricland.com

Post a reply to this message

On 06/21/2010 08:57 PM, jberry02 wrote:
> POV-Ray for Windows v3.7 beta 37a (64-bit)
> 
> ini file requires extension, whereas 3.6 did not.
> 
> i.e., Input_File_Name=scene worked under 3.6, but the beta requires
> Input_File_Name=scene.pov
> 
> 
> 
works fine for me linux-beta37c ... I have Work.ini that contains my
basic setup:

---
Display_Gamma=2.2
Input_File_Name=Work
Output_File_Name=/povfiles/
+fn
+wt4

Library_Path="/users/ash/POV-Ray/Source/"
Library_Path="/users/ash/POV-Ray/Source/Contributed/DF3Files"
Library_Path="/users/ash/POV-Ray/Source/Contributed/Proceduralize"
Library_Path="/users/ash/POV-Ray/Source/Contributed/Lattice/"
Library_Path="/users/ash/POV-Ray/Images"
Library_Path="/users/ash/POV-Ray/Includes"
---

then bash script that I run from command line:
povray Work Options[SomeAA] Options[RadiosityLoad] Options[Pause] +w800
+h600

note: from the command-line if no extension is given 'INI' is assumed

Jim

Post a reply to this message

On 24.06.10 04:48, SharkD wrote:
> On 6/22/2010 11:32 AM, Thorsten Froehlich wrote:
>> On 22.06.10 01:57, jberry02 wrote:
>>> POV-Ray for Windows v3.7 beta 37a (64-bit)
>>>
>>> ini file requires extension, whereas 3.6 did not.
>>>
>>> i.e., Input_File_Name=scene worked under 3.6, but the beta requires
>>> Input_File_Name=scene.pov
>>
>> Hmm, you say ini file and show and example scene file. Please provide a
>> clear report saying what you expect and what happens instead.
>>
>> Thorsten
>
> No, he showed the example syntax he provided is used for INI files. See
> "3.1.2.5.2 Input File Name".
>
> Also, the docs say "If you do not have an extension then .pov is
> assumed", which I assume is the problem he's reporting.

He says the INI file requires an extension. The syntax he showed should 
work, and he did not say it doesn't. Hence he needs to clarify what the 
problem is.

	Thorsten

Post a reply to this message

On 06/24/2010 12:28 PM, Thorsten Froehlich wrote:
> He says the INI file requires an extension. The syntax he showed should
> work, and he did not say it doesn't. Hence he needs to clarify what the
> problem is.

... and my example shows that it does indeed work ... least ways for me ;-)

Post a reply to this message

"jberry02" <nomail@nomail> schreef in bericht 
news:web.4c1ffc789becd6c8bba8fbcd0@news.povray.org...
> POV-Ray for Windows v3.7 beta 37a (64-bit)
>
> ini file requires extension, whereas 3.6 did not.
>
> i.e., Input_File_Name=scene worked under 3.6, but the beta requires
> Input_File_Name=scene.pov
>

the line:
Input_File_Name=scene

works well in version 3.7 for me. No need to add .pov

Thomas

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> He says the INI file requires an extension. The syntax he showed should
> work, and he did not say it doesn't. Hence he needs to clarify what the
> problem is.

OK - let me try to be more specific.

The syntax I showed used to work under prior versions of POV-Ray, and I was
expecting it to work under the 3.7 beta, but it fails.

First, note that this is the Windows version.
Second the issue is not with opening the ini file, but with opening the scene
file from within the ini file.

I have a scene.ini file, that has a line:

Input_File_Name=scene

under POV-Ray 3.5 *and* POV-Ray 3.6, the scene defined in the file scene.pov is
rendered properly using the parameters specified in the scene.ini file.  The ini
file is opened from the POV-Ray GUI, and run using the "Run" button.

under POV-Ray 3.7, I get an error - I originally thought that it was simply not
looking for scene.pov (i.e., it wasn't adding the .pov extension when trying to
open the scene file), but looking closer the error is *actually*:

Input file 'C:\[...]\scene' not found; cannot determine I/O permission for
write.
Failed to start render: Cannot open file.

In other words, it appears that the problem is that it isn't adding the default
..pov extension when it is trying to do the I/O permission check.  I do not have
any special I/O permisssions configured for any version of POV-Ray (I get the
pop-up dialogs), and this is a change in behavior from 3.6 to the current beta
of 3.7.  The scene.pov file is not in any of the POV-Ray directories - it is in
a separate tree where I keep my scene files.

I hope this is clearer.

Post a reply to this message

"jberry02" <nomail@nomail> schreef in bericht 
news:web.4c295a08949a9ca3bba8fbcd0@news.povray.org...
> Input_File_Name=scene
>
> under POV-Ray 3.5 *and* POV-Ray 3.6, the scene defined in the file 
> scene.pov is
> rendered properly using the parameters specified in the scene.ini file. 
> The ini
> file is opened from the POV-Ray GUI, and run using the "Run" button.
>
> under POV-Ray 3.7, I get an error - I originally thought that it was 
> simply not
> looking for scene.pov (i.e., it wasn't adding the .pov extension when 
> trying to
> open the scene file), but looking closer the error is *actually*:
>
> Input file 'C:\[...]\scene' not found; cannot determine I/O permission for
> write.
> Failed to start render: Cannot open file.
>

My guess: you may have to add the path to the scene.pov file. Obviously, the 
ini and the pov files are not in the same directory, and the path is not in 
your povray.ini

Thomas

Post a reply to this message

Am 29.06.2010 04:27, schrieb jberry02:

> under POV-Ray 3.7, I get an error - I originally thought that it was simply not
> looking for scene.pov (i.e., it wasn't adding the .pov extension when trying to
> open the scene file), but looking closer the error is *actually*:
>
> Input file 'C:\[...]\scene' not found; cannot determine I/O permission for
> write.
> Failed to start render: Cannot open file.
>
> In other words, it appears that the problem is that it isn't adding the default
> ..pov extension when it is trying to do the I/O permission check.  I do not have
> any special I/O permisssions configured for any version of POV-Ray (I get the
> pop-up dialogs), and this is a change in behavior from 3.6 to the current beta
> of 3.7.  The scene.pov file is not in any of the POV-Ray directories - it is in
> a separate tree where I keep my scene files.

Having looked at it in a debugger, I can confirm that there is a 
problem, and that you don't seem to be far off the mark:

The error occurs when POV-Ray tries to determine the I/O permissions for 
the /output/ file. If that isn't explicitly specified with a path, 
POV-Ray will try to get the path from the input file; however, it will 
take the unprocessed parameter (in the sample case "scene") rather than 
the file name POV-Ray makes of it ("scene.pov"), and then attempts to 
get the full /long/ path name of the file (remember the good old 8.3 
filenames for compatibility with 16-bit programs?), which only works 
when the file exists.

Would you mind submitting a bug report to <http://bugs.povray.org>?

Post a reply to this message