Nealius

Github single download package like the A-4 mod is straightforward. A dance of multiple patches is anything but, and will get worse with future patches.

Yes, I'm looking through the ED manuals and the real pilot's handbooks Reflected included in his campaigns. "Propeller control lever" is most often used however the ED manuals are extremely inconsistent, with the Spitfire in particular specifically saying "pitch lever" with high frequency after initially calling it propeller control. Mossie manual also references prop pitch lever friction despite never calling the prop control lever a prop pitch lever. All of this inconsistent labeling of what is essentially the same thing makes it seem like all the terms are interchangeable. What @some1 clarified (low pitch = fine pitch = lever forward = high RPM; high pitch = coarse pitch = lever aft = lower RPM) isn't discussed in most of the manuals, and may actually be wrong in the P-47 manual? Page 55 says: But increasing propeller pitch should DECREASE RPM, correct? The manuals are all over the damn place. Digressing from the main topic but it should be clear that the documentation the average user gets doesn't enable clear understading of prop pitch; or worse appears to imply the opposite of what is true.

Wait, so by increasing the prop pitch/RPM lever you are also increasing RPM, but decreasing pitch? I see prop pitch lever/RPM lever/prop control lever used interchangeably in DCS communities and in DCS-related documentation (not to mention the levers themselves are labeled "P" and not "R") so I thought "increase" applied consistently to everything.

Yes.....that's what I described doing. I increase the prop pitch lever, and slow down. @Art-J It still does work in the Mustang. I was doing it regularly the past few weeks due to a nasty habit of coming in way too fast in the overhead break.

In real world it varies at lot, it seems.

It happens in DCS. As stated, I do it frequently and watch my airspeed needle plummet faster than it would if I had not increased the prop pitch. If that's not supposed to happen, then what's the explanation for higher prop pitch causing a dump of airspeed in DCS? It's clearly observable in all the Allied warbirds. I haven't messed with manual pitch on the Axis warbirds so can't comment on those. So by going fine pitch at a low power setting, I'm inducing windmilling and that's what causes the speed dump?

@Flappie in my instance lights were off, however in a later test they turned on once contacting the tower for landing, which differs from the default logic of them being on at all times during low visibility.

For verification. However according to accounts from former pilots and LSOs, the reason for aircraft type is to ensure the arresting gear is set, and 15 seconds is plenty of time for adjustment. What's missing from the guides is the context of the "old" days where there's a huge difference between an A-6, an F-14, and an F/A-18 coming in, to today where it's all Rhinos. Plus the newer Ford class carriers with arresting gear that doesn't even need to be set per aircraft type because of its design and advancement in technology. Pieterras guide is tailored mostly to present-day operations. People often forget this context. Once we get the Naval Phantom, the A-7, and F-8 I'm sure we'll see people doing everything according to Pieterras' guide--when period footage and documentation shows no clearing turns and carrier breaks at 300kts--because they haven't considered context or multiple primary sources, instead putting all their faith in one unvetted personality.

What causes the induced drag when going to high pitch settings? I frequently go into full pitch to act as a speedbrake when rejoining on AI formations or dumping excess speed in the downwind when I've fudged my overhead break.

Who relays aircraft type and weight to the crew setting the arresting gear before a particular aircraft traps? My understanding is that the aircraft type and state at the ball call is specifically to set the arresting gear to match the aircraft coming in (IIRC it was discussed by Jell-O on his podcast).

No but you'll suck more gas. Imagine rowing a boat. When you slap that water with the oar you take a bigger "bite" out of the water but you need more strength to push the oar through that water. If you angle the oar so it slices into the water a bit, you don't need as much strength to push the oar through the water. Kinda similar with props. At 3,000rpm the blade's pitch is taking a bigger bite out of the air but also inducing more drag, requiring more power to drive it, thus burning more gas, when you could achieve the same speed at a lower manifold pressure if your RPM were lower, thus saving gas. At least that's how I think of it.

I wish our saved activation wasn't so short. It seems authentication is required every three days? Mine only gives me 1.5 day's of access since I didn't log in yesterday. Disconcerting when there's so much money invested in something that can disappear into the aether.

