ENO'S FIREHOUSE: 1.2.7 U2 STRESS TEST JAN25

[ENO]

PLEASE NOTE, THIS WILL NOW BE A 1.2.7 RELEASE EVENT!

 

 

http://www.zulutime.net/

 

TS3 info

104th Phoenix

Addy - 50.197.62.13

Pass = phoenix

 

Firehouse regulars and simhq pilots may be on SimHQs TS3 as well (free reg required)

 

1600UTC

 

I expect the server will run with doors open throughout the day so don't worry about being there "right on time."

Edited January 24, 2014 by ENO

[Pipe]

ill be there

[Winfield_Gold]

I would come along but that's 2:30am AEST. The 2000UTC suits me better ENO

[ENO]

Okay! Well now 127 is released... I guess that changes things a bit- or is it worth hosting a 1.2.7 final release stress test?

 

Thoughts?

[SkateZilla]

A 1.2.7 Release Stress Test!

[Raven68]

ENO how have the beta's been performing? Have you noticed improvements with the latest beta update?

[SkateZilla]

MP in 1.2.7 beta was a lot more stable.

[Raven68]

MP in 1.2.7 beta was a lot more stable.

Thanks Skates thats good to know. I am hoping to see the day that we have servers hosting 64+ without too much of a hitch. I know ED is still reworking the base code and it will take time. :thumbup:

[ENO]

Raven- it really was quite good. Keep in mind my template smashed just about every aspect of DCS into one "mission" with a good mix of AI activity and client based action.

 

We had some hiccups- but that's why we were testing.

 

It was very stable- but most significant I think was the 1024 connection speed repair- it significantly reduced bandwidth usage on the server and made for a really smooth experience. Only exception to that was if I was on an actual LAN connection with the server using 1024... at that point I was warping horribly-

 

 

Just to confirm- Servers should stay on LAN (from what we found) and clients should connect at 1024 unless they experience warping (which didn't ever occur to my knowledge except when someone with half a second ping came in)...

 

So... 127 release stress test? I'm in! How do I change the title that displays in the forum?

Edited January 24, 2014 by ENO

[SkateZilla]

or change it to 1.2.7. Fly-In Release Party.

[Raven68]

Just to confirm- Servers should stay on LAN (from what we found) and clients should connect at 1024 unless they experience warping (which didn't ever occur to my knowledge except when someone with half a second ping came in)...

 

Thanks ENO. I will note that and change my settings. I am in for the stress test buddy.

[SkateZilla]

just make sure you sert ADSL1024 and not ADSL10240

[Raven68]

just make sure you sert ADSL1024 and not ADSL10240

 

:thumbup:

[ENO]

I would come along but that's 2:30am AEST. The 2000UTC suits me better ENO

 

I'm sure we'll still be up and running around that time Winfield. I'll try to have it up for the entire day... we'll start with the template and then work into larger scale missions and see where we end up!

[Ninja1959]

rgr thanks......

[ENO]

Problem signature:

Problem Event Name: BEX64

Application Name: dcs.exe

Application Version: 1.2.7.23097

Application Timestamp: 52dfa4c6

Fault Module Name: StackHash_1dc2

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 0000000000000000

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 4105

Additional Information 1: 1dc2

Additional Information 2: 1dc22fb1de37d348f27e54dbb5278e7d

Additional Information 3: eae3

Additional Information 4: eae36a4b5ffb27c9d33117f4125a75c2

 

 

 

We're back up now for those of you who want to step in.

[ENO]

Maybe it's just this mission- but I've run this mission reliably for weeks with the Beta and now it is completely messed up. The sync drops out almost immediately between the server and clients which undoubtedly causes crashes.

 

Some vessels are moving, some aren't... bombers just disregard waypoints... then suddenly appear over the target area dropping bombs... (client side) meanwhile all is normal on the server side.

 

Anyone else experiencing this?

[ENO]

We just wrapped up the session and to say I'm disappointed would be saying very little- but it was my own fault and I broke many of my own rules.

 

Biggest one so far is the fact that in the past when we've updated full version numbers (125, 126 etc) I've done a clean install. I didn't do that this time and I am convinced it has lead to issues. I confirmed the likelihood through some of the members online today. They were having similar issues, while our beta experience was remarkably clean and fantastic. Coincidence that the Beta was a clean install while the 126-127 transition was not?

 

I think not.

 

Anyway, I leave this today wanting to suggest to those of you who cut the corner and installed through the update path... if you're having any issues at all with missions or sync separations, or other glitches (missiles going through targets... ground vehicles taking flight with dust trails in tow) then think hard about uninstalling and getting a fresh copy.