 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Someone recently posted on here that a crash is always an error; that
the appropriate action for the program to take if there's something
wrong is to give an error message, not to crash. So I'm posting this
code, which makes POV do just that.
I am using POV-Ray, version 3.1g for Macintosh, on a G3/300 running OS
9.0.4, with 160mb RAM. I know code shouldn't normally be posted in this
group, but this is /really/ short, as I was looking at how height fields
work. I suspect my slopes are too abrupt or too confused, but here it
is. You can find the image I was using to create the height field at
<http://www.coyotesdaughter.com/dawn/newworld.gif>.
#include "colors.inc"
light_source { <0, 10, 0> White }
camera {
location <0, 3, 0>
look_at 0
} // close camera
height_field {
gif
"newworld.gif"
//smooth
pigment { Red }
}
--
Dawn McKnight | "Who cares what the hipbone's connected to? I'm in Neurology!"
McK### [at] mac com | -- Justine Devlin, M.D.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3A2### [at] maccom> , Dawn McKnight <mck### [at] maccom>
wrote:
> Someone recently posted on here that a crash is always an error; that
> the appropriate action for the program to take if there's something
> wrong is to give an error message, not to crash. So I'm posting this
> code, which makes POV do just that.
>
> I am using POV-Ray, version 3.1g for Macintosh, on a G3/300 running OS
> 9.0.4, with 160mb RAM. I know code shouldn't normally be posted in this
> group, but this is /really/ short, as I was looking at how height fields
> work. I suspect my slopes are too abrupt or too confused, but here it
> is. You can find the image I was using to create the height field at
> <http://www.coyotesdaughter.com/dawn/newworld.gif>.
Please check the POV-Ray documentation folder and fill out the bug report
form. then send this form to mac### [at] povrayorg
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> Please check the POV-Ray documentation folder and fill out the bug report
> form. then send this form to mac### [at] povrayorg
This is one of the oldest bugs that I know of. It has something
to do with the camera being at x+z = 0 while using look_at = 0.
i.e. -
camera {
location <0, 3, 0>
look_at 0
}
If you change it to something like -
camera {
location <0, 3, 0>
look_at <0,0, -0.01>
}
the crash will not happen. A divide by zero bug maybe ?
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken <tyl### [at] pacbellnet> wrote:
> This is one of the oldest bugs that I know of. It has something
> to do with the camera being at x+z = 0 while using look_at = 0.
More specifically, the problem is caused by the camera's view direction
being parallel to the sky direction (e.g. location <3, -5, 1> look_at <3,
15, 1> should also cause the problem). When this occurs, POV-Ray is unable
to determine the up vector of the camera matrix, and the result is often a
program crash.
As Ken detailed, a work-around to avoid this is simply to shift the location
or look at so the view direction is not parallel to the sky direction, which
can also be done by specifying the sky or up vector of the camera directly.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken wrote in message <3A232B64.7E9DE15F@pacbell.net>...
>
>This is one of the oldest bugs that I know of. It has something
>to do with the camera being at x+z = 0 while using look_at = 0.
>
>i.e. -
>
>camera {
> location <0, 3, 0>
> look_at 0
> }
I've never had a problem with doing this. Is it something specific to a
particular version? I'm using POV-Ray for Windows 3.1e, all versions of
MegaPOV, many versions of the SuperPatch, all versions of UVPov since 4.0a,
and all versions of SkyPOV.
--
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mark Wagner wrote:
> I've never had a problem with doing this. Is it something specific to a
> particular version? I'm using POV-Ray for Windows 3.1e, all versions of
> MegaPOV, many versions of the SuperPatch, all versions of UVPov since 4.0a,
> and all versions of SkyPOV.
It used to be a problem in v2.2 and it happened in v3.0 for Windows.
It guess I have been so strongly influenced by this I doubt I ever
checked it out in v3.1.
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Dawn McKnight" <mck### [at] maccom> wrote in message
news:3A2### [at] maccom...
Well, there have been other suggestions, but, IIRC, hf's do sometimes crash
pov - the general solution is to move the camera slightly.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dawn McKnight <mck### [at] maccom> wrote:
: Someone recently posted on here that a crash is always an error; that
: the appropriate action for the program to take if there's something
: wrong is to give an error message, not to crash.
I think that was me. And you are right. Povray should never crash, specially
when we are dealing with the camera location. If the camera location is
illegal, an error should be issued instead of just starting the rendering
and crashing.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I've only had this problem with heightfields.
--
Peter
http://hertel.no/bigone
> Mark Wagner wrote:
>
> > I've never had a problem with doing this. Is it something specific to a
> > particular version? I'm using POV-Ray for Windows 3.1e, all versions of
> > MegaPOV, many versions of the SuperPatch, all versions of UVPov since
4.0a,
> > and all versions of SkyPOV.
>
> It used to be a problem in v2.2 and it happened in v3.0 for Windows.
> It guess I have been so strongly influenced by this I doubt I ever
> checked it out in v3.1.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Dawn McKnight" <mck### [at] maccom> wrote in message
news:3A2### [at] maccom...
Does the problem occur if you remove the hf? (put something else in scene to
avoid "no objects" warning).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
