bengo

There are multiple threads about this issue already. Please join one.

Really weird community-behaviour : everybody is complaining but only a few go the extra mile and supply the log-files which have been requested many times. If we don't supply evidence and clues (which are in the log-files) the devs have nothing to start from. So please guys, it's good that you're reporting having this issue, but try to be complete and attach the zipped server- and client-logfiles. B

Please join this thread. Maybe together we can get our voices heard : http://forums.eagle.ru/showthread.php?t=92767 B

Hi, I've started this thread in order to differentiate this issue from the other multiplayerproblems being reported. In an effort to track this bu properly, please, only report in this thread if you have the following problem : "The server you want to connect to is up and running (not crashed, CTD'd...) but it is not shown in the masterserverlist." Every post should be accompanied by server- and clientlogs, otherwise ED have nothing to start their search from. Just found the 74th server up and running, but it was not in the masterserverlist. I could ping it without a problem. Here are the logs. B Serverlogs20120807.zip ClientLogs20120807.zip

Hi, got a "connection interrupted" last flying on our UK-based server. Two other pilots, one from the UK and one from Canada, had no connection issues and could continue their flying. No CA-slots. Mission was "Clear Tvarkcheli", adapted for multiplayer. CllientLogs20120805.zip Serverlogs20120805.zip

Yes

More logs. "Connection interupted" after flying around in a KA50 a little bit and then switching over to SU25T. Crashed while I had the new load-out screen up before starting electricity or engines. Accidentily restarted my client session before backing up the logs, so I'll only submit the old log. Server did not crash and could be logged onto and entered afterwards. B serverlogs20120801_2000.zip clientlog20120801_2000.zip

Okay some good data again. This time I got a "Connection interupted" while I was flying on the server alone. 41 seconds after taking off it happened. Went into teamviewer to see server is still iup and running. Extracted the serverlogs without stopping the server and zipped up my clientlogs. We were able to reconnect to the server without having to restart anything. Btw, I hope I'm not cheering too soon, but I noticed our server did not drop from the masterserverlist in the past 24 hours. Is that because it's being fiddled with or is it just coïncidence ? I'm hoping for the first of course. B Serverlogs20120801_1901.zip clientLogs20120801_1902.zip

New logs, server was not in masterserverlist, nobody was on the server, could ping the server but could not join by using "Connect by IP". Always received a "connection interupted." Funny thing is that the server restarted the mission (servman is active) each time I tried to connect but I would always get "connection interupted". It even created a track-file for each attempt. So here are the serverlogs from when I first found the server, and the serverlogs after I've tried to connect to it by "Connect by IP" Bengo Lynxlogs20120730_2218.zip Lynxlogs20120730_2223.zip

Rgr

Hey Groove, do we need to keep sending in logfiles, or is the cause of these problems found ? B

More logfiles. This happened while at least 7 pilots were flying on the server tonight. I fired up multiplayer and was able to retrieve to masterserverlist, only to see that the 74th server was not in the list, but 7 players were flying on it at the time. I then backed out and started copying the logfiles from server and my client. After that, I decided to try and connect to the server through direct-ip but it crashed after I logged in and before it showed the masterserverlist. I then collected the log-files from server and client again. B logs20120729_2245.zip logs20120729_2246.zip

Sounds to me you're still on the old version of DCS world. Plenty of servers in 1.2.0.

Hi, about 2h50min after I've restarted (cold boot of Windows) our server it has dropped from the serverlist again. Cannot connect to it through "Connect by IP" either. Can ping the server with an avg of 39ms. Attached are server- and client - logs Serverlogs20120726_1654.zip ClientLogs.zip

Even smaller needles have been found in much bigger haystacks. Tracing and logging comms can reveil even the tiniest error in a protocol. Good luck ED B

Hi, here are the logs from our server when I found her still running DCS but she was no longer appearing on the masterserverlist. Tried to look her up in history : not there. Tried connecting via IP : connection interupted. Server name : 74th - VFS 'The Flying Tigers' - LYNX TS3:217.146.89.100:10143 mission : Dragon's rookieterrorists IP : 82.17.12.150:10308 Pressed "Disconnect" on the server and launched the same mission again. Server was now back in masterserverlist and I could connect to it fine. If you need more info, please let me know. B Lynxlogs20120726_1403.zip

Skymad, no need for a track yet, send in your log-files, they contain information on your connection and what is happening on your computer and maybe even why it crashed. If they need your track, they will ask for it. B

Hey Skymad, sorry to see you're suffering from a multiplayer issue too. But you are not providing any information here. We need to get as much info as possible to ED so they can search for the rootcause. That means describing exactly what you're experiencing and exactly when it happened and what you were doing. Also mention which server you were trying to contact and upload your log and crash files. and post your system specs. B

Thank you Viper and Groove for this feedback. This is the first official reply stating that there's an issue indeed. I've submitted server- and client-logs aboutthese issues two months ago. Even got a reply back that they were indeed helpfull, and then it was like talking to a stone : no-one from ED would reply to any questions on this issue. Now, since we seem to have your attention, can you comment on this other long-standing issue : "server gets dropped from the masterserverlist eventhough it is still up and running and can be accessed through direct IP." ? A simple "yes we know about it and are working on it.", or a "No, never heard of that one." will suffice. If there's anything we can do to help clear these issues (I'll try to submit logs) please do ask. The sooner we solve these, the better. B

I wouldn't put my money on it. It's a problem that's been reported to ED for a long time by many people, but so far no solution, not even a confirmation they know what is going on.:(

Okay then, how come there's been no feedback on the "server-gets-dropped-from serverlist"-error and the "CTD-while retrieveing the masterserverlist" eventhough reported by many pilots and squadrons, and despite sending the requested log-files to ED. There not been an official reply on this issue since I sent in some log-files two months ago. ED testers do not reply in threads where these problems are mentioned. Ed does not reply in threads where these problems are mentioned. Feels a lot like these issues are being ignored. We've been reporting these errors for quite some time now. Simple question: does ED know the problem exists ? Do the testers know the problem exists ? I'm not asking for an immediate solution, a simple "Yes we know this problem and we're trying to fix it." or a "No, we've never heard about this problem." will do fine, but sadly I've not seen any reply. In the latter case I (and a lot of other pilots in the community) will be glad to offer any assistance necessary to fix it. B

Issue is known by the community for some time now. We've tried to let ED know that this issue exists, by numerous posts en pm's, but there never was confirmation from ED that they know there's an issue with it. B

Please ED, stop denying this issue. There are multiple threads about it for several months, but no reply from ED. The community is very annoyed with this error. Again, here is what happens : Sometimes when people start up multiplayer, enter their name and password and press connect, the program ctd's before the list of available servers is printed on the screen. It can take up to 30 minutes before they can get to the masterserverlist again. During that time the program will ctd each time the player tries to connect to the masterserver. And then (after those 30 minutes) -without anything being changed on the computer (no reboot, no parameters changed)- all of a sudden the player can connect again. When this happens it is not a single pilot that can not connect, but multiple players from different continents are experiecing the same thing at the same time. So somewhere in the communication with the masterserver there is a flaw. Is it in the (players') client or is the masterserver not replying in time/sending invalid information ? That is for ED to find out. But the problem is real. I've asked in posts in this forum if ED is aware of this problem but did not get an answer. Second problem that we're dragging along for a long time (too long ?) is that servers get dropped from the masterserverlist after some time, eventhough they are still up and running and can be joined by using direct IP. This issue has been discussed with Ed and I (and several other players) have provided log-files of this issue to ED. We even had a reply two months ago that ED got usefull information from those logfiles, but the issue still exists today. So, again, does ED know about these issues, and is action being taken to fix them ? B

+1 We've seen it happen to pilots from Europe, UK and US at the same time. Definately suspicious. B

Deleted