I thought it would be safer to change the declarations so I did that instead of casting.
PyAmanith and macholib are installed. Where is the Mac revision of the FretsOnFire source code? The readme says that there are some changes, notably src/setup_mac.py. I can't seem to find it - and it is not included in the MacSupport download. Thanks again!
MAC OS X Version - Trouble installing new version
Forum rules
- Before posting in this section please make sure your question has not already been answered:
- Read the FAQs and stickied topics. In particular: /******READ THIS POST BEFORE POSTING IN THIS SECTION!******\
- Visit the Wiki: http://fretsonfire.wikidot.com/
- Please try to search the forums before posting
- Questions about FoFiX?
- For general help, visit the project's Wiki: http://code.google.com/p/fofix/w/list
- Problem running FoFiX from git? Ask ALL your questions in the FoFiX forum
This topic is 18 years and 1 week old. Instead of replying, please begin a new topic, or search for another related topic that may be more suitable.
Great! The changes you mention are exactly the ones that are unfortunately currently missing by a mistake (I'll send some mail to hurry that...). It's not as bad as it sounds, though. Without them, you can't make the .app, and I'm getting random crashes on startup (some SDL/PyGame threading thing), but I'm able to run it with "python fretsonfire.py".
But if you're in a hurry...
** In GameEngine.py
After Engine.(self, fps = fps, ......)
add code:
"""
if sys.platform != 'darwin':
pygame.init()
"""
After bufferSize = .... add:
"""
if sys.platform != 'darwin':
self.audio.open(frequency = frequency, bits = bits, stereo = stereo, bufferSize = bufferSize)
else:
self.audio.pre_open(frequency = frequency, bits = bits, stereo = stereo, bufferSize = bufferSize)
pygame.init()
"""
** In Audio.py
Add method:
def pre_open(self, frequency = 22050, bits = 16, stereo = True, bufferSize = 1024):
pygame.mixer.pre_init(frequency, -bits, stereo and 2 or 1, bufferSize)
return True
**
But if you're in a hurry...
** In GameEngine.py
After Engine.(self, fps = fps, ......)
add code:
"""
if sys.platform != 'darwin':
pygame.init()
"""
After bufferSize = .... add:
"""
if sys.platform != 'darwin':
self.audio.open(frequency = frequency, bits = bits, stereo = stereo, bufferSize = bufferSize)
else:
self.audio.pre_open(frequency = frequency, bits = bits, stereo = stereo, bufferSize = bufferSize)
pygame.init()
"""
** In Audio.py
Add method:
def pre_open(self, frequency = 22050, bits = 16, stereo = True, bufferSize = 1024):
pygame.mixer.pre_init(frequency, -bits, stereo and 2 or 1, bufferSize)
return True
**
I made the changes you listed but now there are new errors. Here's the output upon running fretsonfire.py:
CPSEnableForegroundOperation (1010, (0, 6815745))
Traceback (most recent call last):
File "fretsonfire.py", line 61, in ?
engine = GameEngine(config)
File "/Users/tim/Projects/FretsOnFire/src/GameEngine.py", line 148, in
self.video.setMode((width, height), fullscreen = fullscreen, multisamples = multisamples)
File "/Users/tim/Projects/FretsOnFire/src/Video.py", line 51, in setMode
pygame.display.gl_set_attribute(pygame.GL_RED_SIZE,
pygame.error: video system not initialized
Perhaps this will go away upon the completion of what you're working on, though. No rush, don't worry. I had some spare time so I figured I might as well try.
CPSEnableForegroundOperation (1010, (0, 6815745))
Traceback (most recent call last):
File "fretsonfire.py", line 61, in ?
engine = GameEngine(config)
File "/Users/tim/Projects/FretsOnFire/src/GameEngine.py", line 148, in
self.video.setMode((width, height), fullscreen = fullscreen, multisamples = multisamples)
File "/Users/tim/Projects/FretsOnFire/src/Video.py", line 51, in setMode
pygame.display.gl_set_attribute(pygame.GL_RED_SIZE,

pygame.error: video system not initialized
Perhaps this will go away upon the completion of what you're working on, though. No rush, don't worry. I had some spare time so I figured I might as well try.
I didn't even get to the point where it crashes instead of running, because the 37.9 MB OS X download seems to have been replaced by a 4 KB file with a checksum of d14a1b4f9c72814fdd7fa19cbaccb1b5
Additionally, the associated os x files at http://louhi.kempele.fi/~skyost....ort.zip
return a page that says
"Warning: Panda GateDefender Performa has detected unauthorized content in the following file: fretsonfire-macsupport.zip
The download from http://louhi.kempele.fi/~skyost....ort.zip has been blocked"
So I'm unable to test things on my computer/offer any input at all here. Something strange is afoot.
Additionally, the associated os x files at http://louhi.kempele.fi/~skyost....ort.zip
return a page that says
"Warning: Panda GateDefender Performa has detected unauthorized content in the following file: fretsonfire-macsupport.zip
The download from http://louhi.kempele.fi/~skyost....ort.zip has been blocked"
So I'm unable to test things on my computer/offer any input at all here. Something strange is afoot.
Yep thats the error, no its an Ibook G4.....
Looks like we all have another problem (I wish they wouldnt release this without at least testing on a few machines or use us as testers before releasing).
Looks like we all have another problem (I wish they wouldnt release this without at least testing on a few machines or use us as testers before releasing).
Last edited by lardbloke on Sun Nov 26, 2006 9:38 am, edited 1 time in total.
If you want more betatesters (and possibly even coding help) you could ask around at some Mac forums, for example the Finnish Omenamehu.
This is the error I'm getting:
Frets on Fire Error
An unexpected error has occurred during execution of the main script
ImportError: Failure linking new module: /Users/SiC/Desktop/Frets on Fire.app/Contents/Resources/lib/python2.4/lib-dynload/datetime.so: bad local relocation length...
I have a new MBP c2d 17inch so :S why doesn't it work?
thanks
Frets on Fire Error
An unexpected error has occurred during execution of the main script
ImportError: Failure linking new module: /Users/SiC/Desktop/Frets on Fire.app/Contents/Resources/lib/python2.4/lib-dynload/datetime.so: bad local relocation length...
I have a new MBP c2d 17inch so :S why doesn't it work?
thanks
I was having the same problem as SiCbe on my Intel iMac running 10.4.8. I was able to get it running buy doing a couple of things.
First I replaced Frets on Fire.app/Contents/Resources/lib/python2.4/lib-dynload/datetime.so with datetime.so from the previous version.
Then I was getting just a black screen with an error in console.log
OSError: [Errno 2] No such file or directory: 'data/mods'
So I created an empty folder named mods in the data folder like...
Frets on Fire.app/Contents/Resources/data/mods
After that it started up and played. I still could not get all the GH2 songs working. I get the 'index out of range' errors when I select a song with no difficulties listed. I'm guessing this is probably from moving the old datetime.so.
First I replaced Frets on Fire.app/Contents/Resources/lib/python2.4/lib-dynload/datetime.so with datetime.so from the previous version.
Then I was getting just a black screen with an error in console.log
OSError: [Errno 2] No such file or directory: 'data/mods'
So I created an empty folder named mods in the data folder like...
Frets on Fire.app/Contents/Resources/data/mods
After that it started up and played. I still could not get all the GH2 songs working. I get the 'index out of range' errors when I select a song with no difficulties listed. I'm guessing this is probably from moving the old datetime.so.
Last edited by killgoro on Mon Nov 27, 2006 2:56 pm, edited 1 time in total.
Hi All,
The trouble you're seeing _now_ was caused by a corrupted USB memstick. (Murphy's law seems to apply here). If you feel like it, you can try replacing all the lib files (.so's & .dylib's) from the old package with the new one (don't replace the .pyc's). Or just wait until an "official patched release"
As for positive news... Well... At least on the Intel Macs you now will get a fully working version. (Tested on my MacBook).
-- Tero
The trouble you're seeing _now_ was caused by a corrupted USB memstick. (Murphy's law seems to apply here). If you feel like it, you can try replacing all the lib files (.so's & .dylib's) from the old package with the new one (don't replace the .pyc's). Or just wait until an "official patched release"

As for positive news... Well... At least on the Intel Macs you now will get a fully working version. (Tested on my MacBook).
-- Tero
Who is online
Users browsing this forum: No registered users and 9 guests