Terry Dactil

There is also an error with the back end of the needle being painted white. It should look like this ... Get the mod on this thread

Yeah... and while they are at it, how about also doing something about the visibility of the radio channel selections. Can you tell me what radio channel is selected here? I certainly can't. I think there must have been a competition in WW2 to design the ergonomically worst cockpit layout possible. The British obviously won with the Mosquito by placing the fuel tank selectors behind the pilot's seat, but I reckon the Corsair is a close second. (The Germans would have been dead last with the FW190-D9)

Left click in the box works for me ...

You can alter the trim sensitivity by changing its value in the default.lua file located ... >> DCS World\Mods\aircraft\F4U-1D\Input\joystick\default.lua Here are the original values. --/N/ Trimmers {pressed = device_commands.iCommandElevatorTrim, cockpit_device_id = devices.CONTROL, value_pressed = 0.002, name = _('Trim, nose down'), category = _('Flight Control')}, {pressed = device_commands.iCommandElevatorTrim, cockpit_device_id = devices.CONTROL, value_pressed = -0.002, name = _('Trim, nose up'), category = _('Flight Control')}, {pressed = device_commands.iCommandEleronsTrim, cockpit_device_id = devices.CONTROL, value_pressed = -0.002, name = _('Trim, left bank'), category = _('Flight Control')}, {pressed = device_commands.iCommandEleronsTrim, cockpit_device_id = devices.CONTROL, value_pressed = 0.002, name = _('Trim, right bank'), category = _('Flight Control')}, {pressed = device_commands.iCommandRudderTrim, cockpit_device_id = devices.CONTROL, value_pressed = -0.002, name = _('Trim, yaw left'), category = _('Flight Control')}, {pressed = device_commands.iCommandRudderTrim, cockpit_device_id = devices.CONTROL, value_pressed = 0.002, name = _('Trim, yaw right'), category = _('Flight Control')}, {pressed = device_commands.Trim_reset_kb, cockpit_device_id = devices.CONTROL, value_pressed = 0.0, name = _('Trim, reset all'), category = _('Flight Control')}, This method has been reported to be successful in another thread.

Would it help if you could press a button (my preference) or use a voice attack verbal command that would read the rudder position and apply trim to reset your rudder control to neutral? I remember when flying a helicopter a long time ago that it had a button to re-center the cyclic stick from a displaced position. ChatGPT can assist ... . We can definitely set this up so you can fly the F4U-1D Corsair in DCS without needing constant rudder pedal work. Essentially, we’ll create a VoiceAttack command that: Reads the rudder position (from your twist grip). Converts that into rudder trim. Centers the rudder input, leaving the trim holding the yaw. How It Works VoiceAttack can talk to DCS through the Export.lua API. We’ll grab the rudder value via LoGetControlInput(). Then, VoiceAttack will issue rudder trim left/right keypresses until the trim ≈ rudder. Finally, you let go of the twist grip — and the trim keeps the aircraft straight. 1. Export.lua addition Put this in your Saved Games\DCS\Scripts\Export.lua (or merge with what’s already there): -- Rudder Capture Function function ExportRudderPosition() local ci = LoGetControlInput() if ci then return string.format("%.3f", ci.rudder) else return "0" end end -- Make it callable by VoiceAttack function LuaExportActivityNextEvent(t) -- existing code... end (We’ll wire this to VoiceAttack via VAICOM or your existing export mechanism — if you don’t have that, I can show you a minimal TCP/UDP bridge.) There is more, but you get the idea. Just ask, and it will produces all the code required,

