Wasn't it Ken who wrote:
>
>
>Mike Williams wrote:
>
>> sin(X)^sin(X) -> crash! (job000179 and job000180)
>> http://news.povray.org/3baf7992@news.povray.org
>
>This does not crash in beta9. At least not with the MSVC compile.

It still crashes with "invalid page fault" on my machine.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

Wasn't it Josh English who wrote:
>I'm not sure if this is a bug or not but POV-Ray spits out a bunch of
>information in the message window on the Macintosh version. I have
>posted a screenshot of the warnings generated at the end of a trace. I
>think it is reporting on information for each object in the scene. 

I can't seem to find anything that can interpret that image.
 
Is it just the list of isosurface max_gradient suggestions?

Can you not save the text from the message window on a Mac, and post
that rather than a platform-specific screen grab.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

In article <3C2A7123.E923B0B4@spiritone.com> , Josh English 
<eng### [at] spiritonecom>  wrote:

> I'm not sure if this is a bug or not but POV-Ray spits out a bunch of
> information in the message window on the Macintosh version. I have
> posted a screenshot of the warnings generated at the end of a trace. I
> think it is reporting on information for each object in the scene.

Yes, these messages exist.  Just ignore them.

    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

On Thu, 27 Dec 2001 02:27:39 -0500, Slime wrote:
>> > (declare without the "#" can cause a much later line to fail to parse
>> > Parser will ignore the first token following old-style declares without
>> > a #.)
> 
> On a related note, it'd be helpful if words such as "declare" weren't
> syntax-highlighted when they didn't have the #.

That might look pretty, but it'll smack you in the face when you find out
that the parser still recognizes them without the # as well.

--
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}

Post a reply to this message

Thorsten Froehlich wrote:
> 
> In article <3C2A7123.E923B0B4@spiritone.com> , Josh English
> <eng### [at] spiritonecom>  wrote:
> 
> > I'm not sure if this is a bug or not but POV-Ray spits out a bunch of
> > information in the message window on the Macintosh version. I have
> > posted a screenshot of the warnings generated at the end of a trace. I
> > think it is reporting on information for each object in the scene.
> 
> Yes, these messages exist.  Just ignore them.
> 
>     Thorsten

I would love to, but a six second render has spent the last ten minutes
spitting out these messages and it has made beta 9 completely unusable.
I tossed the prefs but it hasn't helped.  I thought earlier versions had
a preference to stop output to some render streams but I can't find any
preference like that in the current version. 

Josh English
eng### [at] spiritonecom
http://www.spiritone.com/~english

Post a reply to this message

Mike Williams wrote:
> 
> I can't seem to find anything that can interpret that image.
It's a Macintosh PICT file
> 
> Is it just the list of isosurface max_gradient suggestions?
Nope. No isosurfaces in the scene.
> 
> Can you not save the text from the message window on a Mac, and post
> that rather than a platform-specific screen grab.
The message window prints things in chunks and you can only select one
chunk at a time. I would be here until Michelmas cutting and pasting
thousands of messages.
Here are a few:
 NULL, // UV_Trans
 0.000000, // Ph_Density
 0.000000, // Ph_Density
 0x92, // Flags
 { -1.000000, 0.000000, -2.000000 }, // apex
 { -2.000000, -0.000000, -0.000000 }, // base
  0.200000, // apex_radius
 
And the message window looks like it's scrolling every time you select
something new or bring the window to the front, so each copy and paste
takes about ten seconds to wait for the scroll.

Josh English
eng### [at] spiritonecom
http://www.spiritone.com/~english

Post a reply to this message

In article <3C2B6E24.C97D8BF3@spiritone.com> , Josh English 
<eng### [at] spiritonecom>  wrote:

> The message window prints things in chunks and you can only select one
> chunk at a time.

You can save the whole output window contents via the File menu.

The messages will only be there for spheres, cones and text objects.

The problem exists only in the Mac version and there is no way to turn them
off.  My time does not permit to upload a new beta 9 without these debug
messages.  Sorry!

    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

In article <3c2b8a2e@news.povray.org> , "Thorsten Froehlich" 
<tho### [at] trfde> wrote:

> The problem exists only in the Mac version and there is no way to turn them
> off.  My time does not permit to upload a new beta 9 without these debug
> messages.  Sorry!

However, you can terminate POV-Ray (it may take a few seconds) while output
of these messages is in progress.  Your image has already be written to disk
at the time these messages are generated, so no data will be lost.

    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

Some more notes and job numbers:

> Additional (?) blob bug
> (blob component disappears when radius is 317 or greater)
> http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
> (also reported as: Blob rendering error (job000136))
> http://news.povray.org/Xns91203DC7F3CCQ@204.213.191.226

> Bug with blobs and media
> (possibly related to  blob surface develops holes when "radius" is very
> small)
> http://news.povray.org/3be5f0b2@news.povray.org

