We should do this mission again yes.

Too many had problems and we're here for the fun. We will do our best to get things sorted out before next mission.

working password seems to be a problem as well . :oops:


Short summary as a BF110 pilot this misison:

Successfully escorted my flight leader who had bombs to over Dover where I ran into a cloud of bandits. Convinced that this would be my end, with no 109s in sight I plunged into the cloud and shot at multiple aircraft, then I made a run for it. A long flight of evasive manoeuvres didn't pull off as I flew into another cloud of bandits, I closed my radiators and dived down to gain speed. After a long run I managed to escape.

As a result of my shooting I downed 1 Hurricane, and another one while I returned to Dover for a second run.

Krupi, Karaya and Adonys got launcher .exe crash within a few minutes, I lasted an hour or so, and was just about to land when I got the .exe as well :(
Mission looked good though guys, just a shame we have these problems.

Forming up was much better this time for our guys :) And squadron CO's plan led us to a couple of flights of stukas.

I got stuck in to a flight and flamed one, gave another an oil leak before heading back to hawkinge to regroup. By this time a lot of our squadron had suffered from launcher.exe crashes :/

Managed to regroup with a few of the remaining guys and get stuck in to a dog fight over Dover. Put some bullets into a 109 and took a partial claim before heading back to Hawkinge.

Assisted a Spitfire in forcing a 109 strafing our field to crash and then did some top cover for the landing planes before landing myself.

launcher.exe crash JUST as I switched off the engine :P

Again thanks to the guys hosting the campaign. I look forward again to next week!

I really enjoyed that and my first time in a co-op mission flying with group of great guys. I don't think our flight lost a single Spit and managed to bag a few hun.... :grin: Not sure about the overall result but great fun!

big let down for me. :sad: couldn't get off the ground. spit would spin around like crazy (wind???), even with full rudder i could not keep from turning to the left, spit just wouldn't get enough speed to get airborne, huge bumps even at the lowest speed that wrecked the plane, wtf... first time i hit engine start the plane stutters so much it went nose to the ground. never have i seen anything like this :confused:

what's worst, i have been of all ppl one of the most blessed with those bugs that seem to be random or case dependent; AA worked for me from the beginning, launcher very rarely crashes, don't suffer memory leaks...

seems everyone else got airborne, so that's something with my system, but wtf, stick was properly calibrated and working perfect minutes before, don't know what to say. hope it turns better next week :???:

last note - seems many others had problems of their own, if you guys want to try this one again i vote yes :mrgreen:

JG13_Admax and I took Bf 109E-3's out of Coquelles and escorted the gaggle of stukas over towards Dover. We were unable to communicate with the rest of Axis due to being kicked from teamspeak every 2 minutes, and this really hampered our ability to contribute to the team, I think :(

As it was, we encountered two Hurricanes up high between Dover and Manston, getting a confirmed kill on the first and a probable on the second about 10 minutes later.

We engaged offensively on two spitfires at about 5000 metres but were interrupted by RAF single-engines coming in above us and were forced to extend away. I took some hits to my coolant line in the process, but eventually we gained the altitude advantage and the spitfires dove low for home. It was at this point the bombers we were supposed to be escorting were beyond visual range, but without Teamspeak there was no way to know where it was they had gone. :evil::evil::evil::evil::evil::evil::evil::evil:

We then spent the next 20-30 minutes stalking what eventually turned out to be 2 ghosts midway between Dover and Calais :???::rolleyes:

At that point my engine blew a gasket and the governor, forcing me to glide back to Coquelles, engine-out. Admax followed and we called it a day.

Thanks 5./JG27 for hosting! We had fun despite the setbacks, looking forward to next week for sure.

i was, 20h GMT; several guys on my channel were logging in at the same time; logged in a few times myself until it got stable, but something went wrong with my connection. you were supposed not to switch planes, but the first time i start the engine the plane went nose to ground, so had to respwan... maybe from there on all went wrong...

56 Sqdn AAR
 

56 were assigned to fly as 604 Sqdn (Rotol Hurricanes) out of Manston. During the leaders' planning 56 elected to take the He111's (pre)-reported to be heading towards Dover at 13000 ft. The planning went fairly well once we got the leaders together and thanks to Osprey for handling most of that.

We took off very soon after scenario start and climbed to 15000+ inland of Dover with the intention of being above the bombers before turning and meeting them mid-channel, avoiding 109s if we could. Two of our sections (5 pilots) were closer to the coast than mine (2 pilots) and ran into more Hurricanes and one or two lower 109s. We left them as we sighted the bomber formations coming across mid-channel towards Dover (He111s at 13000ft and Do17s at 8000 (allocated to another Hurricane Unit). About now some 109s were sighted. I called it all on leader channel and requested Spitfire assistance. My pair were closer to the bombers and went in first. The other five came in behind us but some ran into the 109s. The rest of us were able to engage the He111s. We knocked down two or three, damaging more but had to rtb when ammo was gone. More He111s fell later. One of our guys had some ammo left and went to help a squadmate still tangling with 109s but he eventually had to bail out from a flat spin. Another of our guys deadsticked at Canterbury due to engine damage from He111 return fire. Another of our guys had to crash land near the bombers target due to engine failure. I landed Manston wounded as did one other. The rest landed safe.

Total 56 score 4.91 which, the way the scores are allocated by share, probably indicates 5 and perhaps 6 shot down with others taking part-shares of the kills. We lost no pilots although at least two were wounded and we lost one Hurricane plus one badly damaged and three lightly damaged.

We had no PC/game crashes. We did restart our games every time he server was restarted to clear memory (in case the memory leak stories are true). Several of us had skin download turned off.

We will be back for Adler Angriff next week :)

