stelr

I'm in the camp of "there is a problem with speed and engine management." I am NOT a real pilot, but I just find it hard to believe that the 2800 Wasp was as delicate and prone to catastrophic damage when running over recommended limits found in the manuals for each version. On CV takeoffs, if I push the throttle full forward (max), the engine begins metal banging sound before I clear the island, with my wheels not even off the deck!. less than a min later, even with reduced manifold pressure (~40 in) and reduced pitch (2500 RPM), the engine seizes and I'm in the water. I doubt the navy would accept any engine that cannot stand some abuse, especially one that must engage in combat where one will eventually have to overstress the engine for short periods to survive. Manufacturers/engineers always put in hefty margins on recommended settings to ensure their product runs well for extended periods, knowing that their product can really do more, safely. Just look at CPU and GPUs for example. OC'ing is routine and even done by the manufacturer if requested in some cases. Built in safety margin. But I digress. One last point. Many here talk IAS vs TAS, and even CAS. Likewise, we talk mph and kts. I would recommend we try to all use IAS and mph in future discussion so that we are all on the same page and avoid confusion. IAS is what your instruments read in the cockpit, so that is easy enough to report without any additional computations. Also, if i read correctly from another source, IAS was what was usually used in actual tests results of the real aircraft. I recommend mph so it is easier for quick comparison to its other Allied aircraft. I understand that one must still convert to kph to compare to Axis aircraft, but at least we won't have three options (i.e. kts). Just my $0.02. (and, that's what it may be worth.) v/r Stel

I think Saxman's post is extremely germane and should be seriously considered in relaxing the very strict limits, while still requiring the engine management procedures. When the recent changes were made, I made sure all temps were in the blue but found that I kept cooking the engine within a very short time. In fact, during my first three CV launches I heard the knocking and airframe shuddering before my wheels left the deck, shortly after passing the island! I'm sure I was at max throttle (not knowing any better), but even so, I can't imagine any engine being accepted into full production that would be that fragile, not being able to handle a less than 10 seconds of overheating. Also, since the gauges aren't digital and tend to vibrate a lot, it's hard to tell if you are at 54" MP or jumping to 55" and potentially damaging the engine. Need a little slack here IMO. Also, IOT avoid stressing the engine and it suddenly quitting in a climb, I had to limit the climb rate to 500-1000 ft/min. The climb rate for the F4U was a key factor in the intended design IOT out-pace the Zeke. It should be able to do a sustained climb rate in excess of 3000 ft/min. If I tried to push it to 2000, the shuddering began, and I had to back off. maybe M3 can take a look at these things and balance the book (recommended figures) with pilot reports. I'm in no way suggesting PIREPs be taken as gospel, since they are not the same from pilot to pilot, but it's just my uninformed belief that this plane would have been too hard to just safely fly, let alone take into combat with a near-peer foe. v/r Stel

My squadmates and I see the exact same. In level flight, at 2700 RPM (max), when I push the throttle past the wire gate (detent), the animation is correct but there is no change to manifold pressure at all. I see others posting that they get an additional 10 kts doing this, but not so for anyone I have talked to or flown with. Am I missing something, or doing something wrong? And to clarify, this in no way refers to the bug in the RPM lever that can provide ~3200 RPM by using the mouse to push the lever down further. That is a separate issue. it just seems, in my experience, that water injection/WEP is not yet implemented.

Do you mean the "throttle"(MP) or are you talking about the "propeller governor handle (RPM)?" I read where after moving the prop governor handle to its full throw (down), you can use the mouse to move it down more to achieve ~3200 RPM and >70 in of mercury manifold pressure. Engine will overheat pretty quickly, so need to watch carb temps. Should it even be able to achieve these settings, or is this a bug? In either case, without doing the above, I really can't achieve speeds in excess of 250 kts in level flight. Same with others I fly with. That's with all cooling close, <50% fuel, and trimmed out for hands off flight. It seems like there is some invisible drag, or hidden extra weight. This also negatively impacts roll rate.

Not to be picky, but unless I wasn't watching close enough, I didn't see any parachutes or static lines attached to the cargo loads on the heavy drops as they are sitting on their pallets (also lack all the layers of honeycomb that would be visible on the bottom and top, just under the chutes). Riggers are gonna get their collective butts chewed for trashing all those supplies.

Sorry, but latecomer to this issue. Pimax Crystal here, using a 3090, so QuadViews is essential. I have the same issue and cannot fly until HotFix from DCS. PLEEEESE prioritize this issue ED!

Just downloaded the update and had a similar message from BitDefender but with a different file. Mine said..."The file C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\Mirage-F1\bin\MirageF1Core.dll is infected with Gen:Variant.Tedy.380857 and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean." This appears to be a Mod File (CoreMods), but I do not use mods and do not own the MirageF1.

Thanks. I'll give it a shot on the next mission.

Thanks, but I cannot access any command menus once my plane lifts off. I have the "\" button programmed for menu but it only works when I am on the ground.

Cannot land on missions after mission #5. So far on missions 6 & 7 my wingman always...always blows up on my very close 4 o'clock on short final, destroying my aircraft along with his. There is no way to get rid of him short of shooting him down myself. Seems he thinks this is a Blue Angels demo...and he fails to avoid colliding with his lead.

Was wondering if anyone here has used, or is using the PIMAX 8KX in DCS. Looking for feedback on the wide FOV available in the PIMAX headset vs the more limited FOV available in the G2 and how important the FOV is to SA and immersion. I understand there is a trade-off in visual clarity, with the G2 being sharper. That said, how much of a trade-off, and if so, is it worth it not considering the differences in cost. Please reply if you have actual experience with one, or preferably both these systems. Appreciate any assistance. v/r Stel

Same issue on P-51 module using Normandy map.

Exact same issues here with sound w/P-51 module. Tried F-18 module, but sound issue did not occur. Will have to test more, but anyone else having this issue, and is it limited to P-51 module??

Thanks Rangi! That seemed to do the trick. Mirrors working again. :)

After changing back from DCS World v1.5 Early Access to DCS World v1.5, my rear view mirror in the P-51D no longer works. The mirror is there, but instead of a rear view, there is only a green and brown pattern (similar to a camouflage pattern). It seems the textures are not displaying properly. The mirrors worked before in earlier release versions and in v1.5 Early Access; so not sure what is wrong. I have rebooted several times, so that isn't the issue. Not a memory issue either as I have 16Gig of RAM and a 4Gig graphics card. The HD is a 1TB SSD. Any ideas on how to fix? Tks in advance for any assistance.