![]() |
|
|||||||
| CoD Multiplayer Everything about multiplayer in IL-2 CoD |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
|||
|
|||
|
ok i will later, thanks
note - never had this before, last week logged fine several times on JG27 server |
|
#2
|
|||
|
|||
|
all i got was "server authentication failure" a few seconds after hit connect, didn't even saw the loading bar; so i never even got to enter the pw
|
|
#3
|
||||
|
||||
|
We missed everything
Perhaps too high at 16-18k and from Biggin Hill we may not have reached the coast in time. Had a pleasant cruise over Pas de Calais but no trade. We had one feezeup/disconnect. Hard to blame that one on memory leak as he has 16Gb RAM although CoD may have run out of legroom as a 32bit application.
__________________
klem 56 Squadron RAF "Firebirds" http://firebirds.2ndtaf.org.uk/ ASUS Sabertooth X58 /i7 950 @ 4GHz / 6Gb DDR3 1600 CAS8 / EVGA GTX570 GPU 1.28Gb superclocked / Crucial 128Gb SSD SATA III 6Gb/s, 355Mb-215Mb Read-Write / 850W PSU Windows 7 64 bit Home Premium / Samsung 22" 226BW @ 1680 x 1050 / TrackIR4 with TrackIR5 software / Saitek X52 Pro & Rudders |
|
#4
|
||||
|
||||
|
We weren't able to use this TS last night due to short notice but it will be up again for next week's mission.
teamspeak.ukatc.com People can also connect directly to the IP address: 77.251.29.22 I hope we can get everyone on it, we are learning fast. I thought it had all gone to rat's when we saw and heard nothing last night but cheesehawk has explained why it was so quiet Well, it was the 13th ! Is last night's mission to be run again?
__________________
klem 56 Squadron RAF "Firebirds" http://firebirds.2ndtaf.org.uk/ ASUS Sabertooth X58 /i7 950 @ 4GHz / 6Gb DDR3 1600 CAS8 / EVGA GTX570 GPU 1.28Gb superclocked / Crucial 128Gb SSD SATA III 6Gb/s, 355Mb-215Mb Read-Write / 850W PSU Windows 7 64 bit Home Premium / Samsung 22" 226BW @ 1680 x 1050 / TrackIR4 with TrackIR5 software / Saitek X52 Pro & Rudders |
|
#5
|
|||
|
|||
|
Nope were going to stick to the script and run the last mission for next week. These are all lesson for next time.
I think we will have to wait for the next campaign until this CTD to be fixed or at least if someone can find a solution... Hopefully next time, we will have an online section where people can log into to get briefings, a seperate TS3 for RED/BLUE and stats. We also aim to run double the number of missions. Also have some red attacks! About the one spawn thing, we are considering different options but really I think there is only 3: 1.Use the same system (No respawns after X amount of time) 2.Use SNAFU's server script 1 life/multiple aircraft - but does this account for being captured? 3.Dont use any restrictions but shorten down the mission so a respawn is a waste of time... Now I can hear some of you thinking, why have one at all why not fly as much as we want?! The answer is simple, with no consequnce people fly wrecklessly and unrealistically. So if you only get one life or one chance to fight you will bring your best flying skills! It also seperates it from being like a public server and makes it allot more exciting (or frustrating). Last edited by 5./JG27.Farber; 11-14-2011 at 12:35 PM. |
|
#6
|
||||
|
||||
|
Quote:
I'd go for options 1 and 2. Allow a window for spawn problems, even takeoff-crashes and collisions among guys just not used to doing this. Then if you can script in 1 life and respawns that would be great. You could also perhaps script in a takeoff delay for bailed pilots. If it were possible to identify which side of the channel they were on you could delay their takeoff for say 15 minutes if over friendly territory or 30 mins if over the channel or enemy territory. Or just a global delay. Just a thought Here's a couple more ideas from what we've done before, probably for way in the future. Have everyone pre-register for this and assign them to their (preferred?) unit in advance. Also allow this to be done by CoD Squadron with expected numbers (well, we do this now). Walk-ons would be reduced and easily handled on the night. Have a Command structure (by direct request or volunteered during registration?). Axis/Allied Commanders could even discuss the campaign, settings (not specific targets of course) but most important be made aware of their order of battle and the amount of 'intelligence' available to them. The main advantage would be a focal point for each side. Commanders decide tactics and issue briefings to their unit leaders in advance. Spreads the load and gives some structure instead of trying to work it out on the night and perhaps not knowing who is doing what. We haven't really cracked that yet. Only issue the server password to unit commanders via the appointed Teamspeak server on the night so that everyone is encouraged to actively co-operate and prevents gate crashing (we're partly there with passwording). Also allows a clear and definitive 'GO' to be issued to the Commanders when the server is started. Just a nicety really, everyone could turn up 'in uniform', i.e. if they are assigned to 74 Sqdn they turn up re-badged as say 74RAF_klem or JG52/3_Farber. Looking forward to Sunday.... and the next one
__________________
klem 56 Squadron RAF "Firebirds" http://firebirds.2ndtaf.org.uk/ ASUS Sabertooth X58 /i7 950 @ 4GHz / 6Gb DDR3 1600 CAS8 / EVGA GTX570 GPU 1.28Gb superclocked / Crucial 128Gb SSD SATA III 6Gb/s, 355Mb-215Mb Read-Write / 850W PSU Windows 7 64 bit Home Premium / Samsung 22" 226BW @ 1680 x 1050 / TrackIR4 with TrackIR5 software / Saitek X52 Pro & Rudders Last edited by klem; 11-14-2011 at 12:58 PM. |
|
#7
|
||||
|
||||
|
Quote:
It's been great talking to folks on the teamspeak servers and getting to know the other squads. Just speaking for myself as a 'lone wolf' pilot this has been a great opportunity to get acquainted with some squadrons that I might want to join up with. I'm confident that the crashing issues will be resolved at some point in the future and at that time there's a lot of things that will open up to us in terms of running events like this. That said, I don't think we should stop putting events of a similar nature on, but maybe scale them back a bit to find the sweet spot where crashes aren't so much an issue. Maybe running with a player limit will help, or altering the structure so that respawning/restarting is figured into the mission. Perhaps limiting the participating numbers to 24 pilots will allow the mission to run with fewer people suffering crashes. I would love to run events like this, but I lack the dedicated server to do it. I have plenty of ideas of how to create a campaign structure though. I won't post them here, but if anyone is interested, I'll create a thread for those kinds of thoughts. Anyway, thanks again for all the hard work and planning required to put this thing on guys! Salute!
__________________
Pilot #1 (9:40 hours flying time, 3/0/1 Fighters, 7/2/0 Bombers). RIP No.401 Squadron Forum ![]() ![]() ![]() Using ReconNZ's Pilot Log Book |
|
#8
|
|||
|
|||
|
Gent's,
Last night several of us flew around without meeting the enemy, this didn't happen the week before, mainly, I imagine, because the previous week we were given the flight path of the Buff's. Can we do this again for the repeat of mission 3 next Sunday? It certainly makes for a good simulation of the information provided by the RAF Radar controllers, much better than the in-game radar reports, which are a bit pointless. But, most importantly, the previous method ensured we all got together for a big fight Along with this, coud we have less German Bomber formations BUT Bigger German Bomber formations? so instead of three groups of 9 or 12 planes, could we have 1 formation of 40 planes? it would certainly make it easier to find, for both sides, and be more Battle of Britain'ish. It would be interesting to see how far the server can stretch with AI bomber formations... will we ever get to formations in the hundreds? Just a suggestion. 56RAF_Witch CO No. 56 Squadron RAF |
|
#9
|
||||
|
||||
|
S!
Lentolaivue 34 had somewhat better experience this time. Only 1 out of 3 us had the launcher crash this time
__________________
AMD 1055T Hexacore@3,4GHz - 2x4GB 1600MHz DDR3 - ATI 6950 2GB, flashed to 6970 shaders - Windows 7 Ultimate 64-bit - 30" LG W3000H (2560x1600) - TM Warthog Stick + Cougar Throttle - wooden DIY pedals with Hall sensor - FreeTrack |
![]() |
| Thread Tools | |
| Display Modes | |
|
|