450Devil

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?

The 23 July update stated "Fixed the radar signal and gunsight reticle from detaching out of place." Sorry but it happened to me again today on a MP server.

Git shot down by AAA on a MP server. I managed to crash land. When I went to the F2 view there was an additional broken tail lying near my overturned Corsair.

I may be wrong but I think DCS can only send audio out to one sound device as selected in the Options menu.

I saw a post in the Corsair forum that some were getting a CTD when trapping on the Essex carrier. I went into a MP server and trapped on an Essex carrier with the F4U. Result - CTD. I then went into a MP seer that had F18s and trapped on a supercarrier. Result - CTD. In both servers I did not use the Comms menu.

In MP CTD now happens whenever comms is not employed when landing on a carrier. Just tried the Corsair on DCSNZA MP server and the F18 on another MP server. Both time my system CTD when I trapped. Suspect it is a ED issue not one limited to F4U.

From the Corsair Pilot Notes

This happened yesterday to one of my flying mates when he did a repair on the Wolf Pack Warbirds server. When his Corsair dropped to the ground following the repair it bounced onto it's nose. Other team members have also reported damage being caused by the repair process. Another curious Corsair damage model is the propeller being bent backwards after taking hits from an enemy bomber. This also happened yesterday on the Wolf Pack Warbirds server when I was attacking a Ju-88 from its rear aspect.