Let the Quaking Begin!
Thresh's comments in BLACK
Kenn's comments in BLUE
First Glimpse
Thresh
…it worked! The game menu launched, and waited patiently for our input. A quick look in the maps directory yielded…a random Mac directory….well, bug #1. From the id server lists, we were already aware that the two maps included with the demo are q3test1 and q3test2. We loaded them up and took some timerefresh scores (as timedemo doesn't function in the demo). Note that the resolutions for both Highest Detail and Fastest Performance were set at 640x480.
| Detail Settings |
| Graphics Setting |
Highest Detail |
Fastest Performance |
| Resolution |
640x480 |
640x480 |
| Color Depth |
32-bit |
16-bit |
| Lighting |
Lightmap |
Vertex |
Geometric Detail
(curves and models) |
High |
Low |
Texture Detail
(0-3 slider) |
3 |
0 |
| Texture Quality |
32-bit |
Compressed |
| Texture Filter |
Trilinear |
Bilinear |
| |
Highest Detail |
Fastest Performance |
| Q3test1 |
34.1 |
66.8 |
| Q3test2 |
33.5 |
63.1 |
Kenn
Not too shabby, considering we're running on a 350Mhz processor. It's important to note here that the Rage128 isn't what you'll find on the Rage Fury or Rage Magnum product for the PC. The Macintosh Rage128 is PCI, and has a core clock of 75MHz and a memory clock of 75MHz. The PC Rage Fury (same Rage128 chipset) is an AGP 2x solution and is available in two clock speeds - the OEM version at 90MHz core, 90MHz memory, and the retail version clocks at 103Mhz/103MHz.
A little more research into id .plan files showed that upgrading the G3 firmware would provide a noticeable framerate improvement. We snagged the file off of Apple's site, performed the update, and restarted the game. True to word, everything sped up noticeably, as the new numbers will show.
| |
Highest Detail |
Fastest Performance |
| Q3test1 |
41.5 |
73.8 |
| Q3test2 |
39.4 |
69.8 |
Let's hear about Q3A!
Digg
Del.icio.us
Reddit
SU
furl
