|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Unlike the BMP output, PNG output (+FN) doesn't cause POV-Ray to crash but
the resulting file is corrupt according to several viewing or image apps
(Windows XP viewer, Gimp, Picture Publisher). They either refuse to open the
file or show a damaged picture (artefacts).
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
42618654@news.povray.org...
> Unlike the BMP output, PNG output (+FN) doesn't cause POV-Ray to crash but
> the resulting file is corrupt according to several viewing or image apps
> (Windows XP viewer, Gimp, Picture Publisher). They either refuse to open
> the file or show a damaged picture (artefacts).
What happens is that the file is kept open until POV-Ray is closed (it
cannot be deleted for instances). Closing POV-Ray seems to add a couple of
bytes to the file and then it becomes "finished" (and can be opened
normally).
G.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
42618810@news.povray.org...
> 42618654@news.povray.org...
>> Unlike the BMP output, PNG output (+FN) doesn't cause POV-Ray to crash
>> but the resulting file is corrupt according to several viewing or image
>> apps (Windows XP viewer, Gimp, Picture Publisher). They either refuse to
>> open the file or show a damaged picture (artefacts).
>
> What happens is that the file is kept open until POV-Ray is closed (it
> cannot be deleted for instances). Closing POV-Ray seems to add a couple of
> bytes to the file and then it becomes "finished" (and can be opened
> normally).
>
Well, Windows and Picture Publisher find the PNG files to be OK but the GIMP
still complains about the files being corrupted (but displays them OK after
that)...
G.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gilles Tran wrote:
> What happens is that the file is kept open until POV-Ray is closed (it
> cannot be deleted for instances). Closing POV-Ray seems to add a couple of
> bytes to the file and then it becomes "finished" (and can be opened
> normally).
Thanks for pointing this out. This actually applies to all image files.
This problem will be fixed in the next beta.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |