Anyone?

I've only just downloaded it (a day or so ago), but am finding it 
slows down enormously (under 9.2.2 on a G4 @ 400MHz - I don't have 
X at all - looks to freeze, but hasn't, quite) soon after it starts 
rendering. [Reading the threads back to August sometime hasn't shed 
much light :-(]

Maybe another question should be asked first:
is anyone not having lockups/slowdowns under 9.2.2?
[Base extensions vs all+a few 3rd party seems to make no 
difference]
TIA

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

In article <0001HW.BA2B9D9300039FDC0F42B1F0@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> I've only just downloaded it (a day or so ago), but am finding it
> slows down enormously (under 9.2.2 on a G4 @ 400MHz - I don't have

If you want slower rendering you can just move the "Application
Friendliness" slider to "Lazy" in the Preferences: general pane.

As many people never read the manual they never found this slider and
consequently never used it in previous versions and then complained that
rendering was slow.  So now the default is more aggressive in 3.5...

> X at all - looks to freeze, but hasn't, quite) soon after it starts
> rendering. [Reading the threads back to August sometime hasn't shed
> much light :-(]

This only happens with a few specific configurations.  POV-Ray either works
on your configuration (which it seems it does) or it won't.

    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 <0001HW.BA2B9D9300039FDC0F42B1F0@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> Maybe another question should be asked first:
> is anyone not having lockups/slowdowns under 9.2.2?

POV-Ray is developed under Mac OS 9.2.2 so if it would lockup everywhere I
could not develop it, could I?

I saw your bugreport you submitted, and from that I saw that only the render
commands are "slow" for you in a particular slow to render and complex scene
(abyss.pov).  What happens is that it takes until a line has completed to
render until rendering is stopped.  That is why it appears slow for you...

If you really want, you can force the rendering into the background using
this hidden option:

You can control if preemptive threading or cooperative threading is used.
By default cooperative threading will be used.  In order to change this
setting go the the POV-Ray preferences dialog.  Switch to the Editor pane.
Now hold down the "option" key* and switch back to the General pane.  Now
you should see another checkbox:  The checkbox for preemptive threading
which will only take effect after you restart POV-Ray!

While it won't make the rendering faster (unless you have a dual G4), it
will make the whole GUI react immediately as rendering takes place in the
background.  The only catch is that parsing will be a tiny bit slower.


    Thorsten


* The "option" key is the one usually marked "alt" on German keyboards, not
sure what it is called on your keyboard...


____________________________________________________
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

On Sun, 22 Dec 2002 21:50:48 +1100, Thorsten Froehlich wrote
(in message <3e059908$1@news.povray.org>):

> In article <0001HW.BA2B9D9300039FDC0F42B1F0@news.povray.org> , Martin Crisp
> <Spa### [at] tesseractcomau>  wrote:
> 
>> Maybe another question should be asked first:
>> is anyone not having lockups/slowdowns under 9.2.2?
> 
> POV-Ray is developed under Mac OS 9.2.2 so if it would lockup everywhere I
> could not develop it, could I?

OK. I wasn't aware of what systems were in use for development. 

As my bug report noted - the behaviour I'm describing occurs 
whether I boot with my (few) 3rd party extensions, or with the Base 
9.2.2 set. I can install a fresh system on an empty partition... 
I'll let you know how that goes. Failing that, and given the 
similarity with symtoms that others have reported, what's weird 
about _your_ system?

> I saw your bugreport you submitted, and from that I saw that only the render
> commands are "slow" for you in a particular slow to render and complex scene
> (abyss.pov).  What happens is that it takes until a line has completed to
> render until rendering is stopped.  That is why it appears slow for you...

Nope. I've taken that into account. 

Abyss.pov renders at the speed I'd expect for 30 seconds, then 
slows drastically - in the first 30 seconds it maybe manages 45 
scanlines, in the next 15 minutes it manages about 15 scanlines. 

The other file I've tried (referred to in the bugreport) can 
complete (just) in 30 seconds with some rendering options (no 
anti-aliasing, 320 x 240). If I turn anti-aliasing on (original, 
0.3, 2, 0.1) then it also falis to complete, getting about 3/4 of 
the way through the render at normal speed (30 seconds), then 
slowing down.

Consistently: 28-30 seconds after the preview window is displayed, 
my machine goes into near catalepsy - screen updates happen once 
every 60 seconds thereafter.

Subject: 7Facets.pov - a very simple scene
in povray.binaries.scene-files


> If you really want, you can force the rendering into the background using
> this hidden option:
> 
> You can control if preemptive threading or cooperative threading is used.
> By default cooperative threading will be used.  In order to change this
> setting go the the POV-Ray preferences dialog.  Switch to the Editor pane.
> Now hold down the "option" key* and switch back to the General pane.  Now
> you should see another checkbox:  The checkbox for preemptive threading
> which will only take effect after you restart POV-Ray!

I'll see what difference it makes. Thanks.

 
> While it won't make the rendering faster (unless you have a dual G4), it
> will make the whole GUI react immediately as rendering takes place in the
> background.  The only catch is that parsing will be a tiny bit slower.

It's not the GUI that's annoying me, other than it's change in 
behaviour indicates other things going awry. 

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

Martin Crisp <Spa### [at] tesseractcomau> wrote:

[...]
> 
> Abyss.pov renders at the speed I'd expect for 30 seconds, then 
> slows drastically - in the first 30 seconds it maybe manages 45 
> scanlines, in the next 15 minutes it manages about 15 scanlines. 
Hmm, always after 30 secons you say...
This looks like a setting in the energy saver control panel.
I don't have that option on my dual but on my iMac it was there.
You should try this: once POV start to render slow, simply move the
mouse a little bit.
If rendering speeds up again, you should go an take a look at the energy
savings panel.
I don't now the correct name but look for something to slow down the
cpu.

Yvo
-- 
MacMegaPOV at:
http://users.skynet.be/smellenbergh

E-mail: yvo### [at] gmxnet

Post a reply to this message

On Mon, 23 Dec 2002 1:18:32 +1100, Yvo Smellenbergh wrote
(in message <1fnlm8j.1ve5dhx1kfrl2aN%yvos.s@gmx.net>):

> Martin Crisp <Spa### [at] tesseractcomau> wrote:
> 
> [...]
>> 
>> Abyss.pov renders at the speed I'd expect for 30 seconds, then 
>> slows drastically - in the first 30 seconds it maybe manages 45 
>> scanlines, in the next 15 minutes it manages about 15 scanlines. 
> Hmm, always after 30 secons you say...
> This looks like a setting in the energy saver control panel.

Nope. Set to sleep the monitor after <checks> something a little 
more than 20 minutes. [I've been tooling around with a genetic 
algorithm I've written, so I don't sleep the CPU.]

> I don't have that option on my dual but on my iMac it was there.
> You should try this: once POV start to render slow, simply move the
> mouse a little bit.
> If rendering speeds up again, you should go an take a look at the energy
> savings panel.

Nope. I've been keeping an eye on the machine, and stopping the 
monitor from sleeping, but that made no difference. Every minute 
the preview and the clock would update, and if there'd been a 
keypress or mouseclick in the meantime then it would be effected 
then.

> I don't now the correct name but look for something to slow down the
> cpu.

Energy Saver is the only thing, and it's set way beyond 30 seconds.

Thanks for the thought though.

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

On Sun, 22 Dec 2002 22:29:28 +1100, Martin Crisp wrote
(in message <0001HW.BA2BED48001659E70D78DFC0@news.povray.org>):

[snip]

> Consistently: 28-30 seconds after the preview window is displayed, 
> my machine goes into near catalepsy - screen updates happen once 
> every 60 seconds thereafter.
> 
> Subject: 7Facets.pov - a very simple scene
> in povray.binaries.scene-files

[snip]

Here's a jpg of the rendered scene from when I first made it (at 
320x240):
http://members.ozemail.com.au/~martincrisp/7facets.jpg

Here are some screenshots of the preview window taken a few seconds 
after pausing the render, but at 640x480
As soon as my machine slowed down (+ 60 seconds):
http://members.ozemail.com.au/~martincrisp/7facets_30secs.jpg

After an hour:
http://members.ozemail.com.au/~martincrisp/7Facets_1hr.jpg

2hours
http://members.ozemail.com.au/~martincrisp/7Facets_2hrs.jpg

3 hours
http://members.ozemail.com.au/~martincrisp/7Facets_3hrs.jpg

And the output file -> jpg when I stopped it (also at 3 hrs)
http://members.ozemail.com.au/~martincrisp/7Facets_stopped.jpg

FWIW

It's a simple scene that shouldn't take a G4 400 more than a minute 
or two. [and didn't in the past].

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

Martin Crisp wrote:

> Anyone?
> 
> I've only just downloaded it (a day or so ago), but am finding it 
> slows down enormously (under 9.2.2 on a G4 @ 400MHz - I don't have 
> X at all - looks to freeze, but hasn't, quite) soon after it starts 
> rendering. [Reading the threads back to August sometime hasn't shed 
> much light :-(]
> 
> Maybe another question should be asked first:
> is anyone not having lockups/slowdowns under 9.2.2?
> [Base extensions vs all+a few 3rd party seems to make no 
> difference]
> TIA


Add me to the list, the render queue stays open and I have to quit to 
get it to stop.  I see a lot of people have this problem but I see no 
answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?

Post a reply to this message

Dale Walsh wrote:

>Add me to the list, the render queue stays open and I have to quit to
>get it to stop.  I see a lot of people have this problem but I see no
>answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?

I'm running on a 500MHz G4 PowerBook, OS 9.2.2, Carbon Lib 1.6, and I
have no problems with the rendering speed or the queue. I set POV-Ray
to Tyrannical or Selfishly fast and turned all the sleep and power saving
settings off.


By the way, I posted these questions a few months ago and received no
response, so I'll try again:

I've set my Edit-> Preferences...-> Editor font to Courier 12, but when I
open new windows they come up in the default font and size. Only by
reselecting the Courier popup in Preferences do the windows display using
my editor preference font settings. Is this problem unique to me?

While I'm here, it would be nice (for me anyway) if POV-Ray Mac asked if you
were sure you wanted to quit. I use the apple-1 and apple-2 keys to pop up
windows and sometimes I accidentally hit apple-q. It will quit without
question even if I've modified some text.

Other than these minor complaints, I've found the editor a joy to use; the
color coding really helps code clarity.

Okay, one other question. POV-Ray Mac crashes when I try to render a large
PICT file, such as 6600x4400 resolution. PNG and Targa work fine, but
Photoshop won't let me look at partial renders in those formats so I prefer
PICT. Is there a limit to how big a PICT file can be?

Post a reply to this message

In article <web.3e06024d42f46e194b5522fd0@news.povray.org> , "Renderdog" 
<slo### [at] hiwaaynet> wrote:

> I've set my Edit-> Preferences...-> Editor font to Courier 12, but when I
> open new windows they come up in the default font and size. Only by
> reselecting the Courier popup in Preferences do the windows display using
> my editor preference font settings. Is this problem unique to me?

No, it is a bug that will be fixed in a future version.

> While I'm here, it would be nice (for me anyway) if POV-Ray Mac asked if you
> were sure you wanted to quit. I use the apple-1 and apple-2 keys to pop up
> windows and sometimes I accidentally hit apple-q. It will quit without
> question even if I've modified some text.

Yes, unfortunately this sometimes happens.  The cause is a bit complicated
and related to an incorrect Apple Event being sent internally.  Eventually
this will be fixed.

> Okay, one other question. POV-Ray Mac crashes when I try to render a large
> PICT file, such as 6600x4400 resolution. PNG and Targa work fine, but
> Photoshop won't let me look at partial renders in those formats so I prefer
> PICT. Is there a limit to how big a PICT file can be?

Yes, they have to be smaller than 4096 pixels.  There used to be an error
message if this was detected before rendering before.  As that code was
replaced, the error message seems to have been 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

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

> Yes, they have to be smaller than 4096 pixels.  There used to be an error
> message if this was detected before rendering before.  As that code was
> replaced, the error message seems to have been lost :-(

I thought the PICT limit was 32768x32768...maybe I'm thinking of the 
QuickDraw API.

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/

Post a reply to this message

In article <chr### [at] netplexaussieorg> , 
Christopher James Huff <chr### [at] maccom>  wrote:

> I thought the PICT limit was 32768x32768...maybe I'm thinking of the
> QuickDraw API.

The limit is of Picts is that of PixMaps.  To be precise, the rowbytes field
uses a few of the upper bits to store other information.  This design
problem dates back to System 1 and the original QuickDraw.  While it is
fixed in Mac OS 9 and later, it has never been documented by Apple how to
access the 32 bit rowbyte field.  And the Pict image format would not be
able to handle it either.

So, while QuickDraw can handle 32k*32k pixels, one cannot create a single
bitmap of such a big image.  For this this reason since POV-Ray 3.1 Mac the
preview is split into tiles, which works around the problem to some extend.
However, doing the same for rendering to Pict images would require enormous
amounts of memory and such Pict images would not be supported by all
applications (also in theory it would be possible to create such a Pict
image) or System 7.x and earlier.

    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 Mon, 23 Dec 2002 5:19:57 +1100, Renderdog wrote
(in message <web.3e06024d42f46e194b5522fd0@news.povray.org>):

> Dale Walsh wrote:
> 
>> Add me to the list, the render queue stays open and I have to quit to
>> get it to stop.  I see a lot of people have this problem but I see no
>> answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?

I haven't looked at the render queue. The render progress dialog 
does the same for me as others have reported - i.e. never has 
information in it, scrolling candy-cane the entire time [even after 
a render finishes - small scenes only...].

> I'm running on a 500MHz G4 PowerBook, OS 9.2.2, Carbon Lib 1.6, and I
> have no problems with the rendering speed or the queue. I set POV-Ray
> to Tyrannical or Selfishly fast and turned all the sleep and power saving
> settings off.

My G4 400 is a tower [Zip drive, DVD-RAM, USB CDR/CD-RW, internal 
scsi card, 256MB, 20GB and 80GB ATA drives].

[snip - answered since]

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

Martin Crisp wrote:

[snip]

>My G4 400 is a tower [Zip drive, DVD-RAM, USB CDR/CD-RW, internal
>scsi card, 256MB, 20GB and 80GB ATA drives].
>

Now tested on another machine: G4 500 MHz [9.2.2 Carbonlib 1.5], more
extensions than I could list (a graphic designer's machine).

Scenes tested: abyss.pov; and parallel_lights.pov [This last needed to
be done at 640x480 to be up long enough for the slowdown to be apparent.]

Same problem, timings are slightly different as to when the slowdown
happens, but once it happens screen updates are every minute (going by
menubar clock). One difference in config: this machine has only one HD, so
POV-Ray is on the same partition as the system (on mine they're on separate
(physical) disks.

Have Fun
Martin
--
To email me don't change the email address, unless you want to.

Kinky: what I do that you wouldn't.
Perverted: what you do that I wouldn't.

Post a reply to this message

On Sun, 22 Dec 2002 22:29:28 +1100, Martin Crisp wrote
(in message <0001HW.BA2BED48001659E70D78DFC0@news.povray.org>):

[snip]

> As my bug report noted - the behaviour I'm describing occurs 
> whether I boot with my (few) 3rd party extensions, or with the Base 
> 9.2.2 set. I can install a fresh system on an empty partition... 
> I'll let you know how that goes. Failing that, and given the 
> similarity with symtoms that others have reported, what's weird 
> about _your_ system?

[snip]

OK, did that. Installed 9.0.4(Z1)->9.1->9.2.1->9.2.2
Left CarbonLib at 1.4
No other software bar what apple dumped on the HD.

Put POV-Ray on the same partition.
Tried rendering 7Facets.pov with anti-aliasing @640x480.

Same result as previous.

Copied POV-Ray to my wife's machine:
7500 upgraded to a G3@312MHz, 64MB memory [+VM @ 170MB - so she can 
play Civ III, really slowly :-)], OS Z1-9.1, CarbonLib 1.5.
Tried rendering 7Facets.pov with anti-aliasing @640x480.

Same result.

4 machines, 4 identical slowdowns.

Suggestions of what to try next most welcome.

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

In article <0001HW.BA2D0F4B0002F2930F175220@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> 4 machines, 4 identical slowdowns.

No, that just does not make sense.  And as you have noticed, nobody else is
having such a problem.  Maybe you have a corrupted download or something
like that.  Or you got a virus that attached itself to POV-Ray and thus you
copied it each time.  What you report does not even make sense :-(

    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

Thorsten Froehlich <tho### [at] trfde> wrote:

> > 4 machines, 4 identical slowdowns.
> 
> No, that just does not make sense.  And as you have noticed, nobody else is
> having such a problem.  Maybe you have a corrupted download or something
> like that.  Or you got a virus that attached itself to POV-Ray and thus you
> copied it each time.  What you report does not even make sense :-(
>     Thorsten


Thorsten,

I can't believe you call him mad ! If you start insulting everybody
that is reporting a bug, then we're not finished yet. Pov-Ray 3.5 
still has problems on Mac OS 9, and I suppose you know it. It seems
to me that you, as everybody else in this newsgroup, should rather 
thank Martin for the time he spends trying to make things advance.

Btw, what does internal error -10000 means ? I got it several times
this morning after switching to preemptive threading as you suggested
and experiencing slowdowns similar to Martin's symptoms...
See this link for a screenshot :

http://cassio.free.fr/divers/Screen_error.png

I could fill a more fromal bug report if that helps.

Sincerely yours,
Stephane.

Post a reply to this message

On Mon, 23 Dec 2002 20:30:52 +1100, Thorsten Froehlich wrote
(in message <3e06d7cf@news.povray.org>):

> In article <0001HW.BA2D0F4B0002F2930F175220@news.povray.org> , 
> Martin Crisp <Spa### [at] tesseractcomau>  wrote: 
> 
>> 4 machines, 4 identical slowdowns.
> 
> No, that just does not make sense.  And as you have noticed, 

Unfortunately, sense or not, it is what I'm seeing.

BUT: Not with the preemptive threading turned on! [Only just tried 
that.]

The differences it made were:
1) the render progress dialog shows details!
2) I can type this while it is rendering in the background [set on 
lowest throttle, of course]
3) no slowdown after ~30 seconds, updates to the preview are smooth 
and continuous, what I would 'expect', rather than a line exactly 
every 60 seconds.
4) if I wait another minute or few (currently line 216 of 480) I 
predict I'll see a render finish 'cleanly'. It did.
5) a fatal error(-10000) when I quit partway through a render.
6) quitting after a render finished was substantially quicker than 
previous (a few seconds).

> nobody else is having such a problem.  Maybe you have a 

[with preemptive threading off:]
Nobody else is reporting it the same as me, perhaps. If someone's 
menubar clock shows the time in seconds, and it updates for the 
first little while of a render, then stops dead - would they report 
that as a slowdown, or a freeze? Several others have reported 
freezes. Others have reported that renders never start on big 
scenes. Which is what I get if I try to render (2^n)-1 differences 
of spheres nested inside each other using a while loop (and a chunk 
then taken out of all of them by subtracting a box), when n>11. 
(n=11 starts to render after about 20 seconds or so, n=12 doesn't 
after 10 minutes). Spheres inside spheres, radii halving.



> corrupted download or something like that.  Or you got a virus 

I've used 2 separate downloads, one on my local machines, and one 
on the graphic designer's machine (the G4 500 with CarbonLib 1.5). 
I downloaded this latter several days ago, but only unpacked it 
today. The .smi is mounted without reporting a checksum error. 
Corrupted download is very unlikely. I haven't transferred any data 
to that machine from home, so viral contamination is unlikely too. 
[And I've no other 'symptoms' of a virus and the only other 
slowdown I have is my newsreader when it's trying to deal with 
subscriptions with more than 50,000 articles. Or old versions of 
applescript that have memory leaks when they open and close files]


> that attached itself to POV-Ray and thus you copied it each 
> time.  What you report does not even make sense :-( 

If it made sense I (probably - I majored in Comp Sci, graphics and 
digital image processing my best subjects) wouldn't be needing to 
ask.
[But I don't read C very well and haven't kept up with what Carbon 
did to the Mac API, so looking at the source wouldn't help. :-(]

I'm just reporting a problem I have (and from what others have said 
that they may have too, but are describing differently) in the hope 
of finding a solution.

Does knowing it works fine with preemptive threading turned on help 
any?

Have Fun
Martin [much happier :-)]
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

On Mon, 23 Dec 2002 22:48:46 +1100, Stéphane_Nicolet wrote
(in message <1fnn944.1lvwmom1f70r48N%cassio@free.fr>):

> Thorsten Froehlich <tho### [at] trfde> wrote:
> 
>>> 4 machines, 4 identical slowdowns.
>> 
>> No, that just does not make sense.  And as you have noticed, nobody else is
>> having such a problem.  Maybe you have a corrupted download or something
>> like that.  Or you got a virus that attached itself to POV-Ray and thus you
>> copied it each time.  What you report does not even make sense :-(
>> Thorsten
> 
> 
> Thorsten,
> 
> I can't believe you call him mad ! If you start insulting everybody

I can, and I don't hold it against him. If it works on Thorsten's 
machine (and presumably others) then that's great. It _is_ 
difficult writing code and then debugging it long distance, 
particularly if you can't reproduce the bug (and I shudder at the 
thought of doing it for a raytracer - and that's after reading 
Principles of Computer Graphics :-)). [Thorsten: remember that 
weird 'is it pov or is it the mac' bug to do with CDs and macros in 
3.0?] I write code for a living (not as close to the metal as C or 
C++, however), and have to support users who don't read 
instructions, don't listen (and can't in one guy's case...), and so 
on. Thinking an individual user is mistaken is an easy, and 
foregiveable, trap to fall into.

> that is reporting a bug, then we're not finished yet. Pov-Ray 3.5 
> still has problems on Mac OS 9, and I suppose you know it. It seems
> to me that you, as everybody else in this newsgroup, should rather 
> thank Martin for the time he spends trying to make things advance.
> 
> Btw, what does internal error -10000 means ? I got it several times
> this morning after switching to preemptive threading as you suggested
> and experiencing slowdowns similar to Martin's symptoms...

Likewise, quitting when a render was partway through, and PT was 
on. [After seeing the render progress dialog progress... I'm in 
love ;-)]

> See this link for a screenshot :
> 
> http://cassio.free.fr/divers/Screen_error.png
> 
> I could fill a more fromal bug report if that helps.

Have Fun
Martin
-- 
a logician telling a computer programmer about logic, is like a cat 
telling a fish about being wet.
[author unknown, to me. Yes, I know it's a two-edged sword, 
thanks.]

Almost always SMASHed

Post a reply to this message

In article <0001HW.BA2D4A770010D86F04AF8FF0@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> Does knowing it works fine with preemptive threading turned on help
> any?

Yes, I assumed you had it on for the four tests and then your report would
not have made sense ... if the effect goes away with it being enabled, then
leave it on (also the switch is hidden, it will remain in effect when
restarting POV-Ray).

    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 Mon, 23 Dec 2002 23:40:17 +1100, Thorsten Froehlich wrote
(in message <3e070434$1@news.povray.org>):

> In article <0001HW.BA2D4A770010D86F04AF8FF0@news.povray.org> , Martin Crisp
> <Spa### [at] tesseractcomau>  wrote:
> 
>> Does knowing it works fine with preemptive threading turned on help
>> any?
> 
> Yes, I assumed you had it on for the four tests and then your report would
> not have made sense ... if the effect goes away with it being enabled, then
> leave it on (also the switch is hidden, it will remain in effect when
> restarting POV-Ray).

Sorry, I just hadn't gotten to that - you seemed unconvinced that I 
was having the problem in the first place.

Thanks for the help. 

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

In article <1fnn944.1lvwmom1f70r48N%cassio@free.fr> , cassio@free.fr 
(Stéphane Nicolet) wrote:

> I can't believe you call him mad ! If you start insulting everybody
> that is reporting a bug, then we're not finished yet. Pov-Ray 3.5
> still has problems on Mac OS 9, and I suppose you know it.

No, it is being developed and tested on Mac OS 9.2.2.  And there is a very
big difference between saying a report does not make sense and calling
someone mad!

> Btw, what does internal error -10000 means ? I got it several times
> this morning after switching to preemptive threading as you suggested
> and experiencing slowdowns similar to Martin's symptoms...

See, I frequently get bugreports in the style you are using as well. But how
am I supposed to be able to get the problem without a screenshot if you
forget to mention 90% of the important information?  If you read the error
message carefully you will notice that it nowhere says something about an
"internal error" and even tells you that you are not supposed to know and
that the error number is there for "internal reference", so you just have to
report what it says ;-)

The numbers are regular Mac OS error codes, so this one is
"errAEEventFailed", which simply means that sending an Apple Event, probably
the one to stop the render, failed for some reason.

    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

In article <0001HW.BA2D4DB700119C0004AF8FF0@news.povray.org> , Martin Crisp
<spa### [at] tesseractcomau>  wrote:

>  [Thorsten: remember that
> weird 'is it pov or is it the mac' bug to do with CDs and macros in
> 3.0?]

Yes, I remember.  It turned out it was a bug in the Finder which would set
some global working directory settings made by the C library.  I think I
recall sending you an email over a year later when Apple had finally fixed
the Finder in a newer Mac OS version...

    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 Tue, 24 Dec 2002 0:01:21 +1100, Thorsten Froehlich wrote
(in message <3e070923$1@news.povray.org>):

> In article <0001HW.BA2D4DB700119C0004AF8FF0@news.povray.org> , Martin Crisp
> <spa### [at] tesseractcomau>  wrote:
> 
>> [Thorsten: remember that
>> weird 'is it pov or is it the mac' bug to do with CDs and macros in
>> 3.0?]
> 
> Yes, I remember.  It turned out it was a bug in the Finder which 
> would set some global working directory settings made by the C 
> library.  I think I recall sending you an email over a year 
> later when Apple had finally fixed the Finder in a newer Mac OS 
> version... 

Yep. Jul 99 (bug reported) vs Jan 01 (email notification of fix).

I don't play CDs while rendering anymore, I got out of the habit 
:-)
Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