S!

Lentolaivue 34 after action report:
Taxiing on the the ground, hmm, fps' at bit of the low end. And when started to build up speed on take off -> fps hits rock bottom, more like spf(seconds per frame) :) Normally I have something like 20-40 fps while playing online.

I barely get airborne. Squad mates reporting the same fps drop while getting airborne. The slide show continues while higher up. And then the game froze, launcher crash. After a minute or so, another squad mate has the same, and then the last one also. Mission end for us :)

Could the coop style start where there are lots of objects on the field simultaneously in a close proximity do this?

We failed to get the mission brief so we missed out on the mission. Was not sure if it was been flown. Can the admin please PM me a brief for 69 GIAP for the next mission. We would like to take part :)
It really sounds like fun

No matter the server problems, SYNDICATE enjoyed themselves!
We were in on a bounce of around seven Stukas around Hawkinge and I think we share some 4-5 kills between ourselves and other squads.
On rtb we engaged two low flying 109:s and we dispatched both.

When approaching homebase two of us suffered Launcher.exe and were out of game.
The other two landed.

Enjoyed the experience!
Thx for doing this JG27! S!

There has been a lot of talk about memory leak. I see you only have 4Gb RAM. My 6Gb runs at just below 4Gb in CoD (about 3.8Gb) so perhaps you are hitting some kind of peaking in RAM usage or if there is a memory leak you don't have much headroom.

Also, there were several server restarts. Try closing and restarting the game if that happens to see if that improves things. Another (possibly folklore) idea is to Alt+Tab to the desktop once you are in the cockpit. Some people claim that helps. I did both of those things and didn't have problems, nor did my Squadmates. I'm pretty sure we all restarted the game after each restart.

I have 8 gig of ram and restarted my game after every server restart plus alt tab once in the mission and I had Launcher crash after about 15 minutes. Strange.
System:
Win 7 64bit
8 gig ram
Core i5 at 4000 clock speed
Asus mother board
Ati 5700 extreme

Well I guess that blows those theories... unless another weakness is VRAM and possible leak. My 1.28Gb GTX570 runs around 1.1Gb and less in CoD.

It is strange though, none of our seven guys had a problem.


Other variables?
We were flying Rotol Hurricanes (but so were 501 Sqdn who had many crashes)
We were on ATAG Teamspeak (but so were 501 Sqdn who had many crashes)
We flew out of Manston with limited numbers (501 flew from Hawkinge with many others)

ermm... I had my mascot just above my screen and my underpants on inside-out :D

ASUS Sabertooth mobo
i7 950 @ 4GHz
6Gb DDR3 RAM
EVGA GTX570 GPU 1.28Gb superclocked
Crucial 128Gb SSD SATA III 6Gb/s, 355Mb/215Mb Read/Write
850W PSU
Coolermaster HAF912+ case
Windows 7 64 bit Home Premium
Samsung 22" 226BW @ 1680 x 1050
TrackIR4 with TrackIR5 software
X52 HOTAS
X45 miscellaneous controls
Running TS Notifier

I have been doing some server jumping, and I have never seen the game take more than about 2,5GB. Windows taking about 1GB so there's always been about 0,5GB free. Nevertheless, I've been thinking of getting some more RAM.

Yall should seriously consider lowering your settings to what I use. I have yet to have a launcher.exe failure since making the changes. The post is buried in here somewhere after the first mission was run.

Got lucky and found it first try. Give it a go.