What's 100% likely is that they're just having fun. Why is this even a discussion?

Download and patches are a hot mess. We have to download which version and then install multiple patches? Why is there no centralized, current version in a single download?

Reproduced with paid campaign Speed and Angels on NTTR, without supercarrier module but with the static tugs and deck crew. These seem to be the cause for the hangup for whatever reason. The end of the logs is always different. Months ago it was stuck on loading deck crew "tables." In some missions it's stuck on loading F-14A properties, in this one CH-47 properties, in others I've seen UH-60 properties. The only foolproof method of fixing it is to remove all static tugs and deck crew, however this is not possible with payware campaigns. dcs.log

This seems related to the Sim PostStart bugs posted in the 2.9 crash forums as well, as myself and others have this same behavior only with supercarrier and/or related static tugs and deck personnel. These are all the same/similar issue, perhaps a merge is in order? With all the threads separate I notice different troubleshooting methodologies in each which might make it harder to find the solution. Thread 1 Thread 2 Thread 3 Thread 4 Thread 5

Was Cobweb supposed to separate on mission 1 as well? I recall such a call on the radio but they didn't break off. I heard no more radio transmissions for the rest of the mission, either.

"It can't be that bad. I'll max the gamma to 3.5 and turn on my black dot labels." Oh it was bad. I survived and made it home, but it was not a particularly enjoyable experience. Not because of the darkness, but because of the combination of darkness, clouds, and the Mustang's horribly unreliable attitude indicator that tells me I'm more or less level when I am in fact 30 degrees nose down with 60 degrees of bank. Nearly CFIT'ed twice. Nearly mid-aired thrice on account of the AI suddenly going from 280mph to 150mph in the clouds. "Nice of them to turn their lights on. Wait.....those are not lights, they're exhaust flames!" as a silver zebra screams past my canopy from a sudden deceleration. I think the killer here, though, is the known dawn/dusk bug where everything goes pitch black. This caused my black dot labels to be useless, totally losing the formation in the soup. Decided to call it quits by climbing through a break in the clouds and heading north. By sheer luck I ended up a few miles behind the group on RTB and managed to land in one piece. Definitely not an experience I want to repeat. Darkness, I can deal. Clouds, I can deal. Darkness AND clouds, plus the pitch-black transition bug, is the kiss of death.

Log and DxDiag for good measure. Mods uninstalled. In my case specific statics don't matter. They're the same even on different missions/terrains that don't experience the issue. I can't find any consistency other than Marianas, PG, and on the occasion Speed and Angels hangs up, NTTR. dcs07FEB24.log DxDiag07FEB24.txt

It's not a fix, though. The issue keeps returning, and interferes with campaigns I paid for (Speed and Angels, Fear the Bones). What makes less sense is that only a small subset of the user base experience this issue. PC hardware issue? OS issue? Why does it run fine for everyone else except us?

Depending on distance/zoom level, the wings move from drooping to parallel to the horizon, and the intake FOD covers disappear:

Happening in PG map as well, mission was created in v2.9. Strangely, Syria and Sinai missions with the same supercarrier assets do not have issues. Is there any chance it could be terrain related (Marianas and PG being ED maps, Sinai and Syria being 3rd parties)? It shouldn't be the MOOSE or AIRBOSS scripts as those are copy-pasted (with edits only to the unit names) from the Syria mission which works fine. Z-PG-Sandbox-RealWx.miz

IIRC cockpit LOS blocking has already partially been implemented from the rear, allowing you to sneak up behind AI in certain situations.

Band of Brothers set the gold standard in my opinion. Pacific was good but couldn't measure up. I feel the same about Masters of the Air. There's a lot of nitpicks that take me out of "immersion," so to speak. The AN/M2 Brownings chugging at a Hollywood-slow rate of fire instead of the 850rpm they should be zippering at, crew opening their chutes at 20,000ft where they would go hypoxic, UFO physics, etc., but the story itself is enjoyable.

In no particular order: Casmo, Iain Christie, Bogey Dope.