You also need to tell us what kind of Intel Mac it is. The Mini, MacBook, and one iMac have Intel GMA 950s, which have no hardware vertex processing, so a heavy vertex load can cause problems for them. There are solutions to that, but you can expect to have to optimize your engine with them in mind.

There are two kinds of processor -- PowerPC and Intel. Neither can run machine code designed for the other. Apple includes software with Intel Macs called Rosetta which transparently translates PowerPC machine code to Intel machine code, allowing PowerPC programs to run on Intel Macs. This translation is *slow*, and the resultant code is *slow*. A ballpark figure is that MHz-for-MHz of CPU, PowerPC code running on an Intel Mac will be at best 1/3 the speed it is on a PowerPC Mac.

A "universal binary" includes both PowerPC and Intel machine code, allowing the program to run at native speeds on both PowerPC and Intel machines.

"ATI Radeon iMac with 128MB VRAM" isn't a very solid description, but if that's a G5 iMac with a Radeon X600, then yes, an Intel Mac Mini or MacBook has a worse GPU (and almost every PowerPC Mac has a worse GPU).

Folks, this is an Apple-supported configuration. You get the option when you erase your disk at OS install time. Please be aware that it *does* matter that your strings in your source code match the names of your files on the disk!

OneSadCookie Wrote:Ah, I bet it's because I have a case-sensitive disk.

Folks, this is an Apple-supported configuration.

And does Xcode make any warnings about this when compiling?

You know like "Hey, .005% of the world might have a silly formatting system in effect, better run through every word of code thats worked for five years on three operating systems and re-write it for that one sad cookie"

OneSadCookie Wrote:You get the option when you erase your disk at OS install time.

When I bought this iMac and reformatted and reinstalled, that was not an option.

I reformatted a partition this morning, seven months after a Tiger upgrade and saw this "Case Sensitive" nonsense for the first time and thought "What kind of mad man would do that to their drive?"

Sure enough I check my email when I'm done with that and there is Keith, standing up in the sea of 25 million mac users, like something out of a Where's Waldo book.

OneSadCookie Wrote:Please be aware that it *does* matter that your strings in your source code match the names of your files on the disk!

It hasn't made any difference at all until Tiger which is maybe 50% of the OS X installed base, and of all the machines tested so far, you are the only one with CaSe_SeNsItIvItY.

Anyway, THAT issue will be dealt with in the future, just in case Sad Cookie-ism becomes a fashionable trend.

UB has been dealt with on normal case insensitive Macs.
Speeds boosted from 30FPS MAX on intel to 130FPS average.