Two of our guys has launcher.exes last night during the mission. both of us have 8gigs ram and top end systems...we were both on our TS and both flying rotols. Its not like there was a degredation of performance prior to the event or that we were in the middle of a huge furball or anything,...in fact we had both just had some major contacts with JU87s 10 minutes before and all was running perfectly. Then suddenly "bang"....launcher has stopped working :(

Im guessing its on e of the oddities of the current build and we have to live with it until next patch.

Great mission tho!

We really enjoyed it. J

Just for the record, I wasn't requesting to refly that mission, but rather a 'refly' which allows one to exit and re-enter the server. When the server was re-started I had the chaps restart IL2 to minimise such an event occurring and normally I will not get these freezes at all. Last night, for some reason, I did.

Something else for red only. I think in future we need to avoid airgroups consisting of lonewolves or at least assign a leader with them who is used to some squadron protocols. At Hawkinge everything was fine until the Spitfires spawned in. Quite a few of them ignored the fact that it was an EXTREMELY busy airfield and that all of the Hurricanes were on the taxiways trying to get to a known take off direction. Guess what happened? Spitfires taking off in all directions, towards each other, crashing and even worse slamming into Hurricanes trying to do the right thing. Over the airwaves I had to hear shouts like "He's coming towards us" followed by "he just took me out". Now I hear that SYN were at Hawkinge with Spitfires too I have to question if your chaps were involved in that Jed? I don't know how many you had there but before we set off I was clear that Hawkinge takeoff heading would be east to west on approx 250 from the eastern end (the T marker). Is that how your take off was organised? Perhaps next week one of you chaps can come into the common comms on ATAG and take on board the whole game plan. That would help a great deal. Thanks.

~S~

Not us Osprey. We were the guys in hurricanes using the taxiways who took off in front of some other hurris. Better look for someone else to blame.

As for the issue of comms, we explained our position to the mission hoster with regards to the 3rd party Teamspeak location. He seemed fine with it. We did suggest if there was an issue that we would retire.

Nah mate, not us. The only culpa on our behalf was that we took Hurri Rotols. We were assigned Spits, but originally asked for Hurris, so we overruled HQ by our own design. We like Hurris.
Besides we've been around long enough to know how to behave on a crowded airfield. We have a TS channel. Feel free to join us there next time. It worked flawlessly.

I just re-read and saw that you mentioned Hurris so I don't know why I thought you were on Spits. Sorry.

Blame is a strong word, I was investigating after 2 of my chaps got sidewalled by Spitfires. I take it from your reply though that you will not send a chap in temporarily in order to organise a common objective? Seems a bit odd to me, unless it's that old BS called clan pride which rears its ugly head far too often. It looks as though the red was compromised due to this problem, given that we all thought you were assigned Spitfires in accordance with the PM from Farber but you say you just took Hurricanes. Hmmm.

I'm not sure about the so called memory leak. Two of our guys have 8GB's and went out after about 15 minutes, another guy has 16GB and went out shortly after that. I have 4 GB and lasted an hour, until I was coming in to land...

Osprey. Lets not turn this into something it isnt. This isnt about clan pride and if you want to know what is is about just pm me and I will gladly fill you in. Im not gonna start on a public forum to discuss our thinking. The reason we took hurris is because that IS what we signed up for and we want to continue our assignment from week to week.

I take it you havent pinned down just who WAS flying across your takeoff path from the people who WERE on comms with you then?...

anyway....back on topic..

It all comes down to patience.

People spawn in and get anxious that some other guy is getting an advantage (blues are flying earlier, other reds are up sooner and going to get the kills, etc).

Fortunately for us, the Spits and Hurris in CloD CAN be kept from overheating on the ground almost indefinitely I've found (the Spitfire should be overheating within 10 minutes regardless of your rad settings).We're far better served getting everyone in the air. Take your time. Let the guy in front of you go first even if you're engine is up to temp and he's still waiting. Just wait a minute more. Check your gunsight. Set your compass. Re-check your radiator flap setting.

Another thing. Once we get word of the airfields that we're going to be using, I recommend taking a free flight around it and get to know its layout. Some of us are taking off from fields we never use. Knowing where the runways are in relation to the landmarks and taxiways is very valuable. I would EVEN go so far as to make a little sketch doodle or print out a screen shot of the airfield for reference.

From what we saw (on our side of the airfied) there was a very patient build up of warmed aircraft taxi-ing around the taxiways towards the strip. It was lovely to see a long line of Hurris getting ready for the off.

Apart from the overenthusiastic spitfire takoff route it all seemed very well done. In the air we met flights of Hurris and spits patrolling the South coast at varying alts. When the 87`s were spotted at least 2 groups attacked at intervals...again leaving space for others to get in.

Like you say, Wolv, patience is the key.

Agreed. There was some craziness once the Spits started rolling west to east, but I also felt the majority of Hurricanes did a great job of taxiing and taking off in turn, regardless of squadron.

A lot of it has to do with who's in front. If you see the guy ahead of you doing a nice taxi to the runway, you're likely to follow him. If he just waits until he has barely hit 40 degrees and the shoves the throttle and roars off, you're very tempted to do the same.

So please, to anyone who participates in these things, if you find yourself leading the ground show at the start, lead by example.

Couldnt agree more!. Last night it just so happened that it was SYN_Per that took the lot of us out to the airstrip.

The feeling of uncertainty and nervousness definitely builds while on the ground. "are we all going to get up safely?". It really adds to the emmersion the feeling of lots of other aircraft around you. More of the same please!

Agreed the knowledge of only having one aircraft to get up in makes me nervous about messing up take off... Fortunately had a perfect take off only to get a launcher error 15 mins later :(

Btw saw your vid of the reverse rof crash, best sim vid I have ever seen :D might have to copy it for cod ;). P.s. where did you get the idea behind that vid I swear I have seen something similar but can't put my finger on it...

Regards Comms, my first time but Klem wrote in his post that he asked for Spit support and that wasn't relayed as each flight is in a different channel.

How is info supposed to be shared so that everyone gets to hear the calls ( I asked this at the beginning of the mission and some reference to flight leaders being on 'whisper' was made but it wasn't confirmed wether that was working or not)?

FPS was pretty low at TO due to the number of players (maybe the cause of several LE crashes?). I wonder if it would be possible to spread the groups over more airfields and associate them with a particular fighter type? It took a long time to get airborne which scuppered the plans for our Spits to form up and intercept at altitude ASAP.

Had a good time ourselves. Don't know about the red side of the house, but us in blue bombers made it back safely. We did have some TS problems (kept getting disconnected etc.) on Jg27 server, but it did get better in the end.

Had no crashes or issues in game, only had lower FPS on the airfield, which seems normal for the amount of planes there.

It was nice to see another organized pairing by the reds in last minute fashion again ;)

I'm assuming reds did it like last time. Each flight group was assigned a leader, and all the leaders were setup in whisper. So you could either talk to your own channel, as a leader, or you could talk to all the flight leaders to relay info.

I don't need to know politics, I'm only interested in us having an organised defence against the Hun. The Hurricanes on taxi did indeed look marvellous and I know who the Spits were - next week I'll assign one of our senior chaps to take control of a Spitfire group by re-opening No.64 Squadron and dragging a few of them in. No.501 will take a hit on a couple of pilots in order to achieve this, it's a small gamble but we did get 10 in yesterday.

So for the mission chaps.....

Commanders Call Sign: No.64_Gromic
Unit Full Name: No.64 Squadron
Unit Tags: No.64_
Axis or Allied: Allied
Website URL: www.legionxiii.org/forum
Minimum Expected Turn Out: 2
Average Expected Turn Out: 4
Pilots "on paper" (Total Pilots): 8
Willing to take Public Players?: Yes, in fact we'll need to.
Preferred Aircraft: Spitfire I (CSP)

There were just 2 of III./JG27 participating, due to the wide spread experience with the launcher.exe problem and we two were expecting to crash out any second, so it was hard to enjoy the flight or take it seriously (you don´t care so much anymore when you expect to crash any second). We were just two 109 so barely enough to contribute or achieve the objectiv of an advanced sweep over Dover. Anyhow, we took off and climbed to 6400m. On the way to Dover we were disctracted by some lonely LW planes flying around here and there. Over Dover it was all quiet and clear until it became appearant, that all the bombers were on a low level raid and no more will come on heights I thought they would. So we dived down, I scared a Spit of 3 Do17s and that seemed to be all. Later we went further down, to investigate was going on there around Dover. There I helped a bleeding 109 and scared off a Hurricane of his tail, when I was attacked by another Hurricane, I could evade and the Hurricane spun into the channel after a few (not serious) hits. Then a string of Hurricanes came down on me and there was no more getting away. My squadmate had an AAA hit and so I had to fight it out and ended in a collision, lost 0,5 wing but limped off closer to the coast, so I wouldn´t have to swim that far.

My experience is that more then 4 (6max) players on one comm-channel is more a nuisance than a help and it is hard to structure and organize groups (whisper keys to channel commanders etc) and we usaully communicate in our mother tongue, that`s why we stayed on our own TS.

Thanks for your work 5.JG27, it is a good start. ;)

