POV-Ray : Newsgroups : povray.macintosh : Update for the Mac version of MegaPOV available Server Time
18 May 2024 05:05:01 EDT (-0400)
  Update for the Mac version of MegaPOV available (Message 1 to 4 of 4)  
From: Smellenbergh
Subject: Update for the Mac version of MegaPOV available
Date: 17 Jul 2001 14:07:02
Message: <1ewpeor.52fgnxqu7jiqN%smellenbergh@skynet.be>
An update of MacMegaPOV v 0.7 is available.

This is a maintenance version. The rendering engine is still at 0.7 with
no changes.
Most changes are to ensure better compatibility under OS X and Classic
versions with CarbonLib. 

MacMegaPov only: 
----------------
* Hitting the scrollbar no longer crashes the application under OS X.; 
* Added support for the mousewheel under OS X; 
* Fixed some dialogs, they would not present right under OS X; 
* Better Aqua support under OS X; 
* The preferences menu item is where it should be under OS X; 
*Added a 'Display Gamma' checkbox and edit field in the Misc pane of the
(application) preferences dialog. 


Yvo & Rene Smellenbergh

-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh


Post a reply to this message

From: nickshea64
Subject: 68k str() bug
Date: 20 Jul 2001 05:04:53
Message: <3B57F480.6555642D@aol.com>
Hi Tracers,

I have already posted this to povray.bugreports but thought
I'd post it here also.

I think I have found a bug with str() on a Mac 68k.

I have a macro which prints out a vector:

//---------------------------------------------------------------
// Macro PrintVector(V)
//---------------------------------------------------------------
#macro PrintVector(V)
 concat("<",str(V.x,4,4),",",str(V.y,4,4),",",str(V.z,4,4),">")
#end

This macro works fine on a PowerPC but not on 68k.

For example:

#local mPosition = <1.0, 5.0, 0.0>;
#debug concat("mPosition is: ", PrintVector(mPosition),"\n")

prints out:
mPosition: <-1.9375,2.1250,0.0000>

mPosition.x (which is 1.0) prints out as 1.9375 and
mPosition.y (which is 5.0) prints out as 2.1250

I can't get access to the 68k source right now, so I
don't know what's going on.

I'm using the last official compile for Mac 68k Version 3.1g r2 for FPU's.
My hardware is a Performa 600 with a 50 MHz MicroMac Diimo accelerator PDS
card.
Although the card patches Apple's SANE routines, the bug persists even when

I uncheck the SANE options in the Diimo Control Panel. Can anyone reproduce

this
bug on a 68k mac?

Any ideas anyone? TIA

--Nick
email: nic### [at] aolcom


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: 68k str() bug
Date: 21 Jul 2001 05:09:11
Message: <3b5946b7@news.povray.org>
In article <3B57F480.6555642D@aol.com> , nickshea64 <nic### [at] aolcom>  
wrote:

> I think I have found a bug with str() on a Mac 68k.

Unfortunately we no longer have any 68K Macs to test or verify if this is a
bug or not.  No similar problem has been reported, and 3.1 has been release
three years ago.

You could try to use the (much slower) version without FPU support and see
if it shows the same problem.  If the problem goes away then just use the
non-FPU version.

The other option is to use a Power Macintosh (even models with PCI bus, such
as a 7200 should be available for less $100 these days).  It would also
allow you to run future versions of POV-Ray as 3.1 is the last release to
support 68K Macs.

Sorry for not being able to offer more help or verify your problem,

    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

From: Nicholas Shea
Subject: Re: 68k str() bug
Date: 22 Jul 2001 00:53:15
Message: <3B5A5C87.4D056ADC@aol.com>
Thorsten Froehlich wrote:

> Unfortunately we no longer have any 68K Macs to test or verify if this is a
> bug or not.  No similar problem has been reported, and 3.1 has been release
> three years ago.

Humm; my performa 600 has a 68881 FPU added on the motherboard. The Diimo
accelartor has it's own on the PDS card (a 68882). I wonder if this has some
thing to do with it...

I have just got the 68k FPU source. I notice that the CodeWarrior project
is optimized for the 68881 FPU. But in the project settings, there is no
option for 68882. Another possibility. I will try various re-compiles to
see if I can solve the problem.

> You could try to use the (much slower) version without FPU support and see
> if it shows the same problem.  If the problem goes away then just use the
> non-FPU version.

I'll do that. But POV-Ray on 68k without an FPU? Ouch.

> The other option is to use a Power Macintosh (even models with PCI bus, such
> as a 7200 should be available for less $100 these days).

I have an old G3 which traces quite fast. I went to 68k because the PPC
is in
use by another. It was quite a shock going back to 68k; like walking
through treacle!

> Sorry for not being able to offer more help or verify your problem,

Thank you for replying Thorsten.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.