Aernov

Different manuals say conflicting things about cowl flaps on takeoff, but the one more "focused" manual (left image) says to half-close them. I think it can be left to personal preference and takeoff profile (when weather is not dictating the cooling settings), but in flight you won't need them fully open even in 160 mph climb most of the time, which means less time pushing on the knob to close them after takeoff. And takeoff run itself is short enough to not overheat until airflow is sufficient. Flaps handle should be set in UP during cockpit check according to both manuals, and neutral position is used to lock flaps in intermediate positions. Not sure about leaving the handle in DOWN position (emergency procedure for hyd. failure says to put lever in neutral after extending flaps, but that's probably to prevent remaining pressure dissipation), but UP is "default".

Normandy seems to be more popular in multiplayer, it is larger (and an update/expansion is planned, with London and Paris, I think), but less detailed and somewhat geographically inaccurate (UK side is practically not modeled currently beyond coastlines and general landscape) Channel is beautifully detailed, has airfields of all shapes and sizes, and is somewhat easier for visual navigation since terrain is more detailed and thus more distinct features can be found, plus it looks more "diverse" terrain-wise. Also, more historic campaigns are made on Channel map as far as I know (the newer ones by Reflected at least). I have both, Channel was first, then I got Normandy and liked it as much as Channel. I wouldn't refund either.

Check your fuel pump switches.

I thought ED were going away from FC3-like modules and trying to split those in a separate game (but not much is heard about that anymore), leaving DCS with fully modeled clickable aircraft only. IMO people wanting to play with planes with not-fully-simulated systems and controls currently have more options than those who want as-realistic-as-possible systems, full controls and a lot of clickable switches that actually do something.

Magdeburg-Berlin-Seelow area map and lend-leased vehicles would be the compromise variant, appropriate for both European fronts. Purely Eastern front stuff probably won't come to DCS in our lifetime in the near future, at least from ED themselves. And late war vehicles can be used in post-WW2 scenarios too, anything that didn't participate in the war won't fit the scope of WW2 assets pack. Imagine the framerate above Berlin though...

We can start with most used Lend-lease vehicles like P-39, Hurricane and P-40 (those will (kind of) fit not only Eastern front but Europe and Pacific too) and liveries for Shermans, M3A1 etc.

This issue have disappeared completely since the update that was released after I made this post. Also, I have found the file, see post above yours.

Do you link any engine controls (Boost+Throttle or Prop)? Was Prop RPM lever all the way forward and pitch control in auto? Was manifold pressure below 52''? Applying turbosupercharger boost on takeoff may result in overboosting and bad things happening to the engine, especially if oil temp is below 50 or RPM is below 2700 (or even <2550).

This can probably be explained, but still, this departure should be looked at, just in case. Also, in the video you have strange AoA readings on HUD, those can't be correct IMO. NATOPS mentions cases of high-speed departures caused by simply rolling the plane (one example - 25k ft at 0.89 Mach indicated), and states SAAHS departure resistance effectiveness loss proportional to altitude and Mach number ("At 0.85 IMN at 20,000 feet there is roughly half the dynamic pressure acting on the jet as there is at the same IMN at 5,000 feet. In practical terms, that means that the aircraft has half the stability at 0.85 IMN at 20,000 feet than it has at 0.85 IMN at 5,000 feet due to decreased control power"). If you had flaps in cruise mode, this could have made the situation worse (0.87 M is the speed limit for that mode, flaps should be placed in AUTO, this will gradually retract them to less than 5 degrees). Rudder deflection is prohibited at >0.80 Mach. Thrust vectoring is prohibited above 30k ft at AoA near stall. And engine ratings above 102% RPM are limited to 15 minutes uninterrupted, but this probably won't cause such departure. Also, I flew 600+ nm mission, only problem I encountered was running out of oil, which is correct since standard oil tank filling for Harrier is for 4 hours of flight, and I got low oil pressure warning at roughly 4 h 10 min. I wasn't flying higher than 32000 ft and faster than 0.8 Mach though, and engine rating timing was closely monitored and not exceeded.

Razorback would be wonderful, even if it was a separate module. WW2-centered portion of ED is small, sadly, but this won't be a full scale module development either, and post-release support would be pretty much completely shared with existing D-30/40. And razorback does look better )

Tactical manual mentions that in multiple AUTO release mode (and other modes) point should be placed in the middle of desired impact pattern, with odd number of bombs one of them will hit that point, with even quantity they will be spaced around it. AFAIK the fix is planned.

Did you change MFD gain or contrast (or overall brightness) prior to uncaging IRMV? I often use the same MFD for EHSD and Mavs since you can select them from EHSD page in A/G master mode, and to make map and symbology clearly visible I set gain to almost minimum. If so, try increasing gain and playing with contrast. New DCS IR implementation makes stationary vehicles really hard to discern from background, thus bringing IRMV usability and range closer to reality, but I didn't encounter such severe range reduction, my Mavs usually locked from 8-6 nm, and in ripple subsequent missiles were immediately locking on uncage. Laser Mavericks can be better if you have the time to loiter a bit, they reliably lock on from 12-10 nm, and lock exactly what you are telling them to lock, not some tree or power line pole (seeker orientation is kinda wonky at the moment, it should center it's search pattern on designated point, but it can drift far from it in vertical axis, and doesn't reorient itself unless it is caged). Firing 4-missile ripple is not practical with LMAVs, but reliable precision and range are preferable usually.

