Have flown a bit tonight on new PC, connecting through 3G. Pings are a bit high (around 150 or so), but not too bad considering (and totally awful compared to 100 Mbit cable!).
Anyway, I had problems joining games, some did work properly, but on many DF servers I first got a message that connection was successful, just to be followed by a error message when I clicked ok, I think it said something about “Timeout 1” and I was back at desk.
Any idea what the reason might be?
Windows 7 64-bit, plain 4.09, no mods (copied from old PC, so it shouldn’t be any difference other then changing some graphics settings).
Just to make it totally clear, some servers worked just fine, like Starfires on the second and third go (different missions).
We ran the same mission with the packs reverted to 4.09m stock.
In the ini. :“checkRuntime=” where
Ultra: checkRuntime=1
HSFX: checkRuntime= 0
That might have been it
The one where Mikke got the error had checkRuntime=1
The server can now check for changes on the client-side game modules, i.e. ensure the modules were not modified. To enable the check, a new key was added to the conf.ini file.
In order to set the client-side verification parameters you will need to manually edit the conf.ini file located in your main game folder before launching the game. Open the file with a text editor, find the [NET] section and in the checkRuntime = line write in either 0 or 1 (or 2), then save the file. If the checkRuntime = line does not exist in your conf.ini file, add it to the end of the [NET] section.
checkRuntime=0-no check is made (default);
checkRuntime=1-quick check;
checkRuntime=2-comprehensive check.
NOTE: during the comprehensive check, if the client runs a different OS version from the client, the check may identify the OS differences as changes in game modules.
Can I draw on you assistance a bit more. I need a bit more help since this is new to me.
I am can only find: eventlog.lst i both root directories.
So I guess I need to enable something in my conf.ini in both installations.
After reading the post on mission4today I have changed both ini-files to look like this:
[Console]
HISTORY=1024
HISTORYCMD=1024
LOAD=console.cmd
SAVE=console.cmd
LOG=1 ( <- I changed this from ‘0’ to ‘1’)
LOGTIME=0
LOGFILE=log.lst
LOGKEEP=0
Anything else I need to do before haressing my CO (Mikke) again
i’m trying to be available as i can and happy to be useful if i succeed
your settings are now ok,
you’d find a file named log.lst being written while the sim runs
in case of crash or whatelse issue start crawling from there
the logkeep switch allows to collect your log.lst history of several runs in a separate file (.old extension one )
TIP: while Flying or using FMB the console is available in the sim GUI too by pressing CTRL+TAB
as said if you need for more just ask, i’ll do my best for share what i know
always hoping to be helpful,