Search the Community

When controlling the HUD Contrast with keybinds, increasing it turns on the HUD, and decreasing it turns off the HUD.

I know that the control we have now is the same as the real one in the hornet, but can we get an axis control that is suitable for rotary knobs in throttles? By this i mean, in F-16 i can use radar elevation with a rotary knob, antenna position is scaled to rotary. But in the F/A-18, whenever i move my rotary for even 1°, elevation control constantly goes up or down. Again ik this is similar to the IRL hornet but its harder to use with many HOTAS throttles. 2 way hats act OK but i dont want to set my 2 way to radar elevation, im using it for airbrake. I wish you guys can add a maybe 2nd control option to make it suitable for rotary knobs, it'd really be better for many players imo

Hello everyone, A little while ago when the apache got announced i got the idea of making a cockpit for it. I started designing some panels to see how well i would do. I only started using fusion a month prior. My goal is to get a fully functioning pilot station with all switches and buttons that are in the real thing. Everything will be 3d printed and modeled by myself. I do fly in VR so there will be no screens in my cockpit for now . I am posting this here because i thought some of you may like the idea and would be interested in how things would look. So i will be posting picture here of my progress. I have been working on it for a little while now. but the Cyclic grip and collective grip are giving me a headache. not to mention the Tedac grips. If there are more experienced people here who do 3d modeling and have some tips for me PLEASE do share them below! Any tips in general are also very welcome! Thank you,

I just opened up DCS to do the F-15C campaign, but upon entering, I realized my key binds weren't working. I opened up controls expecting me to have set something wrong, only to see that all my controls were gone and that about 80% of the controls were greyed out, without any option to add new controls. The only controls that I could add were view controls and function key controls. I scoured the internet but couldn't find much on the topic. I deleted any custom content I downloaded, such as a mission, and the clickable FC3 mod that I wasn't using. I deleted all the input files from the saved games folder, and also from the main folder, in the Mods/aircraft/Flaming Cliffs/Input. I also went and updated the drivers for my HOTAS. The HOTAS I have is the Winwing Orion 2 throttle, with the F-15EX II grips, and the F-16 EX joystick. Nothing that I have done has helped at all. I was even playing the F-15C earlier that day and everything was fine. Any help would be appreciated!

