|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
when I try to render a scene I get an error message and the message pane
contains this message:
Messages cleared.
Preset INI file is 'C:\PROGRAM FILES\POV-RAY FOR WINDOWS
V3.6\RENDERER\QUICKRES.INI', section is '[160x120, No AA]'.
Preset source file is 'C:\Program Files\POV-Ray for Windows
v3.6\scenes\main.pov'.
-
Cannot open INI file 'C:\Documents and Settings\u ivatel\Data aplikac
\POV-Ray\v3.7\ini\povray.ini'.
Failed to start render: Failed to parse INI file
known for this).
Megapov 1.2.1 and PovRay 3.6 works fine.
Thanks in advance for pointing me to a potential solution. If there's
none I'm looking forward for a new beta (or a MegaPov with SMP).
John Dvorak
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
jan dvorak wrote:
> when I try to render a scene I get an error message and the message pane
> contains this message:
> Messages cleared.
> Preset INI file is 'C:\PROGRAM FILES\POV-RAY FOR WINDOWS
> V3.6\RENDERER\QUICKRES.INI', section is '[160x120, No AA]'.
> Preset source file is 'C:\Program Files\POV-Ray for Windows
> v3.6\scenes\main.pov'.
> -
> Cannot open INI file 'C:\Documents and Settings\u ivatel\Data aplikac
> \POV-Ray\v3.7\ini\povray.ini'.
> Failed to start render: Failed to parse INI file
>
> known for this).
>
> Megapov 1.2.1 and PovRay 3.6 works fine.
>
> Thanks in advance for pointing me to a potential solution. If there's
> none I'm looking forward for a new beta (or a MegaPov with SMP).
Thanks for this, I"ll look into it this weekend (I hope to do a new
beta then, time permitting). At the moment I don't think there is a
workaround.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This should work in the next beta, please let me know if you still see issues.
regards,
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
> This should work in the next beta, please let me know if you still see
> issues.
This fixed more than you think, asc("á") now gives the correct answer :)
Even when using >0xFF Unicode characters!
(compared to 3.6... maybe this is a different problem that was fixed in an
earlier beta)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |