Arrgghhh... Looks like Cargo Cult...

Is anybody having a problem with MP?

Since a friend and I updated to this version when trying to join The "Connecting (xxx)" number just keep rising (I waited until 10,000). Rolled back to 1.11 and connected at around 400.

I have no problem with connection (at least to AMRAAMs Server). Maybe you should back up your eech.ini and remove it from the game folder. The game will create then a new one with default values. Try to connect with that 'stock' .ini and if you succeed, then it would mean, that you simply have to set something up in that previous version of the ini file. Good luck!

Yay!! I can select resolutions higher than 1280 by 720 now!!! And no more corruption and tearing of the sky, ( which was fixed in the "test" executable I was last using) everything works great so far!!! Thanks a lot !!!

Thanks RoGal will give it a go

Links to the Executable only is broken

Hey, Firebird and Kurtz,

I have just updated to 1.12.2 (I skipped 1.12.1 as I was away) and my dedicated server "runs" but has issues. The issue is that it only opens the same campaign. I came to this post to try testing with 1.12.1 to see where the issue was introduced, but see from Kurtz's comments that he too was having issues.

I'm downloading 1.12.1 to testing at the moment, (I have downloaded 1.12.1 and get the same results as 1.12.2) but thought I would note down what is happening for me as well, perhaps to give you some idea of what the issue is?

With 1.12.0: The Dedicated server batch file runs fine.

With 1.12.1: I'll do some testing and update this post when I have. I have tested 1.12.1 and it has the same issues as 1.12.2. So the issues seem to have arisen in relation to changes that happened as part of 1.12.1 upgrade

With 1.12.2: It seems to be that the batch file runs, (it starts EECH) but it ignores the command line parameters that follow the "cohokum" command.

[This is an example of a line in the dedicate.bat that launches the game]
cohokum /pitod:0900 dedicated:1 game_type:2 gunship_type:2 path:..\common\maps\map1 directory:camp01 filename:thailand.chc

(and just in case you were wondering where the dedicate.bat file came from, it is part of the EECH install, its not something that Kurtz and I made up. :))


So when the batch file launches the game it does not go into dedicated server mode, it just starts in "normal" mode. I can force the game to start in dedicated server mode by editing the eech.ini file and setting the variables for dedicated server mode.

[This is extracted from EECH.ini]
[Dedicated server]
# for more information see http://www.eechcentral.com/wiki/index.php?title=Dedicated_server
dedicated=1 # dedicated server mode (0 = off, 1 = on) (def = 0)
pauseserv=1 # pause server if no clients connected (0 = off, 1 = on) (def = 0)
game_type=2 # available game types (1 = Freeflight, 2 = Campaign, 3 = Skirmish) (def = 0)
gunship_type=8 # available gunship types [NOTE!] dummy value (0 = Apache, 1 = Havoc, 2 = Comanche, 3 = Hokum) (def = 8)
path= # path to map/campaign/skirmish folder

This loads the game in dedicated server mode, but then (I presume because it ignores the command line parameters) it always loads the same map, which is the Standard (Sword in the Sand) campaign Yemen map (..common\maps\map6)
If I hard code the map folder location in the eech.ini file (under the path= varible) then the server does not load. It crashes with the following error: Error opening file for reading:

C:\razorworks\cohokum\common\..\common\maps\map3\camp01\yemen.chc.

This map folder number is whatever number I have hard coded in, and if I hard code the map into 1.12.0 then it works fine. So I suspect that the game has been hard coded to always try and open the yemen.chc map?

I have not tested connecting to the server in version 1.12.2. I will do that right after this post, and edit this post to contain my results. I know I should have tested that first, but I forgot, and well I don't want to have to type this all again. I have tested connections internally and they are working, so people should in theory be able to connect to the server from the outside world as nothing has changed in that respect. So it's just the issue that the commands after the cohokum in the batch file are no longer being read which is preventing the Dedicated server from starting (As far as I can work out at least).

And Finally, Sorry for bumping an old post. This message ended up longer than I thought it was going to be originally.

Ive been flying mostly DCS of late, so havnt looked at the dedi launch prob too much although I knew it was there. Personally I think its caused by the "random themes" but I could be wrong. Ive been waiting for the sound bug to be fixed.

I still like EECH, but I also like the flight dynamics of DCS. I also like a PC puzzle so I'll see what happens when I load my EECH dedi up and report back here

One question though-

1. Can the random themes be disabled by setting "themes=0" ? I think not, but please confirm.

OK just tested some stuff.

AMRAAM if you just set the eech.ini param "dedicated=1" the command lines work again. So im guessing the server bat file entry "dedicated:1" is no longer functional but the eech.ini entry is OK. You never needed to do this before, but no big deal

Another oddity is that the only way to kill my server is via my eech killer bat file "Taskkill /f /im cohokum.exe"

ps- I also deleted my server eech.ini and game.cfg and let them regenerate.

**edit** before setting dedi=1 start game and configure, including multiplay etc

OK here goes-

Dedi server update to current build notes-

1. update server to latest exe

2. Delete eech.ini and game.cfg

3. Run game in normal mode to regenerate files

4. configure game options including multiplay

5. edit eech.ini including dedicated option

6. run bat file to launch

Notes for clients-

1. Open direct7 ports and set software forwall permissions when asked

2. Locate server IP via http://hoxdna.org/eech/

3. Enter server IP via multiplay options then press "enter" before pressing "OK"

4. Go to Campain screen and select multiplay

5. You should see server in green text

6. When entering new server IP, first clear old IP, then press "enter" then click OK, then re-enter multiplay and enter new IP, then press enter. You need to do this to clear the old IP properly

enjoy

ps- Ive just tested your IP and I cant connect to your server either AMRAAM. Something is wrong there.