20.05.2009, 13:22
Toto_Yoyo -
That error is usually caused by missing objects in the client (Your install).
The easiest way to debug this is to turn on logging for the console in the conf.ini file(Looks like you allready have it by your errors. Here's my section of the conf.ini file that logs console stuff to the file log.lst
Then when you connect to the server and you get the java.lang.intiger error, exit out of IL2 and open the log.lst file in a file editor.(Notepad, wordpad, etc)
The errors you described about the engine sounds are there even with a good install of UI 1.1.1. You need to look at the errors after the mission starts loading ( something like "Loading mission FBDj/Torch409.mis...")
There were quite a few people who had this problem and it turned out to be missing static A/C. After downloading the Static A/C fix from here (AAA forum) it worked.
WildWillie
That error is usually caused by missing objects in the client (Your install).
The easiest way to debug this is to turn on logging for the console in the conf.ini file(Looks like you allready have it by your errors. Here's my section of the conf.ini file that logs console stuff to the file log.lst
Code:
[Console]
HISTORY=1024
HISTORYCMD=1024
LOAD=console.cmd
SAVE=console.cmd
LOG=1
LOGTIME=0
LOGFILE=log.lst
LOGKEEP=0Then when you connect to the server and you get the java.lang.intiger error, exit out of IL2 and open the log.lst file in a file editor.(Notepad, wordpad, etc)
The errors you described about the engine sounds are there even with a good install of UI 1.1.1. You need to look at the errors after the mission starts loading ( something like "Loading mission FBDj/Torch409.mis...")
There were quite a few people who had this problem and it turned out to be missing static A/C. After downloading the Static A/C fix from here (AAA forum) it worked.
WildWillie