DD_Fenrir

Biggin Hill was a sector station - this meant it had an Ops Room (the big map table where they pushed the wooden blocks indicating air raids and friendly air units around) and was the primary control authority for the squadrons based at the stations within within it's sector, these being West Malling and Lympne. Biggin was on the frontline as a Fighter Airfield right up until early 1944, with many notable fighter squadrons rotating through it from 1939 till the months before D-Day. The squadrons based there claimed 1000+ enemy aircraft destroyed. Manston was one of the secondary fields (no Ops Room) in the Hornchurch sector. Used by Fighter Command during the Battle of Britain it was attacked so frequently and so heavily that units were withdrawn to bases inland, as it being so close to the sea the fighters based there struggled to get to height before the enemy raids arrived, meaning the squadrons often got bounced, or missed the interception altogether. As the air war became less defensive, Manston started seeing lots of units rotate through, particularly on a temporary basis as fighter squadrons might forward deploy from the bases inland to extend their range somewhat in order to be able to escort bombers to targets in Belgium and Holland. Later, it became a regular home to Hawker Typhoon squadrons and during the V-1 campaign the first squadrons of Gloster Meteors were based there.

Surprise surprise; XB telling people how they should be playing/building their game. Tell me, when are you gonna realise you have no authority as a gatekeeper in this community?

Valves. No solid state transistors in WW2. Any electronics of that period relies on thermionic valve (aka tube) technology, and these take time from power on to warm the filament up to operating temperature.

Frankly it’s semantics - RPM is governed by the pitch of the blades whether it’s controlled automatically or manually.

RPM and fuel efficiency are directly proportional. More RPM = more fuel usage. More RPM also = greater stress on the engine. Anytime you wish to save gas, or the motor reduce RPM. Buut remember that there are limits to how far open the throttle can be at lower RPMs; go too low with the RPM and don't reduce your throttle with it and you'll suffer from detonation or 'knock' which will also kill the motor.

I suspect a mix up in terminology. As a rule: 1. ETO = European Theatre of Operations = Channel and Northwest Europe 2. MTO = Mediterranean Theatre of Operations = North Africa, Italy, Greece and Southern France 3. PTO = Pacific Theatre of Operations = Pacific Islands, New Guinea, New Britain, Austrilasia, Phillipines, Okinanwa 4. CBI = China, Burma & India = the aforementioned + SE Asia 5. EF = Eastern Front = Third Reich vs. Soviet Great Patriotic War actions across Eastern Europe I think Silver Dragon is including EF under ETO, which the majority of us Westerners do not.

Try this: https://www.quercusbooks.co.uk/titles/robert-lyman/the-jail-busters/9781784290177/ I have a few books that cover the subject, best balanced by far. There is also: https://www.amazon.co.uk/Walls-Came-Tumbling-Down/dp/0285625195 But the veracity of this is made deeply questionable by statement about the Mosquito's dogfighting their way out of the target with the Navigators steering and firing the guns... 'Nuff said. It also reads like a boys own adventure novel, with the story telling suspiciously florid at points where the details of conversations and chance meetings seem too detailed or forced, as if they have been embillished or even fabricated. There's also this: https://servicecomm.co.uk/catalogue.php?product=874&productID=the-amiens-raid-secrets-revealed However, despite some great research on the RAF involvement and a creditable analysis and follow-on conjecture of the bombing (which aircraft dropped what and where the bombs ended up), he very much has an axe to grind against the British Intelligence services and this leads him to some rather spurious conclusions based on compounded suppositions.

Be wary of making that assumption; different engine can result in different mounting and that can result in CoG shift which can impact handling significantly. It can also result in a different thrust line, plus distance of the prop from the CoG altering the way gyroscopic forces act in relation to it. Also the way the airflow - including the propwash - interacts with the nose can have unpredictable effects with airflow down the fuselage, over the wing roots and how it eventually interacts with the tail, horizontal and vertical. Sometimes changing an engine type on an aircraft has negligible effect; at other times handling characteristics have even been improved. But sometimes they've been considerably affected for the worse.

But you do. You don’t just make a sminky 3D model, texture wrap it in some hi-res bump mapped 4k bitmaps and have a fully functional module. The systems modelling is all lua code, lines and lines of syntax and ones & zeros, most of which works, some of it doesn’t and some of it which might work but we don’t know yet cos we’re trying something we’ve never done before. Now, if you think that a developer are going to start posting screenshots of their programming just to satisfy impatient petulant and over-entitled potential customers, I think you need to wake up from your little “I want I want I want” fever dream and smell the coffee.

