1.2.2 MP issues with logs

[JorgeIII]

MP issues with 1.2.2 version on our squadron, tested the last weekend:

1)

All clients CTD, server stays online:

happens always after 10-30 minutes with missions edited or created with 1.2.2 version. With or without FC3 or CA slots. It happened many times to all the squadron in our 2 dedicated servers (different hardware, bandwidth and location) and in the 104th server. It did not happen with old 1.2.1 missions, but we had issues # 2 & 3. All clients have a CTD at the same time every 10 to 30'.

We had Servman installed in the 2 servers, 1.2.2 overwrote some or all of its files. It was not reinstalled to prevent compatibily issues. May be is somehow related?

Known issues:

2)

Connection interrupted, server timed out issue.

Still present. Kicks one client at a time. Seems to be related with the amount of moving ground units (about > than 5-10) and amount of clients (more frequent with more than 4-6 clients connected). Latest 1.2.1 was more stable than prior versions. Hard to tell the difference with 1.2.2 because of so many # 1 (client CTD)

3)

Server not in the list:

Frequently one or two of the clients can’t see one of the 2 servers in the list nor connect using IP. Sometimes the server appears after refreshing, sometimes they can be refreshing for 30’ without seeing the server. It happends to one or two clients, the rest can connect OK.

We also had 2 or 3 CTD on server #1, which is rare.

 

Logs:

 

Server #1: (i5 2500k, 8 GB DDR3, SSD Vertex 3, Ati HD 6850, Windows 7 x64)

server logs.rar

 

Client #1: (specs in the signature)

client 1 log.rar

 

 

Most flights where done on server #2, let me know if you need the logs and I’ll ask for them.

 

Hope this helps. We flew many hours this weekend but could't finish any mission.

Edited November 12, 2012 by JorgeIII

[Dejjvid]

Ever since we installed 1.2.2 we've had these issues. As you wrote it's two to three different scenarios.

 

1. Everyone crash, including the server.

2. Everyone except the host crash, server is rejoinable

3. A single client crash, other clients and server can continue.

 

10-30min until it happens.

 

 

We've played alot with 5-15 players. We noticed this issue immediatly after we patched to 1.2.2 . hard to say if it's related to FC3 or if it crash with A-10C and BS.

 

Edit: And we only use vanilla software, no mods what so ever.

[LostOblivion]

Ever since before DCSW, I have noticed that there is a large difference in client lag and stutters (not network lag), whereas in the exact same mission as singleplayer it would be very smooth.

 

For some reason, when in a multiplayer environment, there is what seems to be client lag induced by it being a network game. I have no experience with this in other games, and I feel that it is strange that there are stutters in multiplayer where there should only be warping/other network related issues.

 

Lost

[ENO]

We're having all the same problem but there doesn't seem to be any connection to clients or ground units. Some missions have tons, some have even more... Some have a few less and they all take turns crashing or booting.

[BRooDJeRo]

The main.lua provided with the old servman download has old DCS netcode functions.

 

Only the last function in the main.lua file and a few extra rows are for initiating Servman.

 

You need to copy and paste this function on the bottom of the file to the bottom of the latest original main.lua file that come with the latest DCS build.

 

I use this one now. Its the only file in DCS modified to make Servman work.

Ofcourse you also need to manualy create the folder 'missions/multiplayer' in the main DCS gamefolder where the missions for the autorotation go in.

Im clueless on the compatibility of the older part of code. Im a total noob at coding, but i do know how to make things work. Its possible professionals will scratch their heads and even wonder why a piece of old code still functions. Its also possible that this is the path to follow. But who cares!!! It works....

 

Im using the personaly modified version in the rarfile below to manage my server and hasnt given me any trouble sofar.

Maybe you did something similar yourself already, but this might work for you when you didnt copy n paste stuff from old file to new ones.

 

Compare both original and modded file so see what is actualy changed at the bottom, you'll laugh on how little it actualy is. Dont use old netcode files in newer installations. This file has been changed between DCS 1.2.1 and 1.2.2 and i think it has partialy to do with a fix to keep clients connected to the masterserver or reconnect when disconnected.

 

I hope it works the same for u as it does for me. When DCS is updated or repared, all modded files go into the backup folder and DCS is fully in its original state. When you have trouble in original state then it doesnt have anything to do with Servman.

 

My server and client seem to run stable for me as well as many other people visiting. Even with high ping (200-250). Sometimes i see weird people logging in and out a couple of times that give me odd feelings. Theres even rumor/gossip of breaking and modding something on the enemy side with a certain multiclient login/logout method. theres enough people running around on this planet that take pleasure out of making someone elses life miserable. This is most likely a reason why many servers are locked.

 

EDIT: Old upload deleted, new can be found here: http://forums.eagle.ru/attachment.php?attachmentid=77165&d=1360902874

Edited February 15, 2013 by BRooDJeRo

[statrekmike]

We have had two updates since 1.2.2 and still it crashes in MP.

 

I don't usually succumb to impatience, I try to be very understanding but after a week of not being able to use DCS products online (the only way I really use them) due to random crashes 100% of the time I attempt to play online, well, I am getting a bit concerned.

 

I know it takes a long time to track down this stuff and fix it but you have many folks on this forum who can't get through a single online mission without a CTD, we have given you all the info we can (and dealt with some rather harsh treatment from ED team members) and now I feel that perhaps even just a quick update on the situation would go a long way.

 

Don't take this the wrong way, I am not whining, I am not demanding anything, I just want to know that the products I own (and have had little trouble with before the recent update) will be usable soon and I can get back to having fun running missions with my buddies.

 

I know you are working hard and I don't mean to pressure you, I just would like to have a rough estimate on the fix or something like that.

 

