![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
MegaPov 0.4 crashes when a pigment pattern is used without colour map. Like:
material {
texture {
pigment {rgb x}
}
interior_texture {
pigment {radial}
}
}
sig.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <38F636AB.3793A386@stud.ntnu.no>, Sigmund Kyrre Aas
<as### [at] stud ntnu no> wrote:
> MegaPov 0.4 crashes when a pigment pattern is used without colour map.
> Like:
>
> material {
> texture {
> pigment {rgb x}
> }
> interior_texture {
> pigment {radial}
> }
> }
>
> sig.
Hmm. I really don't know what could cause this...I don't think I messed
with much of the texture code, just added another texture and a check
for which one to use. Maybe a bug lurking somewhere in the texture code
which only appears in interior_texture...or maybe I forgot to copy the
pointer somewhere...
When does it crash? Parse-time, after parsing but before rendering
starts, as soon as rendering starts, when rendering reaches an object
with that material...?
Well, at least there is a workaround, you don't have to stop until it is
tracked down. You really should supply a color_map anyway... :-)
--
Christopher James Huff - Personal e-mail: chr### [at] yahoo com
TAG(Technical Assistance Group) e-mail: chr### [at] tag povray org
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Chris Huff wrote:
...
> When does it crash? Parse-time, after parsing but before rendering
> starts, as soon as rendering starts, when rendering reaches an object
> with that material...?
The latter. And yes, the bug is mostly harmless..
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <38F6F328.13359AF3@stud.ntnu.no>, as <@stud.ntnu.no> wrote:
> > When does it crash? Parse-time, after parsing but before rendering
> > starts, as soon as rendering starts, when rendering reaches an object
> > with that material...?
>
> The latter.
Uh, which one would that be?
And could you give a short scene file which produces this problem, to
help track it down?
--
Christopher James Huff - Personal e-mail: chr### [at] yahoo com
TAG(Technical Assistance Group) e-mail: chr### [at] tag povray org
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Chris Huff <chr### [at] yahoo com> writes:
> Uh, which one would that be?
It crashes when trying to trace the texture, that is reaching the object. I
don't have the scene at hand (vacation). It was something like this:
camera { location <5,5,-30> look_at 2*y } // (just guessing)
light_source {
0, 1
looks_like {
sphere {0,2 pigment{rgb 1} finish{ambient 1} }
}
translate 20*<1,2,-3>
}
sphere {0,4
texture{
pigment {rgb x}
}
interior_texture{
pigment {radial} // chrashed with other patterns too
}
cliped_by { plane{-z,0} }
}
--
Sigmund
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |