Holbeach

I wonder if they have flattend RAF Deanland runway bump, bug reported 18 months ago. ..

Headcorn, C/S Headcorn, as we know it today, formerly known as Headcorn Aerodrome before the war. Changed to RAF Lashenden during the war, the Headcorn name now given to the ALG NE of Headcorn. I flew into this field with Rollason Condors, during the 90's, when it was called, "Lashendon (Headcorn)" C/S Lashendon Radio, noted in Pooleys, but we always called it Headcorn locally. The old RAF Headcorn perimeter, can still be seen on Google maps. On todays Skyvector maps, Headcorn is named "Lashenden Headcorn", C/S Headcorn.. In Normandy 2, it should be called, RAF Lashenden. ..

I got the inspiration from the RAF's fear, after Falklands war, of an attack by Hercules, landing troops to attack Stanley infrastructure. 2 Hercs approach from the West. 4 F1 approach from West and South. Target 3 Phantoms on the ground and a Herc parked. A Rapier site with 4 launchers and 2 directors will destroy all of these aircraft. To prevent this, a 2 Viggen fllght with Mavericks, will need to destroy them first. My job with the only servicable Phantom, is to destroy 2 bears with cruise missiles and save the incoming Carrier fleet. OR. Shoot the Viggens and save the Rapier site. OR. Shoot'em all. Could also be used on Kola. Rack the sounds up. ..

4 MB339 attack 2 Chinooks parked at San Carlos, with guns and rockets. ..

2 Argentine Navy Viggen, Maverick attack on Rapier site at Stanley, to prepare way for Mirage strike on parked Phantoms.. ..

6 F1 posing for Argentina, attacking Stanley parked jets. 2 Top cover. 4 Strike. ..

Thanks, but that's not for me. I don't mess with inner workings, that's what I expect the Devs to do. ..

Yes, I tried all settings adjustment from High,, using a simplified version of Falkland AA mission right from the start, running repeat missions for about a week with no luck. Then I used preset Medium and bugger me the 900' ball drop went away. I then increased all values one by one and it was still OK, until I put 'Unit Texture' from medium to high and my ball drop came back. Back to medium and it went away. Increased all other values to what you see in the screenshot and I've been clean for 20 days, with 100% success rate. Unfortunately it doesn't seem to work for anyone else. ..

Don't just turn textures down, turn default medium or low on, that's what I did and it immediately cured the problem. Unfortunately it doesn't seem to work for anyone else. It looks horrible, but if it works then you can start increasing stuff until it fails again. I'm still 100% clean using this mission every day. Settings. Vsync fast. Max frames. 13 Yo pc. Falkland AA (3) mission WIP. Start Stanley F4 54fps, Priority 2 Bears. They will destroy your fleet. 6 MB 339 will destroy Chinooks at San Carlos and Goose green. 2 x 2 F1 will destroy aircraft parked at Stanley. 2 Viggen will destroy Rapier site at Stanley. Damage limitation is up to you. .. Falkland AA (3).miz

"Package for Stanley". ..

Correct, but now with Unit Textures reduced to Medium, that bug never occurs and I can't tell the difference in quality. Here is my AA practice mission as it stands and used this morning. Shoot the Bears and with the remaining ammo, just run amock. Land at Stanley Frames on the runway are 54. . Falkland AA .miz

Here's a reminder of what a 50 frame ball drop looks like. 70 down to 20 in an instant. ..

For me it would have to be Windsor Davies. "We're drifting off, lovely boy". "Oh dear, what a shame, never mind". ..r

It's easy for me to do. All setting on Max and it sometimes occures. Unit Texture to Medium and it NEVER occurs, no matter how much I torture it. ..

If you were to take whatever frame rate you are experiencing and as you descend through 900' AGL anywhere on the map, it dropped to 20fps instantly and stayed there until you climb through 900' AGL, where your frame rate recovers, then that is what some people are experiencing, not just a poor frame rate per se. To make it worse, it doesn't happen all the time. ..

