[Helios Users- New Mosquito FB MK.VI Profile 1.0.1]

Updated 

1.0.1

1. Adjusted color of airspeed needle.

2. Removed accidental binding on "Keys" button that was sending cycle commands to the kneeboard.

[Helios Users- New Mosquito FB MK.VI Profile 1.0.1]

Updated 

1.0.1

1. Adjusted color of airspeed needle.
2. Removed accidental binding on "Keys" button that was sending cycle commands to the kneeboard.

[Helios Users- New F4U-1D Profile V 1.0.3]

1.0.3
- Changed mixture lever animation to not give missing image warnings.

[Helios Users- New F4U-1D Profile V 1.0.3]

1.0.3
- Changed mixture lever animation to not give missing image warnings.

[Helios Users- New F4U-1D Profile V 1.0.3]

Updated to 1.0.2:

Added Throttle Quadrant panels to Dash, L1 and Indicators.. Please see the Readme for using the controls and "Known Issues" about the warnings helios will give you.

[Helios Users- New F4U-1D Profile V 1.0.3]

Updated to 1.0.2:

Added Throttle Quadrant panels to Dash, L1 and Indicators.. Please see the Readme for using the controls and "Known Issues" about the warnings helios will give you.

[Arcade model]

28 minutes ago, Etask said:

I fly the P47 all the time, never blew up the engine. And I never use takeoff assistance in any of the warbirds I own. 

I have no problem in taking off, landing or managing the engine in any of them.

Yet the Corsair feels very weird, both in flight model and engine management (FM feels easy and artificial to me).

I agree with Saxman, having an engine that blows up every time you exceed POH for a few seconds is far from being realistic, quite the opposite actually.

And I’m not suggesting it should be easier or more “arcade” to manage. I’m suggesting it should have a more flexible, less rigid implementation; possibly with some power deterioration before the engine just dies.

But as you say, it’s still WIP so I hope it’ll get adjusted.

BTW, I love the F4U and I’m glad that Magnitude brought it to DCS, just trying to give some constructive feedback.

 

I would agree with that. Could use tweaking, but I don't think it should be easier or dumbed down, just adjusted to a more realistic manner. In a real car just because you hit redline doesn't mean the engine will blow instantly. Lots of variables in there to consider. I would assume aircraft engines are built with some pretty hefty safety margins.Just because you shouldn't go over a certain parameter, doesn't necessarily mean you can't.. maybe  .... I love the Jug too .. I have seized the engine a few times not paying attention Only seized the F4U once, coming in for landing and again wasn't paying attention. Loving the F4U too but I agree it's close but not quite there. 

[Why should exporting RWR and other viewports break integrity check?]

On 8/7/2025 at 3:12 PM, BIGNEWY said:

Sorry I do not have any updates to share currently. 

 

All good. Small potatoes in the big picture. Hopefully one day there will be time for some work on some of this as multi-monitor use  becomes  more and more prevalent.

[Special Options Slider to Adjust Trim Rate]

On 8/16/2025 at 4:49 PM, Terry Dactil said:

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.

 

I do this in the p-47 to slow it down too. Just wishing they all had slider options 

 

[Arcade model]

I’m guessing the people complaining about the engine management being too hard, have never flown the p-47, or tried taking off and landing a Spitfire with “takeoff assistance” turned off.  Or they are too used to full burner at all times in more modern jets.  Maybe its not setup perfect and some aspects needs adjustments, sure ( WIP right?). But hard to fly and manage the engine? Most certainly not. If anything, I think it’s actually pretty tame, for a warbird… imo

[Flight Model/Trim Issue with FFB Option Enabled]

2 hours ago, MAXsenna said:

Yeah, I'll skip WW. I might get a Moza while I wait/finally take a plunge at Rhino/Beast, or I'll wait for VPC. The Moza will probably be fine in a dedicated heli simpit.  