Ah, Osprey, just worked out who was in the spits myself :P

SYN_MrWolf made the vid. Lot of ppl recognised something about it...prolly the music which was nicked from a dead island preview vid :)

Theres more here if you wanna look:

http://riseofflight.com/Forum/viewto...?f=346&t=22918

and:

http://paddyjed.proboards.com/index....lay&thread=962

My apologies Untamo, I was talking total usage and I just rechecked. I'm sure I have seen 3.8Gb total in the past but of course there may havebeen other things running. Here's my breakdown as of now:

Windows only: 1.54Gb
Plus Teamspeak (+0.3Gb): 1.57Gb
Plus TS Notifier (+0.01Gb): 1.58Gb
Plus CoD...
in Menus (+0.3Gb): 1.88Gb
or
in Server Map Room (+1.37Gb) 2.95Gb
or
in spawned Hurricane MkI (1.54Gb) 3.12Gb and VRAM was 1.044Gb
That's with the channel map but I haven't looked while flying around.

I didn't crash to desktop in this round

my rig:

AMD Phenom II x6
ATI Radeon HD5770
6 GB DDR3 RAM
Windows 7 64bit.

All settings high except ground details. Unlike last time I did had some FPS trouble over Dover. But that might have been because I ran into 20 enemy aircraft :)

We organised Flight leaders to have a whisper key with all the Flight leaders on it. It worked fine, we all knew how to do it, but if there are flights on some other TS we are wasting our time. I didn't even realise the SYN guys were flying.

Sorry guys but if we can't even agree on a comms server then why are we bothering with these scenarios? The whole point is to work together with a plan oherwise you may as well jump onto any old server and play your own game. I really don't have time for 'I wont talk to him'. You're spoiling it for everyone else.

I understand there's some 'history' so why are we using the ATAG TS? Why not the Jg27 one provided? Or would you like me to try to find another one?

Again really enjoyed the mission.

The procession of Hurricanes taxiing at Hawkinge was great.

The combat also felt very realistic, getting from a sky full of planes to an empty one in a matter of few minutes.

The new sounds are amazing, hearing a Spit land just after me back at Hawkinge while sitting at the dispersal really sounded and looked lifelike.

Had a few stutters at take-off and when bouncing the Stukas.

No crashes in two sessions, my specs are below and I run the sim at med-high settings.

SYN_Ricky

