|
|
#3020842 - 05/28/10 04:51 PM
Re: EECH multiplayer
[Re: CHADDOGG]
|
Member
Registered: 01/29/07
Posts: 1142
Loc: Australia
|
Campaign Comander, GWUT, Formscomp etc are all determined by the host servers config as far as I know. Client side config doesnt matter except "downwash" should be set to off for multiplay.
|
|
Top
|
|
|
|
#3020878 - 05/28/10 06:02 PM
Re: EECH multiplayer
[Re: Colonel_Kurtz]
|
Member
Registered: 01/29/07
Posts: 1142
Loc: Australia
|
Multiplay Server live at IP- 115.70.99.206 Kenia Peninsular War
|
|
Top
|
|
|
|
#3023210 - 06/01/10 06:47 PM
Re: EECH multiplayer
[Re: Colonel_Kurtz]
|
Member
Registered: 09/21/05
Posts: 172
Loc: 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
|
|
Top
|
|
|
|
#3023344 - 06/02/10 03:31 AM
Re: EECH multiplayer
[Re: AMRAAM]
|
Member
Registered: 01/29/07
Posts: 1142
Loc: 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.
Edited by Colonel_Kurtz (06/02/10 03:32 AM)
|
|
Top
|
|
|
|
#3023368 - 06/02/10 05:19 AM
Re: EECH multiplayer
[Re: AMRAAM]
|
Junior Member
Registered: 02/23/07
Posts: 84
Loc: 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.
|
|
Top
|
|
|
|
#3023693 - 06/02/10 01:09 PM
Re: EECH multiplayer
[Re: Re-Ordained]
|
Member
Registered: 12/03/09
Posts: 264
Loc: Chimacum, Wa
|
Im very happy that yall are working on this, EECH multiplay is a blast, it would be great to schedule a time that a few of us can get together and fly. I wish i had the skills yall do as i would be more then happy to donate my extra time to helping any way that i could. AMRAAM, please pm me with the server IP or contact me on SimHQ teamspeak, thanks bud!
|
|
Top
|
|
|
|
#3029639 - 06/11/10 08:02 PM
Re: EECH multiplayer
[Re: CHADDOGG]
|
Member
Registered: 12/03/09
Posts: 264
Loc: Chimacum, Wa
|
AMRAAM's server is reporting to http://hoxdna.org/eech/ but i cant join as he is running 1.12.3 and im running 1.13 
|
|
Top
|
|
|
|
#3029659 - 06/11/10 08:42 PM
Re: EECH multiplayer
[Re: CHADDOGG]
|
Member
Registered: 09/21/05
Posts: 172
Loc: 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
|
|
Top
|
|
|
|
#3029750 - 06/12/10 03:28 AM
Re: EECH multiplayer
[Re: AMRAAM]
|
Member
Registered: 01/29/07
Posts: 1142
Loc: 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.
|
|
Top
|
|
|
|
|
|
|
| |