> Blob component textures transformed twize
> http://news.povray.org/3bf70645@news.povray.org

All three logged as parts of job000189.
(also probably not the same problems)

> sin(X)^sin(X) -> crash! (job000179 and job000180)
> http://news.povray.org/3baf7992@news.povray.org

Fixed in next beta.

> [bug] orthographic camera bug?
> (objects sometimes disappear when the orthographic camera is used)
> http://news.povray.org/3bdca5eb@news.povray.org

An even simpler scene for this would really help.

> Jpeg and memory problem during animations (job000194)
> (It seems that some memory is not properly released between frames when
> a jpeg file is used)
> http://news.povray.org/3be2ef0d@news.povray.org

Fixed in next beta. (At least all known leaks there have now been fixed...)

> Black outline in smooth meshes
> (The outline of smooth meshes exhibit black dots or areas (which go away
> with double_illuminate))
> http://news.povray.org/3bf6794e$1@news.povray.org

Does this have something to do with surface normals?  The current behavior
might actually be correct...

> User_Abort_Command
> (User_Abort_Command does not seem to work at all)
> http://news.povray.org/Xns913D9F7268736seed7@povray.org

This might just be a user error.  Need details what users do and what they
expect.

> First report from bugreports
> http://news.povray.org/u12outsm2kso3k5ef4lp26ogm5cvsm46ge@4ax.com

Please change this to:

>>>
Error in VRand_Object
http://news.povray.org/3bc423e5[at]news.povray.org
<<<

> Re: trivial question on topic
> (Poly Object Bug: heart has a dark line of artifacts)
> http://news.povray.org/3BEBEB4C.CA854309@pacbell.net

Logged as job000038.

> Camera is off by half a pixel
> http://news.povray.org/3bccc696@news.povray.org

Will be changed in a future beta of 3.5 if #version 3.5 is used.

> Light_sources in light_groups don't cast shadows
> (rendering without light buffers (-UL) puts the shadows back)
> http://news.povray.org/3bfd4d63@news.povray.org

Logged as job000197.

> Save during render
> (is very slow)
> http://news.povray.org/jhaiduce@engin.umich.edu

I am not able to find this on the server.

> double_illuminate only works with direct lighting
> http://news.povray.org/3BF6F1FE.D21B0C6@oreka.com

Has not been confirmed.  Might just be a user misunderstanding.

> no_image, merge and shadows
> (setting no_image to an object in a merge causes that object to stop
> casting shadows)
> http://news.povray.org/vqfd0ucm5276q9j8sdh34afjliapc1kj0n@4ax.com

Logged as job000198.

> Isosurfaces *much* slower in beta 7?
> (isosurfaces with "evaluate" are now very slow)
> http://news.povray.org/3bdf24b3$1@news.povray.org

Already fixed in beta 9.

> Isosurface : 2 bugs
> (int() causes crash)
> http://news.povray.org/3c082dbe@news.povray.org

This was fixed in beta 9 but due to a usability problem did not make it into
source code used to build beta 9 versions other than the Mac beta 9.  It can
be removed once beta 10 is out.

> IsoCacti.pov
> (displays 754 evaluate warnings, most with incorrect values)
> http://news.povray.org/3c08c36c$1@news.povray.org

Fixed in next beta.

> Re: triangle texture interpolation
> (the second texture is on the first point and the third texture is used
> on the second and third points)
> http://news.povray.org/3C0A8288.DDA0905B@free.fr

Logged as job000199.

> Re: Workaround for function problems in beta 8 without scene file
> modification
> (using Include_Header in povray.ini crashes in some circumstances)
> http://news.povray.org/Xns9170BB3381723CoridonHenshaw@204.213.191.226

Same as function problems in beta 8.  Alreday fixed in beta 9.

> Crash with no objects in scene
> http://news.povray.org/3bd985b0@news.povray.org
> (also reported as http://news.povray.org/3C19B9EA.D2E16FBC@gmx.de

I cannot reproduce this.  Need to verify this bug still exists in beta 9.

> bug in sphere_sweep for removing parts of an object
> (discontinuous normals on inverse of sphere_sweep)
> http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl

Logged as job000200.  May or may not be related to job000176.

> color dot operators
> ((Color.red) doesn't work as a function parameter)
> http://news.povray.org/ofpr1ug9r6q3cak417pmj72bck6ufmgbtg@4ax.com

It does not work as *macro* parameter.  this is a very important difference.
Logged as job000201.

> Bicubic patch triangles disappear
> (When the triangles are fairly small)
> http://news.povray.org/3c23b26c@news.povray.org

Logged as job000202.

____________________________________________________
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

> > Camera is off by half a pixel
>
> Will be changed in a future beta of 3.5 if #version 3.5 is used.

So that's what you meant. :-) Thanks!

Anders

Post a reply to this message