Its really weird and there's obviously more to it than mets the eye. I always go through the Clean boot up, restart if server restarts, Alt+Tab out/in etc,. almost as a superstitious mantra now but who knows?

The other BIG variable I didn't mention was individual settings both in-game and in your GPU manager where game profiles are stored and what else may be running in background. Maybe some guys might want to look into the current version of FS Autostart or Alacrity to kill off unwanted processes.

But I'm sure now there's more to it than that.

well we understood we would use the jg 27 one, and all of a sudden on the first night it changes to another ts3 server???

edit: SYN have a ts3 server, we could use that one

Ah, but we (the Spits) were told to intercept BFs by climbing to 4/5000m altitude whilst heading for the French coast and try to catch them climbing. In all fairness the rush to get airborne became a misplaced priority and lack of experience in these sort of organised encounters took its toll.

I made an error but you learn from these mistakes and make sure you don't repeat them. By the time I did get airborne having waited patiently behind the Hurris our mission objective was pretty well scupperred.

I would have thought that having fighter groups spread over more airfileds would allow them to get airborne and form up quicker. They could also form a 'big wing' if necessary far quicker.

As I said, this was my first experience and OK, only 1.4 kills but I would certainly like to join up with a Spit squadron and hone my group co-operation skills - flying solo is one thing but flying as part of a much bigger plan is wholly different. I will definitely be logging into next weeks match for sure and look forward to being part of Gromics group.

I'm with Klem on this. We only gathered on ATAG because it just happened that way. Like I said, I'm not into politics, too much 'clan fighting' goes on - I've witnessed far too much from the USL and it's always the other clans fault.

Might I suggest that we do start using JG27 server and bloody well get on with it....

As for Luftwaffe comms, it's well known that it was badly organised, lots of opposition from senior people saying that RT wasn't required and different sets between groups. The RAF had different channels for different jobs but could communicate with each other on the RT

It's not my business but please, let this first campaign not increase hostilities between units. That would be a very bad start for online competent campaigns in this already trouble filled game. You're more then welcome on 5./JG27 TS3. But it would be even better if you agree to join each other up on a different voice com server, because our server is getting stressed a lot I reckon.

I'd be delighted if that happened. Unfortunately, for now, our own TS3 only has 25 slots so it's not up to it. Any advance on that? Klem, what do No.56 have?

Just noticed the above in your post, that instruction was not given - I certainly wasn't aware of it, in fact I lined up behind Hurris and Spits facing West to East with Hangars on port side, hence the problem of TO in wrong direction. Apolgies for that but will hold and check in future.

I think maybe it's time to relocate that teamspeak server :cool:

Yup, it was given via whisper to your flight lead so I guess it never go relayed on. It's ok, just means we'll get No.64 leading the Spits for next time :)

Just let us know. It's a shame one team is trying to stir up drama over something as simple as teamspeak. Ours is setup for an unlimited amount of clients and has more bandwidth than could ever possibly used.

The whole reason everyone gathered on ours is because many players not in squads were picked up there as quite a few players get on for the MP server.

I'm not gonna let someone holding a grudge ruin this for everyone. I'll join any teamspeak server, but it was clear yesterday that you guys will need a different setup/license to host that many clients without issue. Ours is a good choice simply because it's already setup for it. Again we'll follow suit to wherever. I just hope some people can swallow their pride a bit. Bickering over this is ridiculous.

Bliss would you be happy making up seperate channels on the aTAG TS for the different squads participating in this event as a temporary measure?

I think its new concept for quite a few guys. We should have thought of the time factor to get the Spits up and away and given them room to do that but hindsight's a wonderful thing.

Its really important that we get the detail right in the leader briefings so don't be shy to put your point. To be honest with such a large map compared with the numbers available something is always going to slip through the net.

I know plans only survive up to the point of engagement with the enemy but we can try to get engaged on our terms.

Yes, Ulrich Steinhilper was the man given the job of driving RT comms through and he even had problems with Galland (and the other 'Spaniards' as he called them) not wanting to know during the early period.
In the RAF the Squadrons may have heard eachother but control and direction mainly came from the ground from a Sector controller. We don't have that so we arrange for the leaders to talk to eachother, cutting out the middle man.

Of course. I've already told Rudelmann that their leaders could have admin control to a particular section so they could add/setup/edit channels for their own event however they liked.

Rubbish eh? So what's your excuse for not joining where the red were last week. I'd wager a guess it's holding a grudge or your pride. There is no overdramatizing at all. The drama started when you couldn't even join a TS.

Please do fill the rest of the red in.

What drama?. Yet again you feel the need to stir up something that isnt there. We just dont want anything to do with you. Thats our prerogative. We spoke to Farber about it and it was explained to us that not being on your TS channel was fine by them. Its their server mission and their rules. If you dont like it then so what?.

We are more than happy to use the Teamspeak that was allocated by Farber on the first week. Thankfully Im not on your Team for this so Ive no need to speak or listen to you any way.

Like you said, Bickering is ridiculous so lets just leave this out, ok?...

As I explained to Farber its because we didnt want to use your TS channel. Its no secret that we dont get along. Why on earth would we want to be associated with you in any way?. Like I said tho...we checked with the organisers and they said no probs. I can see that you are trying to suggest that we are not team players here. Fair enough if that is your intention. Im pretty sure tho that people can see through that.

