Hinkey

Me too. Normandy 2 is still installed and functional, but the new module badge is up on the start screen, and the "install" fails.

Found the other thread on this issue. My problem was assigning TACAN 71X to a carrier which is already in use on the map.

Totally agree. This seems like a step down in build quality. The original gear and hook levers had sturdy metal shafts and the original hook handle appears to be a solid casting. The new ones seem very flimsy; they ship with stickers on them stating "Don't commit acts of violence, or it will cause the switch column to brake" (yes, that really is the quote). So apparently winwing considers them fragile straight out of the box. The cool new handles (Parking Brake, Wing Fold, and also Hook) are all hollow plastic and open on the back which you feel every time you move them. The case has been downgraded from metal to plastic, and all the new stuff has a light duty, toy like, feel. Positives: The metal switches still feel solid and SimAppPro seems to sync the lights well with the Hornet module. Overall I far prefer the original combination of PTO 1 and Combat Ready Panel.

Have downgraded to "Simplified Gear Lever" in DCS Special Options until they get a chance to fix this.

Running in to the same problem here. I do have a previously saved mission with Gun Camera removed, and that still works as desired. As a work around I was able to copy paste that jet into a new mission successfully.

Same issue here. Have had undampend yaw oscillations triggered by firing a missile or jumping into a wingman aircraft.

Same issue here. The HUD RWR symbols are particularly annoying since they overlap creating a bright green blob.

A three position flap switch keybind would be appreciated.

Nice, thanks for the links.

That looks good. I'm looking at trying to attach the winwing MIP to my monstertech. What mods did it require?

Your DCS flight model feels great. One of the best ones in the sim. I'm assuming airspeed is the accurate indicator. Do you guys recommend just disregarding AOA for now and flying reference airspeeds?

I read in another thread that random startup loading for TACAN, VOR, preset radial on HSI and altimeter setting is a feature. It is not an accurate feature. In an analog aircraft like the MB-339 the radios are set where the last guy left them. The last guy did not set the radios to some random airfield 700 miles away, he left them where they were when he landed. E.G. CDI set to the runway he landed on, TACAN/VOR set to field he landed at, radio tuned to ground or squadron ops freq. Now, your squadron may have a policy to zero out certain settings to force the next guy to look at them, but even in that case, under no circumstances, would the policy be to randomize the cockpit. Things that should/could be random: - Altimeter - Accelerometer (good chance zeroed by last crew or maintenance) - Transponder (good chance zeroed by last crew per sop) Things that should be set to local field: - TACAN/VOR - CDI (any plausible runway for aircraft type. So, semi-random) - VHF/UHF (for the purposes of DCS) tower IndiaFoxtEcho already does with with the flaps and speedbrake. The last guy left them full and out, so that's where they are.

Compass indicating 360° out is a serious problem IRL too. Think that's gonna get marked "correct as is".

Yeah, you can definitely deal with it once you notice it. You just have to remember when at cruise altitude watching your altimeter instantaneously jumping up and down by 1000ft that your are at the higher altitude. I have no idea which is correct for the MB-339 either. I haven't noticed this behavior on any other analog drum type altimeters in DCS before. I'm pretty sure those are actual physical drums with numbers painted on them being rotated mechanically. I don't believe they jump instantaneously, both for mechanical reasons, as well as the obvious clarity implications of having an instrument with 1000ft error. Maybe the Italians have a different system.

Are we seeing different lists? Thank you.

The altimeter thousands drum flips digitally rather than rolling with an analog animation as the hundreds drum does. This results in 1000ft inaccurate readings as you approach the next 1000ft altitude. For example, 4000ft and 4999 feet display the identical readout of 4000. MB-339 at just below 5000ft: A-10 at just below 5000 ft:

I love any poll where I get to choose between an SF.260 or a Thud. Correct answer: Both please! I had to go Panther for the carrier ops. vs.

I think those are AI hornets. That's already in the game (including grabbing the towel rack). Would be cool to have that on player aircraft as well. Love the Tomcat salute in mirror.

It is possible I exceeded the gear limits initially since I just jumped in and went flying. I didn't bother to look anything up. If I did overspeed the gear while flying would that somehow program the "Failures" tab in the mission editor? I have not seen that behavior before. When I originally placed the MB-339 in a mission it came in with all three gear preselected to fail electrically (I did not know this at the time, I never look at the "Failures" tab). I don't know how that happened but this appears to be more a mission editor issue for me not one associated with the MB-339. Further experimentation has shown that if I place a new aircraft on the map (of any type) and select a system in the "Failures" tab, all other aircraft on the map now have that failure set, including aircraft of different types which don't even have that system. The programmed failure will occur on all aircraft of the original type on the map. As I said, I have never looked at the "Failures" tab and don't know if this is the correct behavior or not. I don't know how your aircraft ended up with the gear selected, but at least I know how to clear the issue. BTW great job on this aircraft. I'm loving it.

Thanks for the response. No point in posting the mission. I went back to the original file and can't reproduce the issue. I'm sure it was operator error of some sort. It's just odd since I have never once even experimented with failures (don't think I've even clicked on that tab in the mission editor) and suddenly the gear were all selected. Working fine now. Thanks.

It would be nice if this included an aircraft weight/approach speed calculator. Granted, it is a simple aircraft, but keeping track of weights of gun pods full/empty, rocket pods full/empty, converting MK-8x to kilograms, weapons without weights in their names like; Belouga etc., ends up being a lot. Do you need to do any of that to fly DCS, Nope. But if it were in the kneeboard I'd reference it.

Very nice work guys. Tons of fun. Flight model feels great. External model and cockpit are top notch. Would love to see the M-346 and T-45C come over as well.

Thanks for the info. So, are we using 44 mils for strafing, or the 34.9 from "sight gyro and gun line" in the chart above.

Gotta vote no on this one guys. The time I had to fly tonight, I spent in the forums troubleshooting. If ED feels compelled to keep doing this then put a “spooky - opt in” button on the splash screen. But saying “We’ve provided you a method to opt out… after you quit, search the forums, then manually edit a .cfg file” doesn't really track.

Found it. For whatever reason, when I place an MB339 in a preexisting mission, it comes in with all three landing gear set to: electrical fault - 100%.