#UPDATE: I uploaded a HowTo PDF with more informations and WIP pictures to Thingiverse. You can also download it from here: https://milkris.de/s/fn9isEywRaWQjxR DISCLAIMER: I’m not a professional maker! It’s not perfect, but it works and I’m fine with the result. Here and there, some filing, drilling, and gluing might be necessary... temp solution to fix the UFC ghosting bug. go to : DCS World OpenBeta\Mods\aircraft\F-15E\Cockpit\UFC\Indicator\UFC_Rear_init.lua find line : try_find_assigned_viewport("UFC") replace by : try_find_assigned_viewport("UFC_rear") Parts needed: The STL files for 3d printing: https://www.thingiverse.com/thing:6248787 a 7" 800x600 4:3 CLAA070MA0ACW LCD Screen (or just a red acrylic glas for VR pilots)https://www.amazon.de/CLAA070MA0ACW-LCD-Bildschirm-TFT-Monitor-HDMI-Eingang-LCD-Controller-Board/dp/B072JTB73F/ref=sr_1_1?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=1Q57UB0M245L&keywords=CLAA070MA0ACW&qid=1696496871&s=computers&sprefix=claa070ma0acw%2Ccomputers%2C95&sr=1-1 10 pieces: 6 x 6 x 10mm Tactile Switches (Display Buttons)https://www.amazon.de/Taktiler-Druckknopfschalter-Momentary-Button-Sortiment/dp/B08KY2QPZ6/ref=sr_1_7?keywords=6+x+6+x+10+tactile+switch&qid=1696497067&sr=8-7 35 pieces 6 x 6 x 4.3mm Tactile Switcheshttps://www.amazon.de/Taktiler-Druckknopfschalter-Momentary-Button-Sortiment/dp/B08KY2QPZ6/ref=sr_1_7?keywords=6+x+6+x+10+tactile+switch&qid=1696497067&sr=8-7 4 Potentiometershttps://www.ebay.de/itm/174261626629?var=473259663408 2 Rotary Encoders (Radio Channels) https://www.amazon.de/s?k=WayinTop+5+Set+360+Grad+Rotary+Encoder+Modul+EC11&__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=YJ7QO6J3747X&sprefix=wayintop+5+set+360+grad+rotary+encoder+modul+ec11%2Caps%2C94&ref=nb_sb_noss 2 Dual Rotary Encoders (RadioVolume)https://www.ebay.de/itm/225271940062 2 ON-OFF-ON Switches https://www.ebay.de/itm/182568517273?mkevt=1&mkcid=1&mkrid=707-53477-19255-0&campid=5338748320&toolid=20006&customid=K4AVAs4ZAAAAgC9iOSdfZ7EEgU0AAAAAAA a Leobodnar BU0836X USB (or an Arduino for DCS BIOS)https://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=180 a 12-button joystick USB (not needed if you use Arduino)https://www.amazon.de/Quimat-Nullverz%C3%B6gerung-Encoder-Joystick-QR04/dp/B06XD1WF8G/ref=sr_1_8?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=176ESIHEU5QHW&keywords=12-button+joystick+USB&qid=1696496950&sprefix=12-button+joystick+usb+%2Caps%2C93&sr=8-8 few black M3, M4, M5 screws, some hot glue, some 3mm PVC foam board Note: I wouldn't use potentiometers next time, even though it might be less tactile and realistic. Instead, I would install rotary encoders in place of the potentiometers. This way, you can also use the BBI-64 Button Box Interface (which doesn't support axes), but has enough inputs, and you'll save the 12-button USB board. https://www.leobodnar.com/shop/index.php?main_page=product_info&cPath=94&products_id=300 !! NOTE !! This thing is BIG! If you have a small printer like me (Creality Ender 3), you have to print some parts WITHOUT rafts!!! The UFC can be mounted slightly tilt forward or straight. There are two option you can print. You can label the panels by changing the filament at the appropriate print height in Cura (etc.). I only did this for the buttons. I printed the other labels on adhesive film. I made these prints resistant with acrylic paint. So, there is an option "NO-LABELS" for some STL parts. I have attached a suitable PNG or here https://milkris.de/s/DtK6gxqaiAgqQTo. This can be easily printed on A4 adhesive film.For some areas in the interior, such as the housing for the electrical boards and the back panel of the UFC, I simply used a 3mm PVC foam board. I simply used a Leobodnar BU0836X USB board, as well as a simple 12-button joystick USB board. It's not pretty, but it works out of the box. Of course, you can also use a different solution (Arduino, etc.). # Note: I wouldn't use potentiometers next time, even though it might be less tactile and realistic. Instead, I would install rotary encoders in place of the potentiometers. This way, you can also use the BBI-64 Button Box Interface (which doesn't support axes), but has enough inputs, and you'll save the 12-button USB board Since I already use a 4K monitor and three 7" MFD screens, my monitor outputs were scarce. The solution was the "Matrox TripleHead2Go". I got the DP version cheaply on eBay. Here I combined my three 800x600 MFD screens into one 2400x600 screen. Now I only need one DP connection to the graphics card for my three MFDs, and I can connect the UFC to the graphics card with a DP to HDMI cable. The viewpoint export must be adjusted exactly so that the lines are readable. Please refer to the pictures at Thingiverse! Since I change the UFCs, throttles, and joysticks depending on the aircraft i fly, I have created various PowerShell scripts for starting DCS, which accordingly adjust the MonitorConfig, etc. before starting DCS If you only use the UFC in VR, you can also simply use a red acrylic glass instead of the LCD screen. It's alive!!! it's a mess My little helper have soldered most of the wires My little corner. Full convertible Cockpit.