I have yet to bicker. There's 2 pages in this thread simply because you couldnt join a ts. The drama belongs to you. Unlike you we don't care if we have to fly with syn or not. We are here to try and enjoy a big teamwork event.

This is why we can't have nice things :(

Organizers, maybe just make sure the briefing places Syndicate pilots on an airfield to their own, that way they can be on their own comms and not have to worry about coordinating ground movement.

If they require contacting other red pilots, the in game friendly only chat box will work. Simple phrases. Require assist. H14. 8k ft.

Solved.

Moving on!

Mind you, if the Reds want to make use of our entire teamspeak for this weekly event they are more than welcome. We cant however hold more than 35 people so both teams isnt an option for us.

The offer is there if you want it, guys

Sounds good bliss.


So has anyone worked out the correlation between the CTD and hardware/settings? Is there a quick and dirty fix?

I do not care which TS any particular Squadron or Staffel uses. In WW2 and other wars, do you two really think everyone on each side got along? Just bite the bullit, work together, communicate and win!

Be better men.


If you wanna talk about this anymore -

Don't involve this thread, campaign or my Staffel...

Hard to work together and communicate if half the team is on a different server (or if we keep getting booted).

I'd suggest all of Axis move to ATAG's server if Bliss is okay with that.

It's a credit to the campaign that this is probably not possible given the numbers involved. We were knocking on the door of 35 reds last time. Please don't take that the wrong way, it's a refusal on practical terms, not political.

I think Wolverine had an amicable solution if SYN are ok with it, that is that the organisers give SYN an airfield of your own to operate from and we communicate through game chat (although I am unsure how to keep that to red only in chat at the moment)
I suspect you will be handed a mission anyway, perhaps the organisers can make this happen (Hurricanes I believe), and I would just request that you let us know if you wish to change from that plan at all.

As for Spitfire support, I will pledge our No.64 squadron to fly Spitfires (organisers please see previous entry) and No.501 on Hurricanes. We will make up our numbers with our lonewolves if they don't mind.

See you on Sunday!

Yeah I'm sure that will be fine with us. I'll try and work with Farber/Rudelmann and get them setup with the privileges. The only thing I would suggest is to add some sub channels under the corresponding airfields. Basically exactly as Jg27's TS, but with more sections. There were around 7 to 8 different flight groups after everyone split up last time. So it would be harder com wise if all the channels had 8+ people in them.

As far as CTD's, I don't understand the cause. It seems I can play longer on my laptop than I can on my personal pc. Perhaps resolution has something to do with how often it happens?

(my laptop is much lesser machine than my desktop)

We can work with that no probs at all. If any others sign up for the campaign after this they can always be allocated to our field and also comms as another "wing". Whatever works for you all.

I can set up the channels, they're usually pretty busy on mission nights.

i very rarely (if ever) CTD when online, usually ATAG, all i can relate to is that after last patch i don't touch my .ini files. then again, i've always been among the luckiest ones with these random crash features...

1680x1050 / texture HIGH / trees MEDIUM/ everything else HIGH / AA 1x / EF OFF / SSAO OFF / VSYNC ON
___________
q6600 3.2
GTX570
4G DDR2 800
Win7 64

Could you please post up your config?

@Doggles - Thanks. I'll hook up with you on steam later on.

I'll be idle on steam most of the day. I think you have my email address already Bliss, send me an email if I don't reply on steam.

sure:

[BOB]
EpilepsyFilter=0

[window]
DepthBits =32
StencilBits=16
DrawIfNotFocused=0
SaveAspect=0
Render=D3D10_0
width=1680
height=1050
posLeft=0
posTop=0
ColourBits=32
FullScreen=1
ChangeScreenRes=1
Frequency=60
StereoMode=0

[NET]
speed=100000
localPort=27015
serverName=My Server
serverDescription=IL-2 Sturmovik: Cliffs of Dover
serverInfo1=
serverInfo2=
serverInfo3=
serverInfo4=
VAC=1
maxPlayers=255
socksEnable=0
socksHost=
socksPort=1080
socksUser=
socksPwd=
host=216.52.148.29
port=27016

[Console]
IP=20001
UseStartLog=1
WRAP=1
PAUSE=1
HISTORY=1024
HISTORYCMD=1024
PAGE=20
LOG=0
LOGTIME=0
LOAD=console.cmd
SAVE=console.cmd
LOGFILE=log.txt
LOGKEEP=0

[rts]
; 0 - not use, 1 - show cursor and not capture, 2 - not show cursor, and capture
mouseUse=2
; 0 - not use, 1 - use if hardware exist
joyUse=1
; 0 - not use, 1 - use if hardware exist
trackIRUse=1

[rts_mouse]
SensitivityX=1.0
SensitivityY=1.0
SensitivityZ=1.0
Invert=0
SwapButtons = 0

[rts_joystick]
FF=1

