![]() |
|
CoD Multiplayer Everything about multiplayer in IL-2 CoD |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Well,
I'd love to have more missions up and even get some coordination going on, but the problems with the game limit what we can do. You fly in formation with twin engine planes you're likely to get a launcher crash within 20 minutes - single engine planes are much better for some reason. Then you have the launcher crash problem itself. This limits the distance (realistic flight times) that I would love to have for missions. So the best spot on the map, mission-wise, using the full channel map, is where it's closest between England and France. Anything doubling the flight times will lead to many people wasting a flight just to finally crash. As far as server rotations go, we used to do that, but soon found out that if the server doesn't cycle every so often - (in other words completely shut down and restart) - that there will be people that can never connect due to steam errors. Willie has released a server commander similar to a beta state of FBDj, but that won't shut the server down, so attached below is prime example of why the server has to be restarted every so often. To give you an idea of what I'm talking about, you'll notice what I have circled. This (null) is actually a player that tried to join the spits server and failed steam auth. Almost 11 hours later his instance of failing steam is still in the server cache/stats listing. This means that whoever that player is will never be able to join that particular server until the server/steam is completely shut down and restarted. ![]() With that said, to avoid these types of issues we've had to create tools that will automatically shut down the server, shut down steam, restart the server, restart steam, watch for steam disconnects, watch for steam server shut downs, and perform a variety of tasks based on which one of those items fail. So lets say noone gets the objectives in the mission window (time limit) and the match ends in a tie, we use scripts to start our mission end cycle which will start the actually server rotation cycle 2 minutes later. For instance: Code:
////////////////////////////////////////////////////////Snippit/////////////////////// { GamePlay.gpLogServer(null, "The match ends in a tie! Objectives still left for both sides!!!", new object[] { }); GamePlay.gpHUDLogCenter("The match ends in a tie! Objectives still left for both sides!!!"); Timeout(10, () => GamePlay.gpLogServer(null, "Mission is restarting soon!!!", new object[] { })); GamePlay.gpHUDLogCenter("Mission is restarting soon!!!"); Timeout(10, () => Process.Start(@"C:\Users\Administrator\Desktop\ATAG_Server\W_O-Hyperlobby\Server_Cycle.exe")); It has taken a massive effort by us simply to keep the server up 24/7 based on the state of the game and steam issues. There's more coding in the tools just to make the server work than in the mission themselves. I do want to make a few scenarios like you suggest - IE..-reds win so the front lines move, the blues get pushed back etc.,etc or vice versa if blues win, kinda like a static MP campaign that changes based on who wins the mission, but I've been a little busy as of late. And having the FMB launcher crash on you after 2 hours of work just makes you have to walk away from it for a bit. But please realize we do things a certain way for a reason. We started when the game came out, and after literally thousands of hours amongst us in testing, building, trying, etc., for all this time, we have a really good understanding of what will work and what won't. I don't think many people realize some of the frustrations it's taken us just to try to have a server....work.. Anyhow, more will definitely come, but the games gotta get there as well ![]() |
#2
|
|||
|
|||
![]()
Holy smokes! I had no idea that a) it was so unstable, and b) the amount of work you guys have put in to make it all playable!
MASSIVE kudos to you and the ATAG crew. Wow. Ok, maybe something a bit more casual. What about, for now, simply a set time each week that people try to make? Yes, people are on here and there throughout the week, but if we tried something like Monday Night Flight Night (6PM PST -- the Europeans can mirror this with another time that suits them) every week on the ATAG server just simply to boost numbers -- something a little more coordinated that people can attend, we might just have one night with decent numbers. I'm sure there will be server resets and all kinds of weirdness so we won't keep track of mission successes and failures, it's mainly just a free flight with boosted numbers because there's a so-called "meeting time". Almost like a virtual pilot's social club. Maybe do a mailing list or something, or just create a forum channel for it. Then, when the game catches up, we can expand it a little to include organized scenarios, teams, virtual fronts, all that stuff (most likely in the year 2031, I'm sure). Or maybe Sundays at 11 AM PST (which I think is 7PM GMT) to include the Europeans as well. It kind of shoots my day a bit, but if people are into it and we get good numbers I don't mind -- I'd probably be playing video games any way. You tell me though, if it's going to be a headache it's not worth it. Last edited by Mr Greezy; 01-19-2012 at 04:44 AM. |
#3
|
|||
|
|||
![]() Quote:
Not worth it until the patch. With the crashes, you can't fly formation, or most people won't even make it to the target before their game crashes. Last week, we took off with three 110's with bombs. We formed up, put the belly on the water and ran as fast as we could straight across the chanel to the G10 targets. Direct route, fast planes and only one guy got to the target to drop his bombs. With the slow bombers is worst. You get some 109 to escort you and when the spits show up, the poor guy that tried to help you will crash to the desktop. I'd say. Let's just enjoy what we have for now and hope they fix it.
__________________
---------------------------------------- Asus Sabertooth Z77 i7 3770k@4.3GHz+ Noctua NH D14 cooler EVGA GTX 780 Superclocked+ACX cooler. 8GB G.Skill ripjaws DDR3-1600 Crucial M4 128GB SSD+Crucial M4 256GB SSD Seagate 750GB HDD CH Fighterstick+CH Pro pedals+Saitek X45 Win7 64bit Last edited by Jaws2002; 02-11-2012 at 02:08 PM. |
#4
|
||||
|
||||
![]() Quote:
__________________
ASUS Sabertooth MB--Intel 2600k@4.7--EVGA GTX580 3GB--Corasir 1200 watt psu--Corsair 16gb 1866--Corsair H70 cooler--Corsair 650d case--OCZ Vertex 3--Track IR5--CH Eclipse Yoke--CH Trottle Quadrant--CH MFP--CH Rudders-MSFF2 |
#5
|
|||
|
|||
![]() Quote:
Maybe it is worth testing if many players have this issue. To reproduce the "Server failed authentication" error one can click Cancel while in server loading screen. |
#6
|
||||
|
||||
![]()
Hey Bliss!
Thanks for that elaborate reply, wish Maddox Games looked at those kind of updates, hehe. Looking forward to whatever happens on the server in the future, thanks for all the efforts in any case =)
__________________
Cheers |
#7
|
||||
|
||||
![]() Quote:
Doesn't always work I'm afraid Ataros. I've seen differing results. (of the solution not the cause!) |
#8
|
||||
|
||||
![]()
attacking radar base in I12 in barely impossible, because 90% Clod Freezes
|
#9
|
|||
|
|||
![]()
Restart the game and clear your cache between sorties. It helps a lot. Also, don't fly close to, and look at, human flown, multi engine planes for too long. That's the only way to make it trough the mission without the crash.
__________________
---------------------------------------- Asus Sabertooth Z77 i7 3770k@4.3GHz+ Noctua NH D14 cooler EVGA GTX 780 Superclocked+ACX cooler. 8GB G.Skill ripjaws DDR3-1600 Crucial M4 128GB SSD+Crucial M4 256GB SSD Seagate 750GB HDD CH Fighterstick+CH Pro pedals+Saitek X45 Win7 64bit |
#10
|
||||
|
||||
![]()
restart the game is like a crash, so I wont do that lol
|
![]() |
|
|