Xxx

Could the problem be in the usage of our CPU Cores? (Just speculating) In Normandy (Deferred Shading on) no ground units engaged, or moving on the map, produces nice smooth flight. Add some ground units and I see stutters. Are the computations for the ground units (threaded commands) getting baulked in the execution of the code? On the other hand, if I just have air to air action, there doesn't seem to be any stutter. Are the air to air threads better optimised? I know it's much more complicated than this! My GTX 980 is always maxed out in 2.1. 100% GPU load and 100% memory use. I am even thinking of upgrading to a 1080 with 8 Gb? If it's a GPU bottleneck? My suspicion is on the threads executed on one core. But here we need a programmer to comment. I also wonder why NTTR is much smoother than Normandy? I hope when all the maps get amalgamated, the stutters are a thing of the past? Regards.

Yes this always happens in the Mirage! I like to think this stops me from "cheating", since in a real world Mirage I couldn't hit "active pause", everything has to be done real time and in good time. It kind of focusses the attention and enhances the adrenaline factor, but that's probably just me? :smilewink: Regards David

I agree totally! I think there are still Gamma problems with 2.1.1, especially with Deferred Shading on. Recent videos of the F18 however, depict a HUD that looks remarkably like the real world one, i.e. it's got a blue cast, which is the UV filter in real life! The HUD appears readable in the videos, but again is that with Deferred Shading on or off? All the HUDs require this treatment! A UV filter so we can see the HUD against the glare of the sky, otherwise what's the point of a HUD and Deferred Shading for that matter? Cheers.

I just updated to 2.1.1.8422. Before the update I got 40-70 FPS in Normandy. Now its a stutter fest! I see 10 FPS, with extreme stuttering going on? This is with the exact same mission I made as before. Granted the HUD is readable now after the update, trouble is its unplayable in Normandy on 2.1.1.8244 Sorry, but some thing went seriously wrong here? Regards David

The Deferred Shading seems to alter some effects for me? System seems to be working overtime to render the graphics? I am curious to know, can you target (Lock) a WW2 Tank, say a Cromwell/Sherman with the Viker missiles? I can lock on, but pressing "release weapons" (RAlt+Shift) assigned to my regular joystick button, has no effect! I can not fire any Viker missiles at tanks in Normandy? Rockets work Ok and the Cannon is OK, just no laser guided missiles? Everything still works in 1.5 though? Cheers

Agreed. I can get a couple of Cromwells to move to "on road" waypoints, off road movement doesn't work for me. My biggest worry is the "stutter" when a simple mission (4 tanks and six troopers) are engaged, with some explosions triggered as objectives are reached and armed houses destroyed. The Normandy map is beautiful to fly over with no "sand box" action taking place. Put some war action in and it's full of stutters. I am thankful I did not buy an Oculus Rift, no chance of flight with those stutters! Also it occurs to me that the map is so good at ground level, colidable trees, rolling topography and detail in the lovely buildings, it seems more suited for a tank "sand box" simulation rather than a flight sim. ED must have worked hard to create this map, but it appears not to be optimised for battle missions? Re creation of D-Day and post D-Day battles appears to be unfeasable without some optimisation of the game engine. At the moment it's only use is to fly about admiring the scenery. I can do this in P3d! I am just about ok with NTTR 2.1.1, In the desert and 1.5 remains the best map for combat. I worry that if ED "converts" 1.5 into a 2.1.1 engine, I will loose functionality of the sim? Best regards David

The frame rate of the Black Shark, when played with a simple mission in Normandy, is so low its unplayable. I see 20 FPS maximum, however there is a constant stutter which makes flight unpleasant? Could this be incompatibility with the 2.1.1 graphics engine, with Deferred Shading on? Just as well there were no Ka-50's in WW2! Thank goodness I still have 1.5 installed. Best Regards David

I have more problems with the mission planner in Normandy. I am trying to create a D_Day scenario. Unfortunately I have more serious issues. I have Sherman's, Sherman Firefly and Cromwells attempting to move from the beach inland. Trouble is, they don't move at all! Even placing them off the beach on to level ground makes no difference, they just sit there and open fire on any targets in range, without moving? The WW2 American infantry move ok. The German Panther Tanks do move, but not the allied tanks. Then the German Troops I place on the map don't spawn! No matter how many/few, or where I place them they don't spawn in the game? Almost like they aren't modelled? I believe this is a known issue? It's difficult to create any plausible D-Day scenarios with these limitations. We need to be able to display many hundreds of troops and tanks, not to mention actual landing craft. I mean the small beach landing craft, not the LST's which don't land on the beach. At the moment all I can do is create micro combat scenarios on small sections of the map? Happily, it's a "beta" map so hopefully ED will sort it out. When I do get several units in contact. The frame rate slows down to a stutter. The explosions are nicely modelled, but I get a frame freeze as the explosions are rendered? At the moment all Normandy is good for is sightseeing over the blank canvas(sand box), which admittedly is lovely! However a full scale D-Day mission scenario/Campaign seems impossible at the moment. Best regards David

