 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello,
In the folder scenes/objects are three pov files named:
crat_dat.pov
crater_dat.pov
crater.pov
In "crater.pov" there are instructions to render the "crat_dat.pov" file
with png-output, yet further down, the heightfield expects a file named
"crater_dat".
However, the "crat_dat.pov" says that it should be rendered with
tga-output, while "crater_dat.pov" has no instructions at all regarding
the output format.
Anyway, I rendered the "crater_dat.pov" as a png-file and then I tried to
render the "crater.pov" and my Mac crashed.
Looking closer at "crater.pov" I noticed that there wasn't any
HF_TYPE/bitmap identifier in the heightfield object, which looked very
strange.
It seemed like an odd thing to forget, so I checked the docs and found out
that it is allowed to skip the HF_TYPE if the output fileformat is set to
the same fileformat as the scenefile expects. Which seems very backwards
to me.
Anyway, by adding the HF_TYPE "png" before "crater_dat" in the heightfield
in "crater.pov", I could render the file without any crash. I guess that
the other option was to change the output to png instead (which I didn't
try since I seldom have any use for png-files outside POV-ray).
So, in short, this is my report:
- Pov-ray crashes when a heightfield without HF_TYPE expects another
fileformat than what the output is set to.
- The file "crater.pov" should either have a HF_TYPE in its heightfield,
or a notice in the comments that the output format should be set to png.
- There's only need for one "..._dat.pov" file, so one should be deleted,
and only the remaining one should be refered to in the "crater.pov" file.
Povray Beta 7
PowerMacintosh G3
System 9.0.4 (swedish)
--
Tom Stone
Domarebacken 42, 14557 Norsborg, Sweden
Phone: Int+46 8 5318 4318, Tel: 08-5318 4318
http://home5.swipnet.se/~w-52256/index.htm
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tom Stone" wrote:
> In the folder scenes/objects are three pov files named:
> crat_dat.pov
> crater_dat.pov
> crater.pov
That's a mistake then. I specifically gave instructions to delete
crat_dat.pov, and it has been correctly removed in the windows version.
You're sure you didn't just install the latest beta over the previous one,
in which case you'd still have crat_dat.pov?
> In "crater.pov" there are instructions to render the
> "crat_dat.pov" file with png-output, yet further down,
> the heightfield expects a file named "crater_dat".
That's my fault. I'll update the comments at the top of crater.pov.
> However, the "crat_dat.pov" says that it should be
> rendered with tga-output
Ignore crat_dat.pov; it should have been deleted.
> while "crater_dat.pov" has no instructions at all
> regarding the output format.
Because it doesn't require a specific output format.
> Anyway, I rendered the "crater_dat.pov" as a png-file
> and then I tried to render the "crater.pov" and my Mac
> crashed.
That's one for the POV-Team. But you should first provide a minimum scene
where the crash occurs.
> Looking closer at "crater.pov" I noticed that there
> wasn't any HF_TYPE/bitmap identifier in the heightfield
> object, which looked very strange.
That's a new feature.
> Which seems very backwards to me.
Me too, but the others disagreed with me.
> So, in short, this is my report:
> - Pov-ray crashes when a heightfield without HF_TYPE expects
> another fileformat than what the output is set to.
Please provide a minimum scene where this occurs.
> - The file "crater.pov" should either have a HF_TYPE in
> its heightfield, or a notice in the comments that the
> output format should be set to png.
That's wrong. The output type should be set to the same format that was used
when crater_dat.pov was rendered. I don't like that, but as I said the
others wanted me to make it that way.
> - There's only need for one "..._dat.pov" file, so one
> should be deleted, and only the remaining one should be
> refered to in the "crater.pov" file.
Correct.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3be33c3a@news.povray.org>, "Rune"
<run### [at] mobilixnet dk> wrote:
>I specifically gave instructions to delete
>crat_dat.pov, and it has been correctly removed in the windows version.
>You're sure you didn't just install the latest beta over the previous one,
>in which case you'd still have crat_dat.pov?
Nope. Deleted the whole Beta 6 folder before installing Beta 7.
>> while "crater_dat.pov" has no instructions at all
>> regarding the output format.
>
>Because it doesn't require a specific output format.
Aha, all formats (including Pict, the default format on Mac) can handle
16-bit gray output now? Sorry, I've missed that.
Doesn't help though - I just tried to render the two files with Picts
instead, and it still crashes, both with and without the HF_TYPE "sys".
So, so far I better stick with png or tga for 16-bit gray images, as they
work nicely.
>> Looking closer at "crater.pov" I noticed that there
>> wasn't any HF_TYPE/bitmap identifier in the heightfield
>> object, which looked very strange.
>
>That's a new feature.
I noticed that when I compared the docs with the 3.1 docs. Couldn't find
it in the segment about new features - but I might have missed it.
>> - Pov-ray crashes when a heightfield without HF_TYPE expects
>> another fileformat than what the output is set to.
>
>Please provide a minimum scene where this occurs.
"crater.pov" is rather small as it is, but sure; I'll put together a
minimum file.
>> - The file "crater.pov" should either have a HF_TYPE in
>> its heightfield, or a notice in the comments that the
>> output format should be set to png.
>
>That's wrong. The output type should be set to the same format that was used
>when crater_dat.pov was rendered. I don't like that, but as I said the
>others wanted me to make it that way.
Ah, but if the instructions at the top of the "crater.pov" is correct,
that the "..._dat.pov" should be rendered as a png-file, then I'm forced
to use png. (Or edit the scene file).
Anyway, on Mac it is best to use png or tga for heightfields, but neither
format is very useful outside Povray. And the eventual time that can be
saved on this shortcut will soon be used up when the output file has to be
converted into a more useful format.
This still seems strange, and I can't think of any situation where this
feature would be useful - is there any advantages at all for this
shortcut?
--
Tom Stone
Domarebacken 42, 14557 Norsborg, Sweden
Phone: Int+46 8 5318 4318, Tel: 08-5318 4318
http://home5.swipnet.se/~w-52256/index.htm
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3be33c3a@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:
> That's a mistake then. I specifically gave instructions to delete
> crat_dat.pov, and it has been correctly removed in the windows version.
> You're sure you didn't just install the latest beta over the previous one,
> in which case you'd still have crat_dat.pov?
There is no "installer" for the Mac version (no need for one). It may well
be that I overlooked that file when I updated the scene files...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tom Stone" wrote:
> Aha, all formats (including Pict, the default format on Mac)
> can handle 16-bit gray output now?
I didn't say that.
> Doesn't help though - I just tried to render the two
> files with Picts instead, and it still crashes, both
> with and without the HF_TYPE "sys". So, so far I
> better stick with png or tga for 16-bit gray images,
> as they work nicely.
You do that.
> Ah, but if the instructions at the top of the
> "crater.pov" is correct, that the "..._dat.pov"
> should be rendered as a png-file, then I'm forced
> to use png.
Those comments are not correct. I did say that I would fix them.
> This still seems strange, and I can't think of any
> situation where this feature would be useful - is
> there any advantages at all for this shortcut?
According to the others the advantage is that new users can simply render
crater_dat.pov and then crater.pov and then it'll work (looking apart from
the crashes, which are of course not supposed to happen), and the user don't
need to know how to change the output format to a specific format. But
personally I agree that that advantage is not as big as the disadvantages
(that 16-bit is not always supported, that it doesn't work if the user wants
to render crater.pov in a different format).
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3be3e7c7@news.povray.org>, "Rune"
<run### [at] mobilixnetdk> wrote:
>if the instructions at the top of the
>> "crater.pov" is correct, that the "..._dat.pov"
>> should be rendered as a png-file, then I'm forced
>> to use png.
>
>Those comments are not correct. I did say that I would fix them.
Sorry, I thought that you only meant that the reference to the wrong
"crater_dat" file would be corrected.
>According to the others the advantage is that new users can simply render
>crater_dat.pov and then crater.pov and then it'll work (looking apart from
>the crashes, which are of course not supposed to happen), and the user don't
>need to know how to change the output format to a specific format.
If the user doesn't change the output format, the output will always be a
Pict file, since that is the default format on Mac. A new user will have a
tough time finding this problem.
>But
>personally I agree that that advantage is not as big as the disadvantages
Yes. If I have the files "Hill.tga", "Hill.png" and "Hill.pict" in an
folder, then I know it probably is for an imagemapped heightfield, since
all tga are imagemaps, all png are for heightfields, and all picts are the
resulting output. (I choose those names and formats for heightfields and
imagemaps since I don't have any use for tga and png outside Povray)
But should I now forget to use bitmap identifier in the scenefile, then
Povray will not give a syntax error, but will try to use "Hill.pict" as
both heightfield and imagemap, at the same time as it tries to overwrite
it with a new "Hill.pict" (as the output is set to pict). I imagine that
this can cause weird things.
It might be possible that this is a practical shortcut for one's own
scenes, but I can only see problems in having it in scenes that will be
used by others.
--
Tom Stone
Domarebacken 42, 14557 Norsborg, Sweden
Phone: Int+46 8 5318 4318, Tel: 08-5318 4318
http://home5.swipnet.se/~w-52256/index.htm
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