Meh: a WW2 map with zero appropriate aircraft and valid for one day out of a war that lasted 2,194. Philippines, Iwo Jima, Okinawa, all much better candidates for the aircraft we are soon to get with far more scope for campaigning.

Not official modules; I’m talking about unofficial aircraft or assets that are made by community members and available for free as modifications to the game. Sometimes an individual mod can cause game functionality to break in specific cases; other times it can be down to a specific combination of two or more of these mods as they rarely get tested together. It could explain why you alone seem to be suffering this bug, which is why we ask.

Mods?

Normandy - the Spitfire, P-47D-30 (early), Mossie, Fw 190A-8 and P-51D are all prototypical but the USAAF birds don’t really represent the most common variants, with the P-51D-25 having capabilities and equipment features beyond those that the D-5 variants that were entering service at the time of invasion should not really have (HVAR capability, tail warning radar, K-14 gunsight) though performance wise they’d be appropriate. Ideally we’d have P-51B and razorback P-47Ds. A Bf 109G-6/14 would help, along with a Typhoon, Mitchell III, a P-38J and B-26D. Ground units wise, the basics are mostly covered (except for shipping) but in reality there were hundreds of models and sub-models of trucks, tanks and artillery that could feature.

The sheer lunacy of reading this statement in a Combat Flight Sim forum... ! Love this community

Do you have head tracking software enabled - I get this sometimes when my TIR is running and I forget to switch it off when moving to the Rift-S.

To your first question, yes, in multiplayer you can have two breathers in one airframe, one pilot, one navigator. To your second point regarding GEE, no the Mosquito in DCS is not equipped with the GEE receivers, primarily because it would be useless ballast without the radio net existing in the map to provide the signals for the GEE set to process and currently these are not present on the two ETO maps and ED have not indicated that there are any plans to add this functionality.

He's called a Navigator; clues in the name... Try flying a 450 mile route Nap of the Earth at 250mph with multiple heading changes to mitigate the chance of interception and avoiding areas of known heavy flak concentrations, whilst adjusting for unforecast changes to wind strength and direction and recalculating the airspeed required to be over the target at the time you were briefed. Try making a GEE fix whilst you're dodging high tension wires, trees and industrial chimneys.... I'm serious, try it in DCS, I guarantee you'll have a very genuine and sudden appreciation for what a Navigator actually does in the FB.VI. No Icon On F10 map in real life.

**BUMP**

That's a 1942 IJN plane set. You'd really need and F4F as opponents for them. A6M2 was replaced in service by the A6M3 Models 32 and 22 before F6F and F4U arrive. D3A2 was beginning to be phased out of service by the time Hellcats and Corsairs enter the picture, in favour of the D4Y "Judy". Even the B5N2 whilst still quite prevalent was starting to be replaced by The B6N1/2.

There is real life precedence for this; prior to the mid-late 1980's the use of AIM-54s was reserved for the Fleet Defence mission, ergo any Tomcat going feet dry running OCA or covering the strikers in the majority of the Tomcat's Cold War career would have by doctrine been limited to Sparrows. If anything the liberal use of the R-77 by the community is one of the issues... from my sources I understand that missile was essentially a pre-production model in very limited distribution throughout the '90s and really only see's more widespread appearance in the -1 variant that appears well after the millenium.

Did you release at high enough altitude to allow for the 6 rotations of the arming vanes to occur?

No, the nose or tail fuse must be set for a fuse that has a time measured in seconds rather than hours. Tail fuses are primarily used for bombs that must penetrate a target, particularly armoured or hardened targets that might destroy or damage a nose fuse sufficiently to render it non-functional, prior to detonating. Plugged is for those occasions when this deemed superfluous, like when dive bombing soft or lightly hardened targets.

Hi Fred. I decided to create a separate post in the bugs and problems thread to generate fresh attention and hopefully motivate change by highlighting specific inaccuracies and provide details of particular issues and the accompanying evidence of why these are inaccurate and what needs to change. Whilst the airfield info thread is great it doesn’t cover specific problems, relies too much on the developer identifying the inaccuracies and being motivated to do something about them, something thus far has not been greatly in evidence. The best results thus far I achieved in seeing change for a more prototypical environment are by presenting specific issues as bugs in a detailed and documented fashion outlining what and where the issue is and providing the developer with as much of the resources to correct it as possible.