It's under 'VR performance' from 2 years ago, (no wonder I couldn't find it) and the reply from Spectre inferred that you should buy a bigger GPU to fix it. The one that Biggus has just bumped, has no reply at all. So from over 2 years ago, it still hasn't been fixed. ..

There is no bug report on this matter and no comeback from the Devs, so it's likely to remain unfixed and I don't intend to sit on my hands waiting for something to happen. A warm cloth is better than 20 fps and if it takes a reduction to get my fav map moving, then that's what I'll do to carry on enjoying it. Apart from that bug and the slow rebuilding of Terrain Textures following F10, I don't find its performance at all bad. ..

Exploring the Look down and Look up capabilities of the F4E and AIM 7M Semi active Radar missile, (same as RAF Sky Flash). Target is a Bear, flying at 26000'. Ist run is level launch from 43000'. 2nd run is level launch from 8000'. 3rd run is from low level and needed some Loft help to get a Radar lock. The mission has 16 target aircraft and is based around, 1982 to 1985, with FGR2 Phantoms from RAF Stanley, carrying 2 tanks, 4 SkyFlash and 4 AIM 9L Sidewinder, against F1 Mirage, MB339, C130 troop transport, and Bear recce aircraft attacking Stanley, where they meet Rapier and Seacat missile defences.. ..

2 weeks now and after about half dozen F4 sorties every day, I consider myself 100% 'Bug Free' or to be more precise, 'free of bug' during that time. Dropping Unit Texture from High to Medium is all it took. (No visible difference I can detect). Removing shadows didn't work. Terrain Texture to Low didn't work. These just made everything look horrible. Nothing I have tried will make the 900' drop reappear, I'm glad to say. ..

Video is my memory aid for setting up a shoot on 2 Bears. Set pylons for tanks only for jettison, not AA missiles + gun. Master Arm on. CW on (up). Pinky to Radar. Jester V short, track. V 2 return to search. V long, lock target. Lights on, SHOOT. Might be useful to someone. .... ..

I increased the Frigates to 13, (all live), and the Rapiers to 11 groups, (121 vehicles). Runway start was 32fps. VRAM and RAM both 11. Shoot Bear, back down to 200'. No drop bug, then repeat with another Bear, then watch the Rapier/Seacat create carnage. When all 24 planes were destroyed, frames were about 55 down to ground level. ..

So today I raised the attackers to 24, 16 F1, 6 MB339 and 2 Bears. Defenders to 3 F4, 2 Frigates, Rapier and 4 bofors. So there is a choice of F4 runway start, (54 fps), F4 air start, F1 bombers or fighters air start. Take out the 2 Bears, so you have 6 missiles left to make a choice of target. I've removed bomb drops because they circle and provide easy targets. Descent through the 900' layer fps remains at 75fps. To me it all points to, more pc power and the bug goes away. Do the 2d thing, because it's obviously no fun for you with goggles in this map and it's a great map. ..

I still pucker up, everytime I pass through the 900' layer, but so far I've had no more frame drop. Vram (ASUS rog strix 2080Ti) and RAM 16gb ( are about the same at 9.5 each). I can only state what is working for me and I can now start on building my, post '82 Falklamds, AA mission. ..

No ball drop. Ball drop. Spot the difference.

Here's my story so far. 3 days of repeat missions with F4. Using Falkland AA mission and previously posted settings. No 900' ball drop on return from high altitude after shooting 2 Bears at 26000'. Added more air sea and land units. Frame drop, but no ball drop. Added SSAO and SSLR. Total frame drop 62 to 52 on Stanley runway. Still OK. No drop. Raised, Unit Texture, from Medium to High, (which brings it back to my original overall High settings) and I get a 75 to 20 frame drop at 900'. Go back to Medium from High and no drop occurs. Repeat tested with F4 and F1. I can only conclude that something happens at 900' that affects unit texture and sends the GPU to 100% and overload and it cannot produce more than 20 fps. With my GTX 1070 it was 17 fps. My PC is old, but it works very well with DCS and I don't intend to throw upgrade money at a problem that shouldn't exist. ..