#3023210 - 06/02/10 01:47 AM
Re: EECH multiplayer
[Re: Colonel_Kurtz]
|
Joined: Sep 2005
Posts: 172
AMRAAM
Member
|
Member
Joined: Sep 2005
Posts: 172
Auckland, New Zealand
|
Colonel,
Did you ever run a test with a previous version of EECH to confirm/deny that the non reporting issue was caused by the latest version of EECH? 1.13?
Just curious to know, if not, I can roll back my EECH to a previous version and see if it is working or not.
My server has been up and running all this time, but without the IP published it never gets any attention. If we can work out where the break in the reporting is, that might help some.
"Don't worry soldier, they can stitch those back on"
[Ord.] General AMRAAM, Commander in Chief
|
|
#3023344 - 06/02/10 10:31 AM
Re: EECH multiplayer
[Re: AMRAAM]
|
Joined: Jan 2007
Posts: 1,142
Colonel_Kurtz
Member
|
Member
Joined: Jan 2007
Posts: 1,142
Australia
|
Hi AMRAAM
Im pretty sure now that the problem is at HOXDNA. I tried loading an EE2 server which did not report in either. I also had a multiplay session last weekend with Chaddog which went ok except for a couple of server crashes. One(Kenia) which I attributed to me neglecting to turn of my server PC's screen saver and antivirus, but Im unsure that was the real reason as a second crash followed not long after loading Skagway onto the server, which in the past, like Sword in the Sand has been rock solid for multiplay up to 4 players. Kenia has crashed in the past after around 2hrs of multiplay, so its not an ideal debugging map I guess.
In conclusion EECH v1.13.0 is quite functional, but the master appears to be bugged ATM. Whether EECH v1.13.0 is stable for multiplay is another question. This could be WUT related, or it could relate to people choosing the AH1-Z Viper(not confirmed of course) The reason ive tagged this is not because of Dfangs model, its because all non standard flyables have a bug which is still present relating to client input into the "right side" MFD of non standard flyables which causes a client end crash. whether it can cause a server end crash I dont know, I just have not ruled it out. In the past if I was flying, Blackhawks, Chinooks, etc I would avoid at all costs inputing/changing the right side MFD to avoid client end crash.
The EECH v1.13.0 update over wrote quite a few files that could be considered for debugging as follows-
1. cohokum.exe 2. Forms 3. Formscomp 4. WUT
Custom texture/audio mods such as Skins, Cockpits, Terrain, GUI, Sounds were lost if you cant find them in an older ver backup.
Theres also no referance to maps 14,16,19,20,31,35 in the "maplist.txt" either. This has always been the case, and I forget now what this file was used for.
My old install was completly cleaned of every broken file name entry eg: "Red sea" = Red_Sea etc. A few years back I went though every file name and every command line within the CHC files every campaign. The camo files, basically a whole bunch of modded files. Doing this I believe created a very stable server base and crashes were rare for me in multiplay in the past.
I havnt really flown this build enough yet to reliably comment about debugging multiplay apart from the info Ive noted above that I found out during the process of restoring my installation.
The Pro's of this build-
* Dfangs excellant new AH1-Z Viper --Thx to Dfang * All of the campaigns are now availlable(appart from Norway which still crashes for me) * Cockpit sound issue has been corrected --Thx to Firebird
Its a shame Spypat doesnt fly EECH, so we could use "Modman" to restore all our custom stuff following updates.
Last edited by Colonel_Kurtz; 06/02/10 10:32 AM.
|
|
#3023368 - 06/02/10 12:19 PM
Re: EECH multiplayer
[Re: AMRAAM]
|
Joined: Feb 2007
Posts: 84
Re-Ordained
Junior Member
|
Junior Member
Joined: Feb 2007
Posts: 84
Detroit, MI, USA
|
Colonel,
Did you ever run a test with a previous version of EECH to confirm/deny that the non reporting issue was caused by the latest version of EECH? 1.13?
Just curious to know, if not, I can roll back my EECH to a previous version and see if it is working or not.
My server has been up and running all this time, but without the IP published it never gets any attention. If we can work out where the break in the reporting is, that might help some. I tested the previous version (1.12.3) about a week ago. It failed to show up on HOXDNA with settings that have worked in the past.
|
|
#3029659 - 06/12/10 03:42 AM
Re: EECH multiplayer
[Re: CHADDOGG]
|
Joined: Sep 2005
Posts: 172
AMRAAM
Member
|
Member
Joined: Sep 2005
Posts: 172
Auckland, New Zealand
|
Damn it... well I will restore it to 1.13 and see if it stays reporting in. Watch this space.
"Don't worry soldier, they can stitch those back on"
[Ord.] General AMRAAM, Commander in Chief
|
|
#3029750 - 06/12/10 10:28 AM
Re: EECH multiplayer
[Re: AMRAAM]
|
Joined: Jan 2007
Posts: 1,142
Colonel_Kurtz
Member
|
Member
Joined: Jan 2007
Posts: 1,142
Australia
|
Damn it... well I will restore it to 1.13 and see if it stays reporting in. Watch this space. I dont think the reporting to HOXDNA was a problem with the 1.13 release as my EE2 server never reported at HOXDNA either. Perhaps its been fixed, as I have not flown over the last week as ive been engrossed in a new RC Heli ive purchased.
|
|
#3030843 - 06/14/10 08:19 AM
Re: EECH multiplayer
[Re: CHADDOGG]
|
Joined: Sep 2005
Posts: 172
AMRAAM
Member
|
Member
Joined: Sep 2005
Posts: 172
Auckland, New Zealand
|
Yep. And someone (the local IT Administrator -me) forgot to change the WUT file in the ini file as well. Hopefully it is all up and running now. We shall see.
"Don't worry soldier, they can stitch those back on"
[Ord.] General AMRAAM, Commander in Chief
|
|
#3030849 - 06/14/10 08:49 AM
Re: EECH multiplayer
[Re: Colonel_Kurtz]
|
Joined: Sep 2005
Posts: 172
AMRAAM
Member
|
Member
Joined: Sep 2005
Posts: 172
Auckland, New Zealand
|
Cheers, I just checked and it was like that already.
"Don't worry soldier, they can stitch those back on"
[Ord.] General AMRAAM, Commander in Chief
|
|
#3031239 - 06/14/10 07:49 PM
Re: EECH multiplayer
[Re: Colonel_Kurtz]
|
Joined: Sep 2005
Posts: 172
AMRAAM
Member
|
Member
Joined: Sep 2005
Posts: 172
Auckland, New Zealand
|
Excellent!
Now I can move that install to my Gaming rig and see about getting back into the air myself. (and rediscovering how to fly no doubt :))
Interesting side note: To upgrade the server, I simply installed the 1.13 allmods over my current install of 1.12.3. I then deleted game.cfg and eech.ini, as well as all WUT files in the cohokum directory (other than the 1130 one). Started the game. Turned on internet play and then exit the game. Customized the eech.ini file to have the correct settings (including having to manually set the WUT to the 1130 version) and then ran the server up in dedicated mode. The server seems to be running fine. So possibly you don't have to do the full install dance when upgrading to 1.13.
A couple of caveats on this though: 1) It may be because the server runs in dedicated server mode, with no graphics options turned on) 2) It may be because the server is not super new hardware.
"Don't worry soldier, they can stitch those back on"
[Ord.] General AMRAAM, Commander in Chief
|
|
#3032812 - 06/16/10 05:06 PM
Re: EECH multiplayer
[Re: CHADDOGG]
|
Joined: Jan 2003
Posts: 7,276
UnderTheRadar
Hotshot
|
Hotshot
Joined: Jan 2003
Posts: 7,276
Austin, TX
|
I was trying to teach a friend the other day and didnt want to have to worry about getting shot at while i was instructing lol. Let me know if you are giving anymore classes
I have gaming PCs that run everything from MS-DOS 6.22 to Windows 7 64-bit
Win7 Home Prem 64 i5-3570 ASRock HM77 XFX Radeon HD 6950 2 Gig 8 Gigs GSkill DDR3 1600 500 Gig Samsung 840 SSD 1 TB WD Black SATA II HD Plextor 24x DVD-RW ViewSonic VA2702w 1920x1080 HP L2206tm 1920x1080 Multi-Touch Screen Antec Neo 550w PS Antec Full Tower Case Warthog 1663 w/ CH Pro Pedals TIR4 w/ Clip Logitech G110 KB Razer Naga
|
|
|
|