You are not alone ... (And you don't even see the Mosquito/Spitfire brake lever on my joystick. How did we ever live without a 3d printer? )

Yes. The mirrors are now completely useless unless you want to trim your mustache in flight. You can remove all the images in the mirrors with Right Shift + M

To my untrained analysis of the code, if you don't want to keep the original key binds, then just find the appropriate Button numbers in the default .lua file and reduce their values from +1 and -1 t0 +0.25 and -0.25 or some other reduced value. Good luck.

Yes. This problem was fixed for the Elevator Trim on the Mosquito some time ago Two lines were added to the default.lua file in >>> Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick\default.lua" I expect it would also work for the Corsair and could be modified for the rudder and ailerons too.. This below is for the Mosquito gives two extra control options , Trim Elevator Nose Up 1/4 and Trim Elevator Nose Down 1/4, to use instead of the originals -- ------------------------------------------------------------------------------ -- Tail Trim Wheel -------------------------------------------------------------- { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -1.00, value_up = 0.0, name = _("Trim Elevator Nose Up"), category = _("Flight Control")}, { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 1.00, value_up = 0.0, name = _("Trim Elevator Nose Down"), category = _("Flight Control")}, -- MOD ADDED HERE { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -0.25, value_up = 0.0, name = _("Trim Elevator Nose Up 1/4"), category = _("Flight Control")}, { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 0.25, value_up = 0.0, name = _("Trim Elevator Nose Down 1/4"), category = _("Flight Control")}, -- ---------------------------------------------------------------------------------- There will be a thread in the Mosquito forum where you can thank the original poster.

Yes. This is the type of setting that reduces the initial sensitivity but still allows maximum effect if required.

This works well on my Thrustmaster pedals. Reduces the effect of the initial pedal movement, so now it needs a lot more pedal movement if you really want to stick the Corsair on its nose.

That's great news. You certainly had a weird problem to fix.

Can you show us a screenshot of your brake axis tuning. If you are using the setup you showed on page one of this thread it appears to me that your brakes are operating from 50% to 100% and are never fully released. If so it would explain the very sluggish performance during take off.

Nah! I checked my system and I get pilot bodies in external views, but not when I am in the cockpit. Strange - Maybe there is not enough room for 3 of us in the cockpit.

Thanks, Boson. I think you've nailed the explanation perfectly. Back in those days aviation was more a 'seat of the pants' operation rather than the 'fly by numbers' we have today. An interesting fact in passing.... There have been fatal accidents demonstrating VMCA where 'higher is safer' can be exactly the wrong idea to apply. This is when your engine power decreases with altitude and the asymmetric thrust is less. This means that full rudder can now maintain the heading to a lower speed, and this may be below stall speed. This means encountering the aerodynamic formula (YAW + STALL) = (SPIN + CRASH). This is why smart instructors will always block full rudder travel with their foot so the student encounters the effects of VMCA well above stall speed.

The SnapViews.lua file appears to be OK in my system. I scrolled down a long way to the Mosquito section and the default VR entry exists. Perhaps the full 'repair' will fix your problem?

It certainly appears that you can move the control according to this bit in the manual. (Unless you are expected to enter combat with gear down).

Me too !

Another original manual is at https://www.vmfa251.org/pdffiles/Corsair Manual.pdf Om page 15 is No mention of the locking pin when folded, only the jury struts. Maybe there was a later modification, but that seems unlikely. (I asked DeepSeek ( AI ) and it found 16 references, none of which was about a lock pin when folded.)

Sorry, my mistake assuming potentiometers were out and everything was rotary encoders now. Not so easy then ... Perhaps the folks on the cockpit builders forum would have the solution for you.

That's easy ... You missed the last step You use the AuthentiKit Tuning App to synchronize the movements PS> Not as accurate, but close enough for me; Use Bodnars setup to increase the number of key pulses per encoder click.

Are the guns armed? (Left Shift + Space_

Agreed that's a fair comment if you ask it about something disputed and there are many different opinions on the internet. However, asking for stuff from official historic documents like aircraft pilot manuals and performance regulations is a pretty safe bet to be correct. What errors did it make in this thread?

Yeah. It's understandable now. My aviation career was after WW2 and performance calculations were greatly improved and more precise. In particular I used (and taught) that the Take-off Safety Speed (V2) was the greater of 1.1 times Vmca or 1.2 times the stall speed. I guess if I was also carrying bombs that would be nowhere fast enough to keep me happy.

Thanks for your explanation Holbeach, what you say is correct. I managed to find a great site for aviation manuals Avialog: Aviation Library and downloaded the Pilots Notes for our Mosquito. It looks like your reference. Since I have been happily flying the Mosquito on one engine at max power by staying above 150 mph, I think adding 65 mph and calling it a 'Safety Speed' is a bit excessive. I would call it a 'Feel Good Speed' All this is understandable since Vmca in performance calculations was not official in WW2. ChatGPT has some interesting stuff on this subject ... The concept of Vmca (Minimum Control Speed Airborne) as a formalized element in takeoff performance calculations did not exist in its modern regulatory form during the development and operational service of the de Havilland Mosquito in the 1940s. Key Points: Vmca as a defined regulatory term became standardized in post-WWII civil aviation regulations, particularly with the introduction of FAR Part 23 and Part 25 by the U.S. Federal Aviation Administration (FAA) in the 1950s and later by ICAO and EASA equivalents. During WWII, aircraft performance calculations—including for multi-engine aircraft like the Mosquito—were based on empirical testing and operational experience, rather than a codified set of performance speeds like V1, Vr, V2, or Vmca. The Mosquito, being a military aircraft, was not subject to civil certification standards. Its performance charts and procedures included speeds for safety, single-engine climb, and control, but these were not labeled using modern terminology like Vmca. However, the underlying concept of a minimum speed at which directional control could be maintained after engine failure was understood by test pilots and engineers. They considered factors like asymmetric thrust, rudder authority, and yaw tendencies in both design and flight test programs. Summary: Vmca as a formal part of takeoff performance calculations was introduced in the postwar era, particularly with the advent of civil aviation regulations in the 1950s. For the de Havilland Mosquito, such a parameter was likely considered in practice but not named or standardized as "Vmca" in the way we know it today.