Scroll bar current position marker in drop-down lists changes size depending on amount of stuff in that list. If there is enough things, the marker disappears completely, making scrolling through the long list inconvenient and long. Can minimal size of position marker be limited so it stays visible? ^Unit list contains a lot of statics, so scroll bar position marker was scaled down so much it disappeared completely^

IRL this LIDS caution light takes time to illuminate, thus NATOPS instructs to hold LTS TEST until it comes on. In DCS this behaviour is not modeled, but the guide was made with future features in mind (hopefully) or was based on real life one.

Can the battery be drained? How long it takes to do so in flight without generator?

Are there consequences of low RPM on the ground? (like spark plug fouling)

WW2 version of Marianas will be nice for sure, and it's free, what not to like, but what we currently have and what will we get in near future that is appropriate for the Pacific theatre this map represents? Japanese liveries for existing aircraft aside, we have no one for allies to fight, no Japanese ground vehicles, boats, AAA, infantry and such. F4U is coming, along with some ships, and that's pretty much it for allies too as far as we know currently (at least that can be helped by re-painting P-51 and P-47). And, for me personally, work on Pacific theatre means less attention to war in Europe and no hope for Eastern front (or at least lend-leased western planes widely used by USSR like P-39 and Hurricane) for a looong time. I will probably fly over new Marianas version for "recreational purposes", but I would prefer more fleshed out European theatre (ground vehicles/ships/artillery/fortifications and static clutter/infantry uniform and armament variants and aircraft, Italy, Germany, maybe North Africa. Not to mention Eastern front/Great Patriotic war assets).

Thank you for answers. I have never experienced Pitot icing myself, maybe I wasn't getting the right conditions before clouds upgrade, I'll continue to fly with heating off and hope ). As for carb air temperature - in cruise without turbosupercharger I often close intercooler shutters to maintain temperature above 12 deg. (that's with outside air temperature above 10 degrees on the ground, winter would require closed intercoolers for sure) (I don't use boost until throttle is firewalled and don't connect the levers). When descending with low power and no turbo, I imagine, we can encounter conditions for carburetor icing, plus, pilots manual warns about it. Mi-24, I think, models engine degrading with dust ingestion (completely different engines, but still), and since there are grass and dirt strips in DCS, this source of damage can be interesting to model IMO (maybe, including ingesting kilograms of fresh dirt blown up with rockets or someone else's bombs when flying through the clouds of the stuff). Aren't drop tanks get fuel forced out by vacuum pump exhaust? Manual says to reduce MP to 20'' and to use rheostat to maintain pressure when switching above 15000 ft. And for carb overflow - main tank gets about 10 gal of fuel per hour back via carburetor overflow return, thus we should use main tank for at least 10 minutes after takeoff and for at least 10 minutes for each hour of flight, otherwise main tank will fill up and all further returns will drain via overflow vent, which can cause continuous fuel siphoning resulting in significant fuel loss if left for a long time. It generates visible (from outside) fuel trail and increased fuel loss rate, and there is a procedure for breaking the siphon. Majority of DCS flights won't last for that long, but still... And Normandy map is going to get bigger too.

Are these operational? If not, are they planned? 1) Oil dilution 2) Pitot heat and icing 3) Carb heat and icing 4) Carb air filter and dust ingestion consequences 5) Emergency fuel pump rheostat and fuel pressure drop on tank switching in some conditions 6) Carburetor overflow to main fuel tank and overflow vent siphoning 7) Cockpit fogging/icing and ventilation/defrosting Tire damage when turning "on the spot" around one of the main wheels 9) Safety catch on gear lever Is the following as it was in reality? 1) Oil tank and lines vulnerability and oil loss rate 2) Hydraulic pressure gauge needle jumping from zero to 1000 with no intermediate pressure levels 3) Cowl flaps movement speed 4) Were there in-cockpit control locks? 5) Could cockpit vent tube be adjusted?

I meant my "request" not for detection triggers (which definitely should be a thing), but for stuff like triggers activating when all groups are landed (low alt, no speed in zone) or took off but still in airfield vicinity (alt above 50 ft AGL, speed above stall), or for triggering something like signal flares when runway is empty (no aircraft in runway zone at altitudes less than, say, 300 ft).

Altitude and speed parameters for trigger zones would be nice. Currently all these parameters can be set and checked for individual units only, it would be easier in some cases (if a lot of air units are present in the mission) to set an entire zone to work in, say, 300-1500 ft ASL range and/or 200-350 kts TAS range.

I have no mods and never had any (besides custom liveries, but currently I have none too). Deleting metashaders2 and fxo is a frequent ritual for me )

Hmm, maybe the issue is with flat shadows...