Santaduck
10-11-2003, 09:43 PM
I know this isn't the latest news, but it's fairly recent...
1) UT2k4 will be released for Mac OS X soon after the PC release... since the PC is in November, I imagine something close to a Christmas release for OS X. Hopefully, Ryan Gordon's (http://www.icculus.org) presence at the 64bit AMD demo means that he is actively working on the G5 64 bit optimization for ut2k3/ut2k4 for Mac.
http://www.ataricommunity.com/forums/showthread.php?s=&threadid=320354
2) framerate tweak for ut2k3 & AA via OpenAL
Ryan Gordon (http://www.icculus.org) has a solution I found that helps framerates. He's the mac coder that is working on the final UT X port, and did the port for AA, and many other significant projects. I think he's doing the G5 optimization for UT2K3 as well, although I'm not sure.
Anyhow, he has an audio tweak (OpenAL) that results in MUCH less CPU load, and I have confirmed on my slow comp, and I'm sure it will be nicer on faster rigs.
The file is here. (http://icculus.org/~icculus/tmp/openal-osx-revolution71fix.tar.bz2)
Use Stuffit Expander, and you get a file called: openal.dylib
For both AA & UT2K3, replace the old openal.dylib file in the game's SYSTEM folder. (You will have to control-click the game icon, and select "show package contents" to access this folder.
more info is on his finger archives: 8/8/2003 (http://icculus.org/cgi-bin/finger/finger.pl?user=icculus&date=2003-08-08&time=00-20-32) and 8/3/2003 (http://icculus.org/cgi-bin/finger/finger.pl?user=icculus&date=2003-08-03&time=06-43-45)
here's a summary from Ryan:
Please note that this can be used to get you a better framerate in
ut2003, too...we're still spending about 7% of our CPU time just feeding
the audio device, which is not good. When I get around to the redesign I
was threatening, that 7% should drop to more like 0.1%. Still, the
current UT2003 version (which is a different codepath completely), is
sitting at 20 to 25 percent right now, so it's still a clear win for all
users, regardless of audio hardware, to use this.
Note that the 7% is spent in a separate thread, so dual CPU systems won't
see as dramatic a benefit as single CPU systems. Also, certain codepaths
will perform better due to Altivec optimizations on certain
conditions...but it SHOULD still work and give a speed boost over the
original version even on a G3.
1) UT2k4 will be released for Mac OS X soon after the PC release... since the PC is in November, I imagine something close to a Christmas release for OS X. Hopefully, Ryan Gordon's (http://www.icculus.org) presence at the 64bit AMD demo means that he is actively working on the G5 64 bit optimization for ut2k3/ut2k4 for Mac.
http://www.ataricommunity.com/forums/showthread.php?s=&threadid=320354
2) framerate tweak for ut2k3 & AA via OpenAL
Ryan Gordon (http://www.icculus.org) has a solution I found that helps framerates. He's the mac coder that is working on the final UT X port, and did the port for AA, and many other significant projects. I think he's doing the G5 optimization for UT2K3 as well, although I'm not sure.
Anyhow, he has an audio tweak (OpenAL) that results in MUCH less CPU load, and I have confirmed on my slow comp, and I'm sure it will be nicer on faster rigs.
The file is here. (http://icculus.org/~icculus/tmp/openal-osx-revolution71fix.tar.bz2)
Use Stuffit Expander, and you get a file called: openal.dylib
For both AA & UT2K3, replace the old openal.dylib file in the game's SYSTEM folder. (You will have to control-click the game icon, and select "show package contents" to access this folder.
more info is on his finger archives: 8/8/2003 (http://icculus.org/cgi-bin/finger/finger.pl?user=icculus&date=2003-08-08&time=00-20-32) and 8/3/2003 (http://icculus.org/cgi-bin/finger/finger.pl?user=icculus&date=2003-08-03&time=06-43-45)
here's a summary from Ryan:
Please note that this can be used to get you a better framerate in
ut2003, too...we're still spending about 7% of our CPU time just feeding
the audio device, which is not good. When I get around to the redesign I
was threatening, that 7% should drop to more like 0.1%. Still, the
current UT2003 version (which is a different codepath completely), is
sitting at 20 to 25 percent right now, so it's still a clear win for all
users, regardless of audio hardware, to use this.
Note that the 7% is spent in a separate thread, so dual CPU systems won't
see as dramatic a benefit as single CPU systems. Also, certain codepaths
will perform better due to Altivec optimizations on certain
conditions...but it SHOULD still work and give a speed boost over the
original version even on a G3.