Thanks for your time ED, I know you won't let us down and I expect to be a customer of you folks for a long time to come.

[Maxpilot]

Thats why I leave long time ago. Sorry, I'm not as forgiving as my previous speaker. Showstoppers after how many years of development? And worse: New introduced showstoppers, and not for the first time. I know this will be deleted, but s.o. will read this and hopefully pass it on: This is simply bad quality management.

[sobek]

I know you are working hard and I don't mean to pressure you, I just would like to have a rough estimate on the fix or something like that.

 

Unfortunately something like that is not possible.

[159th_Viper]

Thats why I leave long time ago....

 

And yet here you are.

 

Rest assured that all are working 8-5, Mon to Fri, to get the issues resolved. Nothing more to be done, apart from exercising patience that is.

[sobek]

This is simply bad quality management.

 

No, you simply don't understand the nature of iterative software development. With every improvement cycle you worsen the quality of the software, that is simply a given. After that, you need a cycle of bugfixing to bring the software to the intended quality standard.

 

Unfortunately, even though the tester team is very hard at work, at this point the software is becoming so huge and complex that it is impossible for the testers to cover everything in an acceptable timeframe. That's why sometimes bugs slip through. However, thanks to the autoupdater, ED can now quickly fix the bugs that have escaped QA.

 

In my experience, the last update to 1.2.1 was the most stable MP environment since at least 1.1.1.0, if not even 1.0.2. No reason to paint such a black picture at this point. Yes, the situation right now is inconvenient, but the quality of 1.2.2 is soon going to improve.

Edited November 17, 2012 by sobek

[leafer]

Thats why I leave long time ago. Sorry, I'm not as forgiving as my previous speaker. Showstoppers after how many years of development? And worse: New introduced showstoppers, and not for the first time. I know this will be deleted, but s.o. will read this and hopefully pass it on: This is simply bad quality management.

 

What show stopper after all these years? All these years I haven't had a show stopper from ED. Terrible fps, for me, since the last update, but that hasn't stopped me from flying.

[BRooDJeRo]

Is there any ETA on the 'lets-give-the-server-a-instahardwarecrash-by-pushing-the-ladder-button-in-the-A10C' bug? There seem to be some Bond-like villans in the erea that have an itchy finger around that button on public servers when the battery needs to be turned on. :pirate: :glare:

Edited November 17, 2012 by BRooDJeRo

[Maxpilot]

No, you simply don't understand the nature of iterative software development.

 

Beyond some questionable interpretations: I don't want to be part of it. Thanks for the info.

[sobek]

Beyond some questionable interpretations

 

Well, you clearly hold the opinion that fixing said showstoppers is a one time thing. It isn't, as such, development time has hardly any relevance.

 

Feel free to correct my interpretations when they are wrong.

[Pilotasso]

Same problem here. After 4 attempts last night I managed 1h of play. I didnt start from the mutliplay icon that time. I entered via DCS world and then chose multiplay within, with windows aero option disabled. Maybe just placebo...

[ENO]

Thanks brood! Rep inbound.

[sorcer3r]

No idea how stable 1.2.2 is at all. I only tested 1.2.2 once yesterday with the Ka-50 on the 104th server.

I got a freeze after 10-15minutes. No crashlog produced. I will wait for the next update and test again.. sometime. :)

[sorcer3r]

My server and client seem to run stable for me as well as many other people visiting. Even with high ping (200-250). Sometimes i see weird people logging in and out a couple of times that give me odd feelings.

 

What is your server's name? just for my interest. :)

[BRooDJeRo]

When it runs its always called Underground nuclear facility. It doesnt run 24/7 at the moment.

[Maxpilot]

Feel free to correct my interpretations when they are wrong.

 

You are right, in my humble opinion same or similar bugs has not to arise several times - at least testers should be sensitized to some crucial and evident points (FFB trimming, MP stability).

Besides that I didn't realize that this development approach is applicable for mass-software - my fault. If it works, good for ED! (yes, yes, and for MS).

 

But the point is: I prefer reasonably finished software.

[badger66]

Unfortunately something like that is not possible.

 

And why not ..... In every other sector of business , a guestamation isnt too much to ask for . In fact an estimate is the norm .....

 

Im getting pissed again too ..... seemed to work better for awhile , then bang . Whats the point of introducing a new product into this world , when you dont have world working properly in the first place ?

[Heli Shed]

MP is now ridiculous for us, again.

 

I have removed all AI from Op Dynamo as a result. LYNX (our server) will now remain open for the public for the foreseeable future as a result and to aid in stability testing, and identification and isolation of CTD circumstances so that we can better inform ED perhaps.

 

feel free to do what you will, but try to stick to the actual mission brief. DCS Logs are being archived for ED.

 

Regards

 

'T'

[macedk]

MP is now ridiculous for us, again.

 

I have removed all AI from Op Dynamo as a result. LYNX (our server) will now remain open for the public for the foreseeable future as a result and to aid in stability testing, and identification and isolation of CTD circumstances so that we can better inform ED perhaps.

 

feel free to do what you will, but try to stick to the actual mission brief. DCS Logs are being archived for ED.

 

Regards

 

'T'

 

Cool tyger ...as always :)

[BRooDJeRo]

I must say that the latest 1.2.2 is a heap of stable for compared to older versions. On my end theres 2 bugs poking around, but they seem to be somewhere on a list.

The wives and girlfriends need enough attention in the weekends too, before the coders can return to do what they love the most during weekdays. We men need them for good food and clean underwear, theres no need to make them unhappy.

[BRooDJeRo]

Oh my, threadmixing in progress. :megalol:

 

Btw, i've onlined the server for the curious ones earlier.