[core]
RandSeed = 0
TexQual=2
TexFlags.PolygonStipple=0
Shadows=1
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
LandShading=2
LandDetails=2
Sky=3
Forest=2
VisibilityDistance=3
LandGeom=2
DrawCollisions=1
Water=-1
Effects=2
EffFlags.Light=1
EffFlags.SpriteRender=0
Grass=3
CordEffect=1
UseFog=0
UseLandCube=1
UseLandConnectedObject=1
LinearObjectManager=1
Roads=1
Sun=1
Clouds=1
EffFlags.LightSpritesProj=1
ShadowMapSize=5
TexFlags.AsyncLoad=1
TexFlags.ShowTexture=0
SimpleMesh.SWTransform=0
SimpleMesh.QuadTreeClip=1
SimpleMesh.InstancingHW=1
EffFlags.LightContextSprites=1
CloudsFlags.Detailed=1
TexFlags.CreateHDR=1
Decals=2
EffFlags.SWLight=0
TexFlags.CockpitOnePass=0
MegaTexture=0
TexFlags.Reflection=0
RenderTargetQual=3
MSAA=1
MeshStatics=3
MeshStaticsDetail=2
SimpleMesh.QTNoCompose=0
MeshFirstLod=0
MeshShowLod=0
SpawnHumans=0
TexFlags.SSAO=0
TexFlags.VSync=1
TexFlags.FastTransparency=1

[sound]
SoundUse=1
DebugSound=0
SoundEngine=1
Speakers=1
Placement=0
SoundFlags.reversestereo=0
RadioFlags.Enabled=1
RadioEngine=2
MusicVolume=14
ObjectVolume=7
MusState.takeoff=1
MusState.inflight=1
MusState.crash=1
MusFlags.play=1
MasterVolume=14
Attenuation=7
SoundMode=0
SamplingRate=0
NumChannels=2
SoundExt.occlusions=1
SoundFlags.hardware=1
SoundFlags.streams=1
SoundFlags.duplex=1
SoundExt.acoustics=1
SoundExt.volumefx=1
SoundFlags.voicemgr=1
SoundFlags.static=1
VoiceVolume=8
Channels=1
SoundFlags.bugscorrect=0
SoundExt.extrender=0
SoundSetupId=8
ActivationLevel=0.02
Preemphasis=0.8
RadioLatency=0.5
AGC=1
PTTMode=1
RadioFlags.PTTMode=0
RadioFlags.PlayClicks=1
ActLevel=9
MicLevel=10
SoundFlags.UseRadioChatter=0
SoundFlags.AutoActivation=0
SoundFlags.forceEAX1=0
speakers=3
vgMaster=2
vgVoice=15
vgMusic=15

[game]
mapPadX=0.6023809
mapPadY=0

so it's pretty much unttouched settings; as you can see, i have Render=D3D10_0 just at the beggining, i once set it to Render=D3D10_1 and all hell broke loose; reseted to 0 default; also my install is from scratch after latest patch

Interesting. Alas it was already so.

I strongly believe this is a fault concerning ATI radeon cards and the game. I think Nvidea get a better time of it.

Growing excited for the next mission! Not even Skyrim will keep me from the skies on Sunday.

Briefs might not be out till saturday. Airfields will be the same unless anyone has any serious objects? Was there any serious spawn issues last time?

I don't recall any actual spawn point issues where I was at Manston which was a bit busy but ok, while Hawkinge sounded like chaos. Perhaps disperse one or two Hawkinge units to say Lympne or Littlestone? Even perhaps move a unit from Manston to nearby Ramsgate?

EDIT: btw I may have a 100Mb up/down TS3 server available for Reds on Saturday thanks to a friend - will get back asap.

Another TS available for Sunday
 

Its not up yet but we have obtained the use of a TS3 server on a 100Mb up/down connection if it would solve the problem of who will/won't use which TS3. If that can get us all together on TS it would be very useful.

If some are still not willing to share TS with some others, well, just let me know I'm wasting my time.

I'm going to get the guys to check here first in case its not wanted before setting it up.

This is the IP
teamspeak.ukatc.com
You can also connect directly to the IP address: 77.251.29.224

I've asked for it to mirror the channels structure on the ATAG server under
5./JG27 and 9./ZG26 Campaign

What!? I dont understand, you have found neutral ground for red or all Squads?

Yes, it is intended to be neutral ground for all the Reds and Blues. Ideally all units need to be on the same TS but there was some history which prevented some units from doing that.

It is a TS server provided by the friend of one of our Squad members. This person does not even fly in CoD.

It will be configured for both Blues and Reds in the same way as the ATAG server.

However they will check here first to see if it is still wanted. Some expressed a preference not to use the ATAG server or use their own. If they still don't want to join a common TS there's no point in offering it.

So, would anyone not willing to use a common TS please sound off asap so we don't waste their time.

================================================== ==========
Sign Up - individuals looking for Squadrons/Staffeln:

Your Call Sign: PorkChop
Red/Blue: Blue
Bomber/Fighter/Destroyer/STUKA: Figther / fighter
Preferred Aircraft: 109

================================================== ==========

yes klem, it is fine, for the record, there is no history between our squad and any other.

Have the briefs been posted?

================================================== ==========
Sign Up - individuals looking for Squadrons/Staffeln:

Your Call Sign: UFO_113
Red/Blue: Red
Bomber/Fighter/Destroyer/STUKA: Figther / fighter
Preferred Aircraft: Spit Ia

================================================== ==========

I would like to offer myself up as cannon-fodder for the campaign, but can't figure out how to do it.

Bases:

RED:

504RAF Hendon A16
Hurricanes

Any RAF Hornchurch C16
Spits, Blenheim IV, Hurricanes.

69GIAP


Easchchurch F15
Spitfires

ATAG


West malling D14
Spits, Hurricanes.

Syndicate


Hawkinge G13
Hurricanes

104th


Scramble! Large formations of enemy aircraft are inbound! Fighter sweep over South East England.

Any Squadrons unassigned use one of the bases where no other squad is listed. As always use commone sense, if there are bad probems just spawn somewhere else.



Blue, Homuth will handle your briefs - enquire with him if you dont have briefs very soon.

I probably should be red cannon-fodder as most of my experience has been flying Spits. That way it will, hopefully, look a bit more convincing (and be slightly more satisfying for the shooters) when I'm blown out of the sky... I'll give ts a try tomorrow. Thanks!

================================================== ==========

Call Sign: OlyMurph
Red/Blue: Red
Bomber/Fighter/Destroyer/STUKA: Fighter / fighter
Preferred Aircraft: Spit Ia

================================================== ==========

I'm gonna try and jump on this ship!
================================================== ==========

Your Call Sign: l3ullDozer
Red/Blue:Any
Bomber/Fighter/Destroyer/STUKA: Fighter/Destroyer
Preferred Aircraft: 110/spit/hurri

================================================== ==========

EDITED:-

I believe

504RAF Hendon A16
Hurricanes

Any RAF Hornchurch C16
Spits, Blenheim IV, Hurricanes.

69GIAP

Should read:

504RAF Hendon A16
Hurricanes

Any RAF

Hornchurch C16
Spits, Blenheim IV, Hurricanes.

69GIAP

If 69GIAP are taking Spitfires 56RAF will take Hornchurch Hurricanes otherwise we'll take the Hendon Hurricanes (but did you mean 501RAF for Hendon?).
We are open to spare pilots willing to fly as wingman to one of ours.

EDIT #2: Or if SYN are flying Spits we could take the West Malling Hurris.

I think your getting mixed up, or I dont understand what your asking.

:confused:

EDIT1

504RAF Hendon A16
Hurricanes

UNASSIGNED



Yes.

OK, 56RAF will take the Hendon Hurricanes.

I was confused because Hendon was the only base you put a Squadron number in front of, so I wondered if you were assigning it to a unit and then I wondered if you meant to type 501RAF not 504RAF. (56RAF and 501RAF both took part in the first two rounds)

Anyway, I guess 501RAF will take West Malling but we can sort it out tonight.

Rudelmann made this mission and didnt put in the unit names.... The previous two and the last one for next week were made by me. I suppose he wanted to give you the freedom of using your own units skins? I might leave the unit names on the bases in future but place squadron as any... Maybe.

What time will this start?

I've been away all weekend, but I'm here now, and both No.501 and No.64 will be flying. If we're from 1 base with CSP Spits and Hurricanes then fine.

We hope to send you our JG26 squadron too (ahem,....2 pilots....has good leaders but needs more crew....)

Independent TS3 server for JG27 campaign
 

Its up if you want to use it

teamspeak.ukatc.com

People can also connect directly to the IP address: 77.251.29.22

EDIT: HOLD THAT!! - not enough time to organise so we're on the ATAG TS3

Hopefully next week we can all be together on the independent server.

Bloody TIR Pro Clip thingie broke just before the mission so couldn't fly :(

Great stuff today gents..

Got into a scruff near Ramsgate where a 5 minute yoyo ensued. Just as I was about to get a bead on the chasing 109, I get pked from the 110 behind me. I should've known ;)

Excellent teamwork and excellent mission.

Thanks fellas..

Managed to get out to Ramsgate and engage. Shot up the tailgunner in a 110 before turning back to re-engage and my game crashed. Sigh.

The concept for this is great, but they absolutely NEED to fix the crashes. I was hoping it could be worked around since playing online has so far been great, but in a 'real' campaign with 1 chance to fly, it's frustrating and a half :/

I hear you, they really need to FIX THIS NOW!

We lost two to CTD and myself over Manston. Wonder if that spit made it home

Unfortunately, along with some of my comrades, I didn't see any action. After forming up over RAF Kenley a number of CTD's occurred. Whilst I understand and agree that we want to have a 'one life' policy I don't think COD is ready for it given the stability right now. Is there an alternative coding method we could implement perhaps? eg.

if(pilot == damaged){
if(pilot==dead)
{
stop refly for that pilot
}}

Flying home to reload in an undamaged aircraft should be allowed anyway

"server authentication failure" even with reboots, loggoffs and steam restarts... oh well

guess my third attempt next week will do?

Krupi and Karaya both got the .exe crash, I myself flew the whole mission at 300 kph and 8.30 PP in an E4 after my auto PP got stuck and I couldn't remember the button for manual...
Bombed a ship (missed) and escorted some dorniers home to crashland at base after getting flak damaged.
I agree it would be a good idea to get rid of the respawn ban for next weeks mission, CoD just isn't stable enough for it just now.