SMH

We can't fire from that position anymore either. We've totally lost the ability to steer the miniguns. (Neither the AI or us seem to be able to put the left side gunsight down.)

Thanks. Hope he releases it soon.

It's unrealistic in any plane, except in the most extreme circumstances. But again, it's one of those things they do to make the game more exciting, and also to give you a little bit more immersion and SA. Helps compensate for the not really being there factor.

But do we know it's SRS's bug? I believe it used to work.

Another one that I assume is due to WIP on multicrew: In 2.5.6.53756 OB the co-pilot's gun sight no longer lowers when he's set to fire. I also can't move it when I switch to the co-pilot position. He doesn't fire either. This is a pretty serious bug. Means we no longer can steer the forward miniguns, either with the co-pilot AI or ourselves.

2.5.6.53756 OB. It seems many switches in the Huey now have reversed their directions from how the left and right mouse buttons used to work on them. I assume due to WIP on multicrew. My muscle memory is all wrong now. Also the radio/intercom selector switch has a weird new behavior that it brings up the radio menu if switched to the private intercom. That doesn't seem right.

Someone posted some shots of a real one in another thread and it's pretty much in the same place (though it has some supporting structure not in our model). The carb heat lever was pulled back to the on position in that shot, so it was behind it. Did look like it would have to tuck under it when off. Here it is... So the panel's fine, but the control names should really be changed to something like English. I also see, looking at the Controls mapping, that the bomb selector switches are misnamed as bomb arming switches. That needs to be fixed. I don't see any mappings for the new arming handles either. Bit of a mess. Screenshots of tooltip and all control names matching "bomb" attached. (They say "arming" but they're really drop selectors and their switch covers.) Here's the pannable cockpit... http://www.nmusafvirtualtour.com/cockpits/WWII_tour/WWII-23.html

So it really does partially cover the carb heat lever! Wow, looks tacked on as an afterthought.

DCS intentionally lets you hear other aircraft when you probably wouldn't in reality. It's a gamey thing but helpful as it provides a bit more SA. I don't mind it it's quite cool in fact. I always fly the Huey with the back doors open to help me hear what's going on outside. I wonder if the "hear like in helmet" option might help. I never used it so not sure.

There's clearly more than one component to the sound. And recordings are optimized to use the full dynamic range of the recording medium. That doesn't have anything to do with their sound level in the real world. Whether you're recording a cricket or a nuclear bomb they both peak at 0 dB.

The one he flew didn't have a working turbo. And it's hard to transplant a sound from one guy's head to another's.

Yeah, there's a new bomb arming panel on the left side aft floor. (Covering up the carb heat lever, which doesn't seem right. Were they really like this?)

They seem to think the turbo acts like a big muffler and they're completely ignoring the waste gates on the lower cowling that most of the exhaust comes out of when the turbo isn't at full power.

It's quite good in the P-51, except that it changes your trim settings but at least you can still find a setting that works. It's absolutely amazing in the UH-1H and Mi-8. The stick centers to wherever it is when you release the Force Trim button. Then there's a bunch of planes I have to turn it off in: The Flankers want to somersault forward when I have it on. The Spit is so twitchy you can hardly fly it with FFB on. The F-5 won't trim back enough if you're heavy meaning you have to keep constant back pressure on the stick. Same with the P-47 regardless of loadout. I get why they have trouble supporting it as nobody is making FFB sticks anymore and there are differences in how the MS and Logitech sticks behave. But yes, the fact they managed to make it work in some aircraft means it could/should work in all of them.

2.5.6.53756 OB. The new bomb arming panel covers the carburetor heat lever. Not sure if this is a bug or how it actually was, but it seems wrong. (I haven't found need to use this lever yet but I'm hoping that's just because the engine is still WIP.) Also the tooltip labels for the new bomb arming controls could be a lot less cryptic.

Same.

Yeah I can't trim it at all with my old Logitech Wingman 3D FFB. There is a shake effect but I've only felt it so far when crashing. It's not quite as bad in the P-47 as in the Spitfire, which I find has the worst FFB implementation of all the DCS warbirds -- having FFB on makes the Spit too touchy to be able to aim which doesn't make a lot of sense. But I turn it off in the P-47 too due to the inability to trim. Too bad, as it works great in other warbirds like the P-51 (though it does change the trim settings I need to use, at least it's possible to trim it with FFB on).

Feels like it's back to as slow as ever after yesterday's update.

Feels like the framerate is back to really slow in Normandy since the 2.5.6.53756 update. Anyone else noticing the same?

Don't know. The broken cockpit shadows that it's had near forever seem to have been worked on, at least the headrest is solid now if not the surrounding geometry. Why working on that would detach a completely different object from its owner I can't imagine.

Still there after today's OB 2.5.6.52437 update as well. :(

Still a mess!

Same. And the cockpit shadows are still a mess too.

FYI, here's a good one of Tallahassee Lassie, one of the few with a working turbo. Note the smoke coming out of both the turbo and waste gates during startup. Would assume sound too. And I think I might hear the turbo whine in a few of the flybys.

No prompt to save mission after changing airfield coalition. As well, despite changes to coalition appearing to take effect when the mission is launched (with the green up arrow icon in the ME) when you return to the ME you see the airfield belonging to the coalition it was before making the unsaved change. (Probably because it's re-loading it from the file every time you exit the Mission and return to the ME.) The save prompts are confusing too. The way it should work is ask a question that Yes/No/Cancel actually applies to. "Mission contains unsaved changes! All changes will be lost!", is not a question. Also, "Press No to discard and continue unsaved", doesn't really make sense, as it seems it can't launch an unsaved Mission (except in the case above).