Moza feels great on helis. I will admit. On planes though, especially with my 100mm extension, there's a lot of slop around center where there's virtually no force at all, yet the encoders( or whatever) still register the movements. So you have this area of "free play" where you can still control the plane before and real force ever kicks in. ( not really noticeable on Helis though.

Not sure if that's a firmware issue or mechanical design issue. Deadzones aren't the way as the area is more than just " oh its drifting a bit". Its a noticeable lack of force in the center 5-10%. Even with every setting cranked to the max. Feels more like mechanical play to me.  Either way I'm happy with the purchase still, but I won't be holding on to it forever. Unless they address that problem before other products hit the market. I'm not opposed to WW hardware, just not a fan of their software. I've become a Virpil fanboy over the years but here in the US almost everything is back ordered and when containers come in, its all spoken for. So you order with the expectation that it will be a few months before you get your item.

 

[Flight Model/Trim Issue with FFB Option Enabled]

1 hour ago, MAXsenna said:

Yes, FFB issues in the Mossie has been reported before. I have an old MS FFB2, with a short extension. It's very twitchy to fly and impossible to trim.
ED has stated they will look into FFB for all of their modules when they get their hands on FFB devices. I assume this will be when Winwing releases their products as it seem to me that DCS is possibly sponsored by WW now.

Sent from my SM-A536B using Tapatalk
 

Just odd that all other modules seem fine. Not sure why the Mossie got the end of the stick… That would be my guess as well with WW. And that’s fine, if it will bring the FFB support along with it. I think I will skip WW FFB as I’ve got my sights on Virpil to really bring it ( hopefully). Moza is working okay for 90% of it all, but there are a couple shortfalls that bug me more and more with it. I try to ignore it, but as soon as I can order the Virpil FFB, I’m there.

[Typo on Airspeed Gauge]

22 minutes ago, MAXsenna said:

That's like when people repeatedly define their Internet connection in grambits.

Sent from my SM-A536B using Tapatalk
 

 Never heard that one, but I can only imagine!.. In the Helios profile I fixed it. It was driving me crazy.

[Helios Users- New Mosquito FB MK.VI Profile 1.0.1]

Version 1.0.1 of my Helios Profile for the Mosquito FB MK.VI. Hope you all enjoy!

Changelog:

1.0.1

1. Adjusted color of airspeed needle.
2. Removed accidental binding on "Keys" button that was sending cycle commands to the kneeboard.

 

Download here: https://github.com/HeliosProfiles/DCS-Mosquito-FB-Mk.VI-Profile-by-MadKreator37/releases/latest

User Files: https://www.digitalcombatsimulator.com/en/files/3346427/

For support and help visit:

CaptnZeen/ Helios Official Discord: https://discord.gg/VEjZ8RB4u7

or

MadKreator37 Discord: https://discord.gg/u8gT7DPHcV

[Helios Users- New Mosquito FB MK.VI Profile 1.0.1]

Version 1.0.1 of my Helios Profile for the Mosquito FB MK.VI. Hope you all enjoy!

 

CHANGELOG

1.0.1

1. Adjusted color of airspeed needle.
2. Removed accidental binding on "Keys" button that was sending cycle commands to the kneeboard.

Download here: https://github.com/HeliosProfiles/DCS-Mosquito-FB-Mk.VI-Profile-by-MadKreator37/releases/latest

User Files: https://www.digitalcombatsimulator.com/en/files/3346427/

For support and help visit:

CaptnZeen/ Helios Official Discord: https://discord.gg/VEjZ8RB4u7

or

MadKreator37 Discord: https://discord.gg/u8gT7DPHcV

[Helios Users- New F4U-1D Profile V 1.0.3]

New release to reflect changes in todays update.

[Helios Users- New F4U-1D Profile V 1.0.3]

New version for today's update.

 

[Flight Model/Trim Issue with FFB Option Enabled]

* I apparently failed to see the FFB issue 5 posts below.. I’m sure  it’s all related. But the track are here regardless.

 

[Typo on Airspeed Gauge]

Shouldn't this be "TENS of M.PH." not "TEMP of M.P.H"? Not really sure what the Temperature of Miles per Hour is, but it's definitely not how fast you're flying.

[Flight Model/Trim Issue with FFB Option Enabled]

Seems to be an issue when Force Feedback is turned on in Options. Have the Moza base running in Telemetry only for the tests so I'm not fighting any induced force on the stick.

- With FFB turned off ( just the option in DCS) the Mossie flies great, decently easy to trim, slow to react, like you would expect it to be. No weird Flight model tendencies.
- with FFB turned on it almost impossible to trim straight at all. All of the trim locations, based on the in-game indicators, to try to keep even remotely straight and level are at much higher values( for lack of better term). The flight model also does very erratic things. More unpredictable random movements and the biggest bother to me, almost religiously around 260-270 mph( going straight, up, down, wherever), it will start pitch down severely  (I'm guessing from the very far forward nose down trim you need to attempt to keep it straight at 240mph) and takes almost full back stick to pull out. OR you can give it a few  taps of nose up trim, literally, and it will pull right back out of the same dive that took almost full stick deflection to pull out of. It does not do this even remotely when the FFB Option is unchecked. I fly warbirds a lot in DCS so I am familiar with ever changing trim and hands on at all times.

Hoping I'm not the only one with FFB issues with the Mossie. Anyone else having similar issues?

It's not an issue with my base or anything. It works perfect on every other module I own.

I attached a couple of tracks .Freeflight on Caucuses. Not sure it will help, but maybe it will help gather data on the drastic trim differences and maybe some FM issue when you enable Force Feedback. 

Mossie_No_FFB_FM_Trim .trk Mossie_With_FFB_FM_Trim .trk

[Display exports]

On 7/27/2025 at 8:22 PM, GeoS72 said:

@jonsky7, @MadKreator, & @Deezle,

Thanks for researching this display export for the Hook!

I noticed the contents of the MFD_device_IDs.lua file identifies the MFDs as follows:

"CO" - co-pilot outboard
"CI" - co-pilot inboard
"C"  - center
"PI" - pilot inboard
"PO" - pilot outboard

MFD_SELF_IDS =
CO = 0,
CI = 1,
C = 2,
PI = 3,
PO = 4

My multi-monitor config includes the use of 3 CubeSim 600x800 monitors plus the primary 2160x1440 display.

I played with the MFD_init_copilot_in/out.lua and MFD_init_pilot_in/out.lua files to see if they would alternate between positions. Foreshadow: it didn't work. Both pilot & copilot displays were overlaying on top of the other. I'm not a coder so break stuff but not confident to fix it.

Here is what I modified for the copilot files:

MFD_init_copilot_out.lua (lines 17 - 18):
17: update_screenspace_diplacement(0, true, 0)
18: try_find_assigned_viewport("CH47_Copilot_LEFT_MFCD")

MFD_init_copilot_in.lua (lines 17 - 18):
17: update_screenspace_diplacement(1, true, 1)
18: try_find_assigned_viewport("CH47_Copilot_RIGHT_MFCD")

I made a separate entry on my monitor config file to add the correct viewport for CH47_Copilot_LEFT/RIGHT_MFCD. I also used the "0, true, 0" and "1, true, 1" displacement values to aid in monitor identification. It did not help. I also changed the displacement values in the pilot position to "3, true, 3" and "4, true, 4" respectively. Again, this was no help in blanking the copilot displays while in the pilot seat and vise versa. 

The blanking of the displays when the player is not in the corresponding position is very similar to the AH-64 TEDAC blanking issue when switching from CPG to Pilot seats. @jonsky7, you initiated that TEDAC thread almost 2yrs ago too.

The solution you guys provided is a good start! For now, the pilot displays are presented on my CubeSim monitors while in any other crew position. At lease they respond to input from the Copilot seat. Ultimately, I believe this problem should be resolved by ED.

What do you guys think?

It is definitely on ED's side. Not just making them switch but accessing all of the others, except  the one (Pilot out) that is currently exportable using RIGHT_MFCD. My files in the first post were just preliminary "patches" for Helios.. As I'm sure you found out, in each one of the mfd init files, you just need to un-comment the script that ed has in there by default ( in the GC_Base folder) and give each one its own name, any name. And use that in your monitor file.. However the switching of them is done in some code that we don't have access to ( I believe). Same scenario as the apache tedac. Even in the Apache the only way to get the main mfd's to switch is to use LEFT_MFCD and RIGHT_MFCD and just one of each and it will flip back and forth between pilot and CPG. I don't think the CH-47 viewports have even been thought about. I mean the script is already written in the files, then they commented it out of all except one viewport..

[Nice FM Update]

My only, (closest, irl) reference to warbird flying  is radio control planes, 30 years of all types, especially warbirds… Now of course thats not going to be exactly the same physics as a real one, but based on how the aerodynamics act at low and high speeds and motor torque, it seems to resemble the way I would expect it to react. At high speed, yes there is sway if you kick the rudder or snap the throttle but due to the increased airflow over the tail,  the recovery is much faster and changes in motor torque are less pronounced. At slower speeds you’ll induce much more sway from engine torque trying to flip the plane as well as the prop wash over the tail, especially with prop speed change, (and of course rudder inputs). Since there’s less air flow it keeps a swaying longer ( or it’s more pronounced), and a lot of time its easy to over -correct with rudder and the cycle continues. The worst being closer to stall speed when coming in for landing. With low wings and a very far forward CG they tend be inherently unstable. More-so at slower speed than higher speed. 

Not trying to argue any one’s points. Everyone is allowed their opinion on the subject, of course. But in my mind, for the only irl reference I have, I feel like it behaves more like how it should.  Or how I would expect, rather. 


* as for the speed, I’m not sure what it should really be. Is it underpowered? Too slow for a given loadout?  I have no clue. I suppose one would have to go off of the kneeboard chart and test each scenario in there with the exact engine settings and altitude But it feels fine to me.  Faster than the p-47 but slower than a lightweight spitfire. I also don’t want to debate that with anyone

 

[Helios Users- New F4U-1D Profile V 1.0.3]

Version 1.0.3 of my Helios Profile for the awesome F4U-1D by Magnitude 3! Hope you all enjoy!

Download here: https://github.com/HeliosProfiles/DCS-F4U-1D-Profile-by-MadKreator37/releases/latest
User Files Here:  https://www.digitalcombatsimulator.com/en/files/3345854/

Boring startup and overview video here: https://youtu.be/iNOFO3YUNrU?si=6cRPGVFzGYyeeRSa

Changelog:
1.0.1
-Added Water Injection switch on L1 and Water Pressure label on R1
-Added Water Injection switch and Water Pressure gauge to the Interface

1.0.2
- Added Throttle Quadrant Panels to Dash, L1 and Indicator panels.

1.0.3
- Changed mixture lever animation to not give missing image warnings.

For support and help visit:

CaptnZeen/ Helios Official Discord: https://discord.gg/VEjZ8RB4u7

or

MadKreator37 Discord: https://discord.gg/u8gT7DPHcV

[Helios Users- New F4U-1D Profile V 1.0.3]

Version 1.0.3 of my Helios Profile for the awesome F4U-1D by Magnitude 3! Hope you all enjoy!

Download here: https://github.com/HeliosProfiles/DCS-F4U-1D-Profile-by-MadKreator37/releases/latest

User Files Here: https://www.digitalcombatsimulator.com/en/files/3345854/

Boring startup and overview video here: https://youtu.be/iNOFO3YUNrU?si=6cRPGVFzGYyeeRSa

Changelog:
1.0.1
-Added Water Injection switch on L1 and Water Pressure label on R1
-Added Water Injection switch and Water Pressure gauge to the Interface

1.0.2

-Added Throttle Quadrant panels to Dash, L1 and Indicators

1.0.3
- Changed mixture lever animation to not give missing image warnings.

For support and help visit:

CaptnZeen/ Helios Official Discord: https://discord.gg/VEjZ8RB4u7

or

MadKreator37 Discord: https://discord.gg/u8gT7DPHcV

 

[Nice FM Update]

FM feels much better now. Dialed back the violent swaying a bit with rudder inputs and throttle changes. Recovers from the sway a bit quicker too. Feels great! Also, to me, the trim feels much more manageable. Absolutely loving it! Good show gents!