Hi, thanks for the reply. I have more problems with the mission planner in Normandy. I am trying to create a similar mission to you. Unfortunately I have more serious issues. I have Sherman's, Sherman Firefly and Cromwells attempting to move from the beach inland. Trouble is, they don't move at all! Even placing them off the beach on to level ground makes no difference, they just sit there and open fire on any targets in range, without moving? The WW2 American infantry move ok. The German Panther Tanks do move, but not the allied tanks. Then the German Troops I place on the map don't spawn! No matter how many/few, or where I place them they don't spawn in the game? Almost like they aren't modelled? It's difficult to create any plausible D-Day scenarios with these limitations. We need to be able to display many hundreds of troops and tanks, not to mention actual landing craft. I mean the small beach landing craft, not the LST's which don't land on the beach. At the moment all I can do is create micro combat scenarios on small sections of the map? Happily, it's a "beta" map so hopefully ED will sort it out. When I do get several units in contact. The frame rate slows down to a stutter. The explosions are nicely modelled, but I get a frame freeze as the explosions are rendered? At the moment all Normandy is good for is sightseeing over the blank canvas(sand box), which admittedly is lovely!:music_whistling: Best regards David

I recently added beach obstacles and some bunkers to the Normandy beaches. Mainly around Omaha beach, but extending along the landing areas. My aim was to create a D Day scenario mission. Took off in the Messerschmitt and although my frame rate counter showed 50-70, I got horrendous stutters. Every 1 second there was a stutter, as if the graphics engine was struggling to load the beach obstacles? Mission was unplayable! Can anyone confirm that Normandy 2.1.1, with Deferred Shading on, does not like the beach obstacles? Obstacles were varied, submersible poles and tank traps. About 75 obstacles in total. Stutters were apparent at take off, well away from the beaches and remained during the flight? A test without any beach obstacles revealed no stutters whatsoever! EDIT. It appears its the Landing craft and the Destroyer escorts that's causing the game to stutter.! Removing all the landing craft restores smooth flight? Now just need a way to have landing craft without stutters? Regards David

Absolutely! Start small and build up! Sometimes missions never play the same twice. Which is great really, I suppose? Also downloading other folks missions and seeing how they did it, is really helpful. Have a look at my latest one on User Files. Deep Strike for Viggen and one for the Mirage! Best regards.

Suddenly seeing low frame rate (3-12) at the start of a mission with multiple groups of B-17's attacking my airfield? B-17's are at 25,000'. Could also be due to Flack placements, (24 assorted Flack positions around airfield, Carpiquet) but the frame rate is now and noticeably jerky? Also had 3 CTD's out of 5 missions? The Normandy terrain is beautiful though, as is the sun glinting off my 109's canopy in external view! Lovely! Glad the Caucuses map is still fast and stable! Regards David

Everything you need is in the mission editor. Have a play with the mission editor. Just open it up click on the aircraft symbol (top left), select a B_17, from right side drop down menu, click on the map and place it at any altitude. Then put your aircraft 109/190 on the map in the same way. You can begin with both airborne and with your aircraft with a hight advantage. Save it and click on fly (green bird symbol on left side menu). Make sure your aircraft is "you"...set as "player". (Drop down menu right side) Then when you click on fly you will start in your 109! You can then build up missions where you have many aircraft aloft. But the more you have, the slower the game will run! I am sure there are tutorials around, but to be honest, it's better to have a play around with a couple of aircraft to start with. Once you get the basics, you can quickly build missions. Today I took off, planning to intercept my 20+ B-17 formation, escorted by Mustangs. By the time I got to 20,000', they Bombers had dropped their ordinance and headed for home. I managed an entire intercept mission, without firing a single shot! However the flying was nice!:megalol: If you do manage to get into range of the Fort. Watch out for the gunners, they will scyth you in two! Of course you could cheat and both of you be on the same side...(also set from menu) that way the Fort won't shoot back! Cheers

