Searching for errors in .log file
If FoF shows a message box with 'Errors occured' in the title after quitting, it means it wrote something to its log file. It is located in the main FoF directory and is named in the same manner the .exe file is, it just has additional the .log extension.
After opening it, you should be able to see one or more pieces of text like that:
Traceback (most recent call last):
File "GameEngine.pyo", line 353, in run
File "GameEngine.pyo", line 345, in main
File "View.pyo", line 208, in render
File "D:\FretsOnFire-1.1.324-win32\FretsOnFire\data\library.zip\GameResultsScene.py", line 305, in render
AttributeError: GameResultsSceneClient instance has no attribute 'uploadingScores2'
The first line is unneccessary for us.
The lines second to the last before one tell us the trace the error had to tent through.
The last line tells us the type of error that occured. This (or similar one) is the value you should be searching for.
List of solved error messages found in .log file
- AttributeError: GameEngine instance has no attribute 'cmdPlay'
- AttributeError: GOpenGLBoard instance has no attribute 'RenderingQuality'
- ConfigParser.MissingSectionHeaderError: File contains no section headers.
- GLerror: (Errno 1284) stack underflow
- IndexError: list index out of range
- IOError: (Errno 13) Permission denied
- KeyError: 0 (can be any number)
- pygame.error: No video mode large enough for 1280x960 (or any other resolution)
- pygame.error: Sound buffer size must be between 2 and 134217727
- UnicodeDecodeError: 'ascii' codec can't decode byte 0xXX in position X: ordinal not in range(128)
- ValueError: invalid literal for int():
- WindowsError: (Errno 3) The system cannot find the path specified: 'data\\mods/*.*'
NOTE: The above error messages are only ones that have known solutions. There are many many more errors out there that have been reported, but have not yet been solved. If you want to report an error, or know a solution to an error not on the above list, please do so at this thread. Please read the guidlines on the first post before making an error report.
Socket errors
All of the socket errors (who can be distinguished by their build - error: (number, message))signify that Frets on Fire is unable to connect to its server part on your computer. They always mean you should disable your firewall or let Frets on Fire pass through it. Typical socket errors include:
- error: (10049, "Can't assign requested address")
- error: (10013, 'WSAEACCES')
- error: ((10061, 'WSAECONNREFUSED')
- error: (10022, 'Invalid argument')
- error: (6, 'ENXIO')
You can check to see if you have a firewall active in Start > Control Panel > Security Center. Even after you have turned off your firewall, there may still be one secretly active. To make sure it's off, try looking in your Networks Connections, right-click Local Area Connection (or something similar), choose Properties, and then check out the Advanced tab.
If you want to go a step further, stop and/or disable your Windows Firewall / Internet Connection Sharing (ICS) service. Get there by going Control Panel > Administrative Tools > Services. Of course, this process may differ if you are running an OS that isn't Windows XP.
