para504

The reason why ED should "care" is because a map (especially a redundant one that breaks existing content with missions and campaigns) is a reflection on ED's ecosystem. Players will be looking to ED for answers, not Ugra... The design decisions have an impact on the broader community, for both single and multi-player environments. The Normandy 2 enhancement is a wonderful idea, but not if breaks more than it fixes. I'm saying this as a long time DCS supporter, an avid Warbird fan, and I appreciate the continued investment. I just don't want to see a potential win with enhanced Normandy and see it turn sour.

I love the idea of an enhanced Normandy map experience, provided its "additive"/enhancement to original and not a separate map. I'd buy that product in a heart beat. That is, existing missions and campaigns work, and owners of original and Normandy 2 can co-exist on missions in multi-player (similar to Supercarrier). Unfortunately with a separate map approach it divides the community, will be a LOT of confusion for what missions work or won't. Many of us have already invested in Normandy 1, including mission/campaign developers - I seriously doubt many of us have the desire to duplicate that for a redundant map. The separate map approach seems like it takes a great concept and turns it into something negative for the DCS community (the negative results outweigh the good). I applaud the developers for enhancing the experience and thrilled to see continued investment in WWII era, but the separate map approach is not the way to go.

This is great & thank you for sharing it. Really look forward to Pacific theater in DCS... Out of curiosity is it feasible to use the Yak-52 FM with the cockpit & armament of choice (say the P-51 as it done here) ? Asking as I have no clue...

+1... Please remove the static reflections!

Do you recall which mod? I'm experiencing the same invisible tanks/bombs, and I have suppressed Spitfire related mods (that I know of), as well as repaired DCS... ETA: Appears to be tied to a WWII ship mod...

Great write up, and very annoying bug. Does ED have a status on a fix?

Same X-axis issues here on a gen-2 gunfighter. Have already serviced it several times. I’m on my 2nd x-axis board btw (1st one had same symptoms getting more frequent and severe until it wouldn’t work anymore). VKB guys were good about helping and replacing it when needed, but it is annoying reoccurring issue.

see the same nav lights glow during dim light, all power off to aircraft.

I've noticed the same in SP missions

I was getting Mission load freezes, and it seems for me to be tied to some older Mod's I had (older user created WWII planes). Was working fine before the 2.5.5 patch, but had to remove old mod's to get it to load. Hope this may help some folks; something to check anyway.

Yes, its been happening frequently again... Hangs up on Exit mission. In Beta version; I've been using FW 190 A-8 on Normandy map, but have seen it in other modules as well. Performed repair, using current graphics drivers (NVidia) without change to the problem.

I agree, the UH-1 is a module I really enjoy, but it has some irritating fixes that are long overdue. We shouldn't have to pay for break-fixes, but I would be very interested in continuing to invest in future helo's, provided I see support for the existing ones... I completely understand its a balancing act of resources, revenue vs maintenance, etc. but the bugs are really over-due for a fix.

Many thanks Baltic Dragon!

MP increase The community has been asking for a MP correction for a long time. Hopefully with the new variant they will introduce the 150 Octane / MP boost quickly. I can't imagine why they wouldn't.

Small world... Similar issue here with different stick (Gunfighter). I was flying the Hornet yesterday in Beta version and all was well. Today, discovered the NWS and the select Sidewinder binds for my stick are now grayed out. Both the row name and the box specific to the stick are grayed out (looks a bit bolder color than other "normal" grayed out options). DCS recognizes the controller buttons when I rebind, but the field/cell remains gray and not recognized when actively playing. I have tried the power shell DCS_updater repair, a reboot, cleared the controller category & rebound, etc. I also tried removing the stick controller lua file from my saved games folder; result was the controller column was empty as expected but the two fields names (select sidewinder & NSW) were still grayed out. No luck. Any suggestions? ETA: Was able to isolate the Saved Games controller bind files somehow became corrupt. My issue is resolved...