Check! The 30mm has the clout for sure, but slow rate of fire and like you say, poor range and not much ammo! Those 151 cannon's would be nice in the wings? The cockpit switch is there ready for use, so come on ED let's have the wing cannons. The 190 is superior in this department! Some great advice from all the guys here. Speed, check. Altitude,check. Dive, shoot, scoot:thumbup: Normandy is turning out to be a real learning curve. One thing that appears more apparent, is the planning and patience required, just to execute a single pass on a B-17. The slow climb to the bombers altitude, takes an age and there are the obvious pitfalls of our DCS visibility limitation? Then you have to fly well, avoiding engine over stresses!:music_whistling: As a bit of light relief, I took 4 Mig 21's up in place of the 109's.....With the speed of a jet, those tactics become much easier. :smilewink: Now, can we have the Me 262.....please!:D Cheers!

Anyone tried attacking the B-17's in Normandy 2.1.1? I placed four box formations (16 aircraft) at 20,000' and tried an intercept with 4 109's.....:pilotfly: The newly activated turret gunners cut me to pieces! I managed a couple of downed B-17's before my 109 exploded! A real challenge now to shoot these guys. The A.I. gunners are as good as the A.I. pilots...:smilewink: Possibly the only tactic would be a head on shooting pass.....just like they did in WW2:D Thanks ED!

Hi, I sorted it out today! It's a key bind in controls, RAlt+#. That's on my keyboard. It could be RAlt+\ on yours? RAlt+# is the "push to talk". That opens the radio menu for our Wingmen, then it's select from that as usual. It's not really a push to talk, it's more an alternative radio menu command! Hope that helps.

Thanks guys. I will have another try. I could have sworn it worked with just the comms menu before, that's \ in the assignments or # on my keyboard? Like you say Art, there's nothing to "push" here! Regards David

After take off and gear up, the radio menu can not be accessed with # or \. This is in Normandy, 2.1.1 Any one else see this? Everything was fine in 2.1 before the latest patch. Radio is ok in every other module in Normandy? Cheers

That sums up the current state of play very nicely!:thumbup: I would add, that if you read the records of post D-Day air combat ( look at Bunyap's You Tube channel, he has done historical videos of the day to day life in a Spitfire squadron), you see that large dogfight's, never occurred. Those were the Battle of Britain days. Most encounters were very brief dogfight's, with the Luftwaffe aircraft able to disengage at will and scoot for their forward bases. The 109/190 had greater speed than the Spit/Pony. If we had the Thunderbolt or Typhoon/Tempest we may be able to catch them? If you fly for the Luftwaffe, you can re create interception of the Flying Forts. I believe ED have activated the B-17 turret gunners, although I have not tested that yet! Cheers.

Here is a Deep Strike mission for the Mirage. I evolved it from the Viggen Deep Strike mission. Flown in 2.1.1, Nevada. Regards David

An evolved mission for the Mirage 2000C. Flown in 2.1.1 Regards David

I keep my fingers crossed for a fix. In the meantime, after fiddling all day with lua settings and getting nowhere fast, I made a discovery.:D Turn up the cockpit flood lighting (white only) to maximum. Then pull down your helmet visor! This permits you to see the HUD symbology against a bright Nevada sky. The other thing I noticed, was if you zoom in to the HUD, right up to maximum zoom, the HUD symbols become clear against the glare from the sky. Zoom back out and they stay visible for a short time before disappearing? There must be a better solution, but in the meantime, the white cockpit flood lights permit the HUD symbols to be read. At dusk/night, the HUD has that pale greenish mask that looks odd? There is no key bind for white cockpit lighting, only red flood lights. Red has no effect upon the HUD. Hope that helps, while we wait!:smilewink: Regards David

I agree the Mig 21 is spot on in 1.5. It's a superb sim.:thumbup: However, someone has taken the time to code RSBN channels into all the air strips in Normandy! So we can fly the Mig 21 around Normandy, with RSBN navigation.:D Once the 2.1 Shading issues are sorted out, perhaps the Mig will be adapted to fit the new engine? It seems like the graphics engine is leading the development process and the modules are in a state of catch-up? For now, I can fly it in Normandy pretty much like 1.5. But I don't have VR. Cheers.

Is there a way to replace this white mask with a mask that would darken the HUD slightly? The real world F18 has an ultra Violet filter which, by filtering out UV, appears to darken the HUD. This results in the HUD symbology being readable against a bright sky. The more I see of Deferred Shading, the more I like it, however the HUD issue is spoiling it completely, IMO. Cheers.

With Deferred Shading on in 2.1.1 and Gamma slider at 1.0, the HUD glass is clear, on my monitor. The only problem is with a bright sky, in NTTR, the HUD symbology is hard to read, against the sky. The A10 did have a night/day HUD function that helped with that module. Is there a way I can alter the HUD colour in the Mirage? I appreciate the real jet doesn't seem to have a HUD colour feature, but it would be nice to make the symbology darker, or give it some contrast? Similar results show in the Viggen, however that symbology is much easier to read due to the "poles" being mostly below the horizon.