Yes, Same here, 867Mhz dual G4. OS 9.9.2 or OSX 10.2.3, Carbon Lib 1.6. 
And I'm rendering very simple scenes.
John


Dale Walsh wrote:
> Martin Crisp wrote:
> 
>> Anyone?
>>
>> I've only just downloaded it (a day or so ago), but am finding it 
>> slows down enormously (under 9.2.2 on a G4 @ 400MHz - I don't have X 
>> at all - looks to freeze, but hasn't, quite) soon after it starts 
>> rendering. [Reading the threads back to August sometime hasn't shed 
>> much light :-(]
>>
>> Maybe another question should be asked first:
>> is anyone not having lockups/slowdowns under 9.2.2?
>> [Base extensions vs all+a few 3rd party seems to make no difference]
>> TIA
> 
> 
> 
> Add me to the list, the render queue stays open and I have to quit to 
> get it to stop.  I see a lot of people have this problem but I see no 
> answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?
> 
> 
>

Post a reply to this message

rThorsten Froehlich <tho### [at] trfde> wrote:

> In article <1fnn944.1lvwmom1f70r48N%cassio@free.fr> , cassio@free.fr 
> (Stéphane Nicolet) wrote:
> 
> > I can't believe you call him mad ! If you start insulting everybody
> > that is reporting a bug, then we're not finished yet. Pov-Ray 3.5
> > still has problems on Mac OS 9, and I suppose you know it.
> 
> No, it is being developed and tested on Mac OS 9.2.2.  And there is a very
> big difference between saying a report does not make sense and calling
> someone mad!
> 
> > Btw, what does internal error -10000 means ? I got it several times
> > this morning after switching to preemptive threading as you suggested
> > and experiencing slowdowns similar to Martin's symptoms...
> 
> See, I frequently get bugreports in the style you are using as well. But how
> am I supposed to be able to get the problem without a screenshot if you
> forget to mention 90% of the important information?  If you read the error
> message carefully you will notice that it nowhere says something about an
> "internal error" and even tells you that you are not supposed to know and
> that the error number is there for "internal reference", so you just have to
> report what it says ;-)
> 
> The numbers are regular Mac OS error codes, so this one is
> "errAEEventFailed", which simply means that sending an Apple Event, probably
> the one to stop the render, failed for some reason.
> 
>     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 Tue, 24 Dec 2002 2:46:09 +1100, John Dribus wrote
(in message <3E0### [at] earthlinknet>):

[top-post moved]

> Dale Walsh wrote:

[snip me]

>> 
>> Add me to the list, the render queue stays open and I have to quit to 
>> get it to stop.  I see a lot of people have this problem but I see no 
>> answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?

> Yes, Same here, 867Mhz dual G4. OS 9.9.2 or OSX 10.2.3, Carbon Lib 1.6. 
> And I'm rendering very simple scenes.
> John

Thorsten's advice cured my symptoms:
<paste>
> If you really want, you can force the rendering into the background using
> this hidden option:
> 
> You can control if preemptive threading or cooperative threading is used.
> By default cooperative threading will be used.  In order to change this
> setting go the the POV-Ray preferences dialog.  Switch to the Editor pane.
> Now hold down the "option" key* and switch back to the General pane.  Now
> you should see another checkbox:  The checkbox for preemptive threading
> which will only take effect after you restart POV-Ray!
</paste>

Have Fun
Martin
-- 
aa #(2^8)*(2^3-2^0)
[...]Et sepultus resurrexit; certum est, quia impossibile.
-- Tertullian

Almost always SMASHed

PGP Key (ID 0xED55A6D0) Fingerprint:
A7C7 F865 B317 ABBB B10E  D8AC F4AD 347D ED55 A6D0

Post a reply to this message

Thorsten Froehlich wrote:

>
> If you really want, you can force the rendering into the background using
> this hidden option:
>
> You can control if preemptive threading or cooperative threading is used.
> By default cooperative threading will be used.  In order to change this
> setting go the the POV-Ray preferences dialog.  Switch to the Editor pane.
> Now hold down the "option" key* and switch back to the General pane.  Now
> you should see another checkbox:  The checkbox for preemptive threading
> which will only take effect after you restart POV-Ray!

This tip solved a lot of the problems I've had. Finally I can use 3.5 on my
laptop. Thank you! :-)

Tom

Post a reply to this message

In article <0001HW.BA2B9D9300039FDC0F42B1F0@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> Anyone?

Get the POV-Ray 3.5.1 Public Release Candidate 1 (expires March 25th) from
<http://mac.povray.org/download/macosx102.html>

    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