Hi everyone, In the recently released newsletter there was a document for the new voice chat feature, on page 10, there was a control menu example, with PTTs explicitly for voice chat. Would it be possible to instead use the current PTTs/transmit switches and related controls that are already implemented for modules (which currently bring up the communications menu), allowing voice chat controls to be bound on a per module basis? A possible difficulty however, will be the current communications menu, which is what the current controls bring up. Perhaps it could be set up such that if whatever PTT button/mic switch is quickly pressed and released (within a small fraction of a second) it brings up the current communications menu (allowing you to talk to ground crew, ATC etc, like we do now), and a press with a longer time before release inhibits the radio menu and just uses voice chat. EDIT: Another possible problem with this is how would custom radios be facilitated? Particularly if you've got more radios than the module's switchology supports, perhaps that's where dedicated global keybinds could come in. Or maybe module specific 'custom radio x' binds. EDIT: Deka with the JF-17 seem to be providing both a short-press/long-press option as described above, as well as a dedicated set of keys for the communications menu, and another dedicated set for voice chat, users can then choose what suits them best (personally, I think this is the best solution). EDIT: Though, regarding the current system: How are modules which have more radios than PTT switches going to be handled? For instance in aircraft like the Huey and C-101, there's only 1 transmit switch, and a selector to select which radio you're transmitting on. Will the current, dedicated, global voice-chat PTT binds key their own radios (allowing you to bypass the selector) or will they key transmit switches in modules? So for instance, in the Huey, would the current 'cockpit r.1 VoIP PTT' bind transmit on whatever radio 1 is (and r.2, r.3 will be for whatever their respective radios are), or will it simply key the transmit switch, and the radio you actually transmit on will be controlled by the selector dial. EDIT: modules seem to use their real world controls, and if there is a radio selector, you have to use it. EDIT: @NineLine can this get moved to the appropriate section that was newly created? EDIT: Thank-you!

Hello, I would like to ask if a sensitivity slider for the button controlled rudders could be added. Currently pressing the button to push the rudder left or right will move the pedals in the chosen direction almost instantly. The sensitivity would mainly affect how fast the pedals and the virtual pilots legs would move in one direction while the button is held. I think this would make the module more enjoyable to control for those who don't have rudder pedals or can't use them for any reason, and also don't have an alternative axis that is suitable. Preferably such an option would also come with a keybind to toggle between "rudders staying in place after button release" and "rudders re-centering at the same rate which was selected with the sensitivity slider". Thank you in advance for looking into this!

Has anyone ran into this issue where I would love to use a free slider axis on my throttle for a speed brake lever but I guess I cant bind it? Yes, I know its a button IRL so dont yell at me but I feel like regarding controls, giving as many options as possible would be great? If anyone's tried this by writing up their own commands or editing some files let me know how you did it. Thanks!

Hey, I bought the viggen and wanted to assign all my buttons when i noticed i couldn't assign my mouse button 4 to "clickable mouse cockpit mode On/Off". The according field is greyed out and on hovering says: "No command available for this device". There were various suggestions reaching from Repopulating the .lua files over clearing all control categorys and reassigning to reinstalling the module but none have helped me. I am currently flying with mouse and keyboard so i have a virtual joystick for my mouse movement. Any suggestion appreciated

Hi friends! I want to know if is there any place to share projects to build in home? I am starting this topic with the intention to share my projet in the future and colaborate with community's projects. I am doing this display with arduino leonardo and a 9,7 hdmi display. The bezel will be backlighted too, so it start from a white material, receive paint and translucent label. I am also working in a force feedback control with 775 dc motors, arduino and optical encoder. you can see a planetary to colect three motors torque in the image above The flight control project will contemplate, ailerons and elevators controls, also rudder.

