"See the logfile at '\FAForever.exe.log' for details."
- Code: Select all
(120 lines, all differing "FunctionNotFound" error messages, all FreeImage_XX as below)
E:\App Files\Forged Alliance Forever\FAForever.lib\FreeImagePy\library.py:90: FunctionNotFound: Error on bind FreeImage_IsLittleEndian.
Error in sys.excepthook:
Traceback (most recent call last):
File "main.pyc", line 56, in excepthook
NameError: global name 'logger' is not defined
Original exception was:
Traceback (most recent call last):
File "main.py", line 44, in <module>
File "util\__init__.pyc", line 595, in <module>
File "util\crash.pyc", line 24, in <module>
File "fa\__init__.pyc", line 82, in <module>
File "fa\maps.pyc", line 39, in <module>
File "FreeImagePy\__init__.pyc", line 35, in <module>
File "FreeImagePy\FreeImagePy.pyc", line 84, in __init__
File "FreeImagePy\library.pyc", line 93, in __init__
AttributeError: 'internlLibrary' object has no attribute 'lib'
The FAForever.lb file exists in the location mentioned in the log. The client is freshly re-installed using FAForeverLobby-0.8.54.exe on Windows 8 64-bit. I had reinstalled in a new location after the client refused to open, with a different dialog box about its inability to write to log for I assume the same reasons. Repairing the installation didn't do anything.
I haven't installed any major updates to my system since the last time I was able to run the client, maybe 4 days ago.
Does anyone have experience with fixing this type of python library issue? I've seen in a similar problem pop up in the forums already, and I've seen mentions that FreeImagePy, or at least FAF's use of it, has problems using the new version of FreeImage (3.15.4). I've tried the earliest version of FreeImage.dll I could find, which was 3.13.0 but the same problem happened, with a similar log.
Another search I tried led to be some forum, when someone had a similar issue in FAF, that mentioned that FreeImagePy uses freeimage.dll v3.9.x but I could not find anything earlier than 3.13.0.
