Only tested on MacOS 10.6.x. may work with 10.5.x
http://www.mediafire.com/?d3twla66apd2rr5
EDIT: BZFS Plugins do not seem to work with my build
[UNOFFICAL] 2.0.17 64-bit Mac
Re: [UNOFFICAL] 2.0.17 64-bit Mac
What is the benefit of this build?
Re: [UNOFFICAL] 2.0.17 64-bit Mac
1) It's 64-bit
2) It has a higher 'GEEK' factor
2) It has a higher 'GEEK' factor
Re: [UNOFFICAL] 2.0.17 64-bit Mac
So in other words, no benefit and less compatible than the project-released binaries?
- Cobra_Fast
- Dev Monkey
- Posts: 322
- Joined: Sat Oct 07, 2006 11:51 am
- Location: Germany
- Contact:
Re: [UNOFFICAL] 2.0.17 64-bit Mac
Seconded. BZFlag doesn't make enough use of memory to benefit of a larger address range (in my tests it's using around 40 to 50 MiB).Constitution wrote:So in other words, no benefit and less compatible than the project-released binaries?
Re: [UNOFFICAL] 2.0.17 64-bit Mac
The only case where I've seen that 64-bit helps BZFlag is on linux. It resolves some of the collision issues (like getting stuck in teleporters).
- Bullet Catcher
- Captain
- Posts: 564
- Joined: Sat Dec 23, 2006 7:56 am
- Location: Escondido, California
Re: [UNOFFICAL] 2.0.17 64-bit Mac
What I still don't understand about that particular bug is that it occurs on 32-bit x86 Linux systems, but not on 32-bit x86 Mac OS X systems. In both cases BZFlag is compiled with gcc. Disabling all compiler optimizations for LocalPlayer.cxx does make the bug disappear on 32-bit Linux, but is not a satisfactory solution.blast wrote:The only case where I've seen that 64-bit helps BZFlag is on linux. It resolves some of the collision issues (like getting stuck in teleporters).
Re: [UNOFFICAL] 2.0.17 64-bit Mac
It has to do with how GCC does it's floating point math in that version.
JeffM
Re: [UNOFFICAL] 2.0.17 64-bit Mac
[flamewar]Or save yourself $1000 and get a PC, which works even better for playing BZFlag.[/flamewar]