450Devil

Yes, you are right. It does improve the handling of the Corsair in flight. Unfortunately, this simple change in line 895 also breaks the Integrity Check. So we need Mag3 to do this as an update to the F4U-1D.lua in the CoreMods/Aircraft/F4U-1D folder. Like your recommended Joystick curves. I was using my standard 25 / 25 but your 26 / 11 works much better. Thank you.

Firstly, the Corsair is definitely my favourite DCS warbirds module. Secondly, the inability to taxi in surface winds over 8 knots is really, really frustrating. Attached are short tracks for Spitfire, P47, P51, Mosquito and Corsair taxing in headwinds of 5 knots and 10 knots. The map is Normandy and the airfield is Manston. The Spitfire, P47, P51 and Mosquito have no problem with taxiing and changing direction in both 5 and 10 knot headwinds. The Corsair taxiing ability in 5 knots is OK if somewhat sticky. In 10 knots headwind it is impossible to turn out of wind. Please, please fix this defect. Warbirds Taxi Test_F4U_Wind 5 knots.trk Warbirds Taxi Test_F4U_Wind 10 knots.trk Warbirds Taxi Test_Mosquito_Wind 5 knots.trk Warbirds Taxi Test_Mosquito_Wind 10 knots.trk Warbirds Taxi Test_P47_Wind 5 knots.trk Warbirds Taxi Test_P47_Wind 10 knots.trk Warbirds Taxi Test_P51_Wind 5 knots.trk Warbirds Taxi Test_P51_Wind 10 knots.trk Warbirds Taxi Test_Spitfire_Wind 5 knots.trk Warbirds Taxi Test_Spitfire_Wind 10 knots.trk

MFD resolution was 1024 in settings. Deleting and rebuilding the fxo and metashader2 files has helped. Many thanks rob10 for your suggestion.

Last night I flew the Hornet for the first time since the latest update. I noticed that the radar display has changed - specifically the sweep appears as a vertical "long dashed" line instead of a solid vertical line. As the radar operated OK I am assuming that this new sweep appearance is now the intended one. Anyone else noticed this change? Screenshot attached.

Thanks to the advice of an online mate, before taking off I now fully cycle all trim tabs and then set them to 6, 6 and 1. This seems to mitigate the occasional hard right roll on take off.

I follow the SOP from the F4U-1D Pilot Notes (AN 01-45HA-1) and have had no issues with cooking an engine during landing.

I wonder if the issue making ground maneuvering so difficult is not the differential braking but rather the limited angle that the castoring tail wheel seems to be restricted to. The tail wheel could be preventing the tail swinging when either main undercarriage brake is applied. I have briefly experimented with other warbirds and the angle the Corsair tail wheel will caster to appears less that other warbirds with similar systems.

Seems to be fixed with the latest update.

While I appreciate that the Corsair did not have an autopilot, please leave it in as it gives me the opportunity to drink a coffee when on a long flight.

With my aging eyes I find it hard to see the Landing gear indicators given the dark nature of the cockpit front lower left hand panel section. It would be helpful if the white center of each indicator was more obvious (brighter). Just a wish.

Firstly, I appreciate the effort Mag3 has put in to the pilot image in the mirrors. I am a flatscreen user so I am not able to comment on how the pilot image works in VR. I use Tobii ET5 for head tracking. It seems to me that the main deficiency is that the pilot mirror image is based on a static positioning of the pilot's head / body in the cockpit. When I fly the F-18 for example, I can move my "virtual" head and body slightly sideways in the cockpit to change the field of view I see in the mirrors. There appears to be no ability to move my virtual head / body sideways or for that matter move my virtual head / body forward / back in the Corsair - thus restricting how I can alter what I see in the mirrors. No matter how I angle the mirrors the reflective angel appears to be back to the static virtual pilot head position. Even rotating the side mirrors completely outwards still shows the pilot image which would not be the case IRL. As this is a WIP I am hopeful that, in time, the Corsair's mirrors might come closer to how mirrors work in the F-18. It is a great module that has great potential in DCS.

As I have been unable to find reference to these issues in previous posts to this forum I have taken the liberty of posting this report. The attached screenshot shows the Batbomb radar controls in the Corsair. The Search Mode button is numbered 1; the Target Lock button is numbered 2; and the Batbomb Radar Rotary ON/OFF Switch is numbered 3. In my Controls Setup I have bound keyboard keys and HOTAS buttons to each of the Batbomb functions / actions. In testing these binding I have found the following: FOR THE RADAR ON/OFF ROTARY SWITCH 1. Using the Mouse - When set to OFF a Left Mouse Click on the Radar Control Rotary Switch moves it from OFF to HOLD 1 MIN. A further left mouse click then moves the switch from HOLD 1 MIN to RUN. 2. Using the Mouse - When set to RUN a Right Mouse Click on the Radar Control Rotary Switch moves it to HOLD 1 MIN. A further right mouse click moves it to OFF. 3. Using the Keyboard Binding - When set to OFF, pressing the Radar ON Keyboard Binding moves the Radar Control Rotary Switch directly to RUN. 4. Using the Keyboard Binding - When set to RUN, pressing the Radar OFF Keyboard Binding has no affect on the switch - it remains set to RUN. 5. Using the HOTAS Binding - When set to OFF, pressing the Radar ON HOTAS Binding moves the Radar Control Rotary Switch directly to RUN. 6. Using the HOTAS Binding - When set to RUN, pressing the Radar OFF HOTAS Binding has no affect on the switch - it remains set to RUN. FOR THE SEARCH MODE BUTTON 1. Using the Mouse - Clicking Left Mouse button on the Search Mode Button when it is out depresses the Search Mode Button and it stays depressed. 2. Using the Mouse - Clicking Left Mouse button on the Search Mode Button when it is depressed causes the button to pop out. 3. Using the Keyboard Binding - When the Search Mode Button is out, pressing the Keyboard Binding depresses the Search Mode button momentarily but it does not stay depressed. 4. Using the HOTAS Binding - When the Search Mode Button is out, pressing the HOTAS Binding depresses the Search Mode button momentarily but it does not stay depressed. FOR THE TARGET LOCK BUTTON 1. Using the Mouse - Clicking Left Mouse button on the Target Lock Button momentarily depresses it. 2. Using the Keyboard Binding - Pressing the Keyboard Binding momentarily depresses it. 3. Using the HOTAS Binding - Pressing the HOTAS Binding momentarily depresses it. Of the three possible setups for using the BatBomb Radar, only the TARGET LOCK BUTTON appears to operating as required in Mouse / Keyboard Binding / HOTAS settings.

Attached are two photos - one a screenshot of the bottom of the wireless aerial on the Magnitude 3 LLC F4U module and the other shows the wireless aerial on the real F4U in the New England Air Museum. The gap at the bottom of the trailing edge of the DCS Corsair appears to be too large in comparison with the real aircraft. Not a big issue but one Magnitude 3 might like to get their graphic artists to look into in due course. I am very impressed with the Corsair module. Keep up the good work, Thank you. ps. Will we see, in the future, a F4U-4 which was produced by Chance Vought from 1943 with the P&W R2800-18W engine (2,459 hp) and the Hamilton Standard four-blade hydromatic propeller?

Many thanks. That was it. Took the other ships away and could then set the Essex's velocity to 30 knots.

When making a single player mission I found that I was unable to set the Essex's velocity greater than 18 knots in the ME. IRL the Essex class was capable of just over 30 knots. Looking at the lua file "Essex_Class_Carrier_1944" I note that it has the GT.max_velocity = 16.83 in meters per second. Why is the Essex's speed limited in this way?