Hi there, I re-built my PC (with new harddrive SSD) and re-installed DCS completely fresh. This time Open Beta only. The "real" non-beta was never installed on this PC. I found a few strange things. One of them being that all controls setups for all my aircraft show a strange mix of descriptions like "Gear up" "Gear down" (the normal descriptions, as I knew them from my previous install) and some rather abstract entries like "Input.Bf109K4.trigger_a", "Input.Bf109K4_trigger_b1", "Input.Bf109K4_trigger_b2". It's not obvious to me which weapons "trigger_b1", etc refer to. It's a pretty frustrating task now to do all the bindings again, without really knowing what exactly I'm setting. How can I get back the "normal" text descriptions for all controls to be setup? Cheers, Emacs

On certain occasions the modifier buttons on my controller are ignored by DCS, i.e. when i press a modifier + button, then only the unmodified button is registered. I do not know what is triggering this bug, but I have noticed this since I increased the amount of my modifier buttons from two to four. When this bug occurs, the modifier buttons are not registered in the the control options as well. However, when I open the window where you define modifiers and then press ok, then the modifiers are registered again. So it is definitely a DCS bug and no problem with my controller.

Load up any free flight, or Mossie mission. Engines die no matter what I try to do to avoid it, almost immediately. All was fine prior to this update. Throttles, pitch etc. mapped to TM HOTAS and stick. Thinking a "problem", and not a bug. Possibly a new mapping interfering? Any help would be appreciated, can't fly my bird. Tried re-mapping, checked Axis controls etc. Trk file attached, happens immediately after mission start. Did I miss something in the change log? Tried instant missions with my P-47 which has similar HOTAS mappings, and all is well with engine management. Any Mossie mission, you get that chugging and stuttering on near full throttle, and one or the other engine will die quickly. Video coming soon - apologies for all the background noise. Had mic on, you get to hear my chair squeaking! Comment will take you to engine failure at 1:09 - engines always drop in RPM on mission start, even with throttles full forward, can see this at beginning of vid. Happens on any mission. MossieEngineshutdown.trk

When I switch my seat from the commander seat to the co-pilot seat, then I often have the problem that the Petrovich AI messes up the flight. Even when I am requesting control quickly, it can mess up the flight stability for a short time or even lead to disastrous results, because the AI does not smoothly take over the controls. The second problem is that my axis are not updated when I switch to the front seat, which can e.g. lead to an idle collective position for a brief time (despite of my options settings to always update my current axis position) until I change my collective to update it. So I suggest to simply grant the player control for the flight controls immediately after switching to the front seat, and properly update the axis positions to ensure a smooth transition during flight in single player. The player can still decide to grant AI control afterwards. Thanks.

I start the game in small window mode then I go to full screen after the plane/map/weather, and everything else is loaded. In the small window the mouse is accurate and it can perform all of the functions over the switches and buttons and use the mouse wheel functions. When I press Left Alt+Enter the accuracy is gone. This is just as of yesterdays 2.7 update, though in the previous version I would have to click the left mouse button to get it to function properly in any new window in full screen. Thanks for any help, this makes the game unplayable

P-51 have (had) the best trim. Hold a few seconds and speed much faster. Not working for for pitch trim with 2.7.

Hi Everyone, Small nitpick, but in the controls menu for the Mi-24P shouldn't the control system for the ATGMs be called 9K114 (for the 9M114 [AT-6 "Spiral"]) instead of 9K113? I thought 9K113 was for the 9M113 Konkurs [AT-5 "Spandrel"]. EDIT: 9K113 is correct, this cleared up the confusion. Thanks to BN though for confirming.

Hi, i switched from the warthog throttle to the CM3 a couple of weeks ago and like it very much. My only downside is that I am missing the feel of the different buttons e.g. the China hat and boat Switch on the warthog. It’s not so easy to differentiate the buttons on the CM3. is there a way to change them or has anyone made custom buttons?

