1st Multisquad Campaign Battle of Britain

[SYN_Per]

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!

[klem]

Originally Posted by Untamo

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?

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.

[Bullit]

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

[klem]

Originally Posted by Bullit

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

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

[Untamo]

Originally Posted by klem

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 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.

[jojovtx]

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.

[jojovtx]

Originally Posted by jojovtx

Those of you who have issues with the game crashing try something with me.

I used to have that issue. Not really until this last patch at least. However, I went back to some lower settings and I was the only one of my squad to not get the launcher.exe failure tonight. I have far from a epic rig as you can see my stats below.

Settings:
1680x1050
full screen: on
model detail: med
building detail: med
land detail: low
forest: off
visual effects: med
texture quality: med
AA: off
Epilepsy: off
SSAO: off
vsync: off
damage decals: med
building amount: unlimited
land shading: low
grass: off
shadows: off and I really hated doing that!
roads: on


In my nvidia control panel:

Anisotropic: 8x
AA: 4x
triple buffering: on
vsync: force on

Flew for little more than 1.5 hours and had no launcher.exe error. Each patch I was able to include and up the settings little by little. With this last patch I essentially went back to me earliest settings and I have apparently beat the launcher.exe problem.

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

[SYN_Jed]

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

[Osprey]

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~

[SYN_Jed]

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.