It's been several times now that I had to manually clear the keybind that enables the camera to automatically track a launched weapon, it interferes with gameplay and ruins immersion and recordings. While I'm ok clearing the keybinds manually this isn't always (ever) possible, as I only find out it's bound again when it's already a problem. Completely disabling certain keybinds would prevent this issue, along with the issue of having keybinds that conflict with other software reappear over time, forever.

Hello, for the longest time I thought this was a real life feature. However I can not find it documented in any real world literature, and after consulting with others believe it may be a bug. I have recorded a track. First I enter active paused, reset trim, test controls in each axis. Then try moving pedal with full back cyclic, left pedal is limited. I then hold in left pedal while moving my cyclic around, and you can see the pedal deflection change as cyclic position changes. I then turned off the pedal dampener and did the same test to verify it wasn’t the dampener. I hope this is helpful, thank you very much Rear cyclic limits left pedal.trk

Hello, I have been following the threads associated with the trim in the Apache so before you dismiss my post as not being a bug please read all of it. I have noticed an issue that only seems to be with the rudder pedals when trimming the Apache. I first noticed this when I would come in for a landing, I'd have to put in lots of pedal to compensate for torque and then I'd trim. Then I would watch as the aircraft would spin wildly to the side I trimmed to. At first I thought it was me and just needing to get used to trim. Then I watched Wags video and he suggested pulling up the controls indicator. So I did and noticed some crazy behavior. In forward flight, when I press the pedal where I need it, then press forward on the trim button and recenter, it would work fine and trims exactly where I put it. However, it may work fine for a few trims but eventually it starts this crazy behavior. Once I have it trimmed for forward flight and then start landing, I'll press left pedal to compensate for torque and instead of trimming where I put the pedal, the control indicator jumps all the way to the left and trims there, in some cases all the way to the edge of the control indicator box and not where I put it. I began testing this on the ground and It is especially noticeable when you trim half way to the left or right and then trim half way to the opposite side. I can replicate this on either side of center and it does the same thing. I am using Logitech Pro Rudder Pedals and I have an old pair of Thrustmaster ball crushers that does the exact same thing. I am using Central Position Trimmer Mode, and I have tried different USB plugs, I have double checked that I don't have other controllers bound to the rudder, and I have calibrated the pedals. Maybe this is part of the reason people are having such a hard time trimming. For me it's so frustrating that I am getting to the point I don't even want to fool with the Apache anymore.

Mouse axis can be assigned there, but not HOTAS axis stick, which makes no sense to me as that is basically the same in terms of input, but the game simply blocks this option. I’m aware that there is another pov option that uses discrete inputs, but that works extremely bad comparing to the axis camera control. is there any way to make it works without virtual mouse/tracIR input?

Check out this forum post where I keep a constantly updated list of layouts and links to my Input Mapper and DS4Windows tutorials

First of all congrats ED on the release of the 64. I've had a blast tonight flying around from the back seat once I got my axis dialed in and worked out the force trim function. She's a bit twitchy but if your gentle and with a bit of practice it gets easier lol Now to my stupid question. How do switch to the CPG seat to let George do the flying in single player mission? I must be missing something so obvious. Thanks Doogie

By "modifiers" I mean keyboard keys like "shift", "control" and "alt". We can add custom modifiers in the controls menu but when I set the "G" key (for landing "gear") to be a modifier, it operates on toggle basis rather than a hold basis. I'll elaborate: When I map "shift + POV up" to gear up, I have to hold down the shift key and then flick the POV 8-way hat switch up to retract the landing gear, when I then let go of the shift key and flick up the POV switch, my POV goes up, as expected. However when I map "G + POV up" to hear up, I just have to press the g key once and then my POV hat switch turns into a gear up/down control, only returning to its intended purpose when I once again press G. I would like the "G" custom modifier to act like the default modifiers, how to do this?