Search the Community

Hello aviators, Here is some bugs to fix and missing features that would be really appreciated by the community The firsts points might be fairly easy to patch/add since it is mostly related to HOTAS commands and bindings. The last one might be more of a change in the navigation system (HSD missing feature). AGM-88 WPN page overall behavior (BUG) : The page should be framed/highlighted when selected as SOI with the DMS (in all modes/submodes)(bug) WPN page should save modes and handoff on each station independently (bug) e.g. Station A is set in POS mode with a submode selected and station B is set in HAS mode Then cycling stations with MSL STEP should keep configurations instead of applying the same mode/submode to all weapons The only thing the WPN page is slaved is the active selected steerpoint on DED and it is applied on both stations When selected as SOI we should be able to cycle modes POS/HAS/DL with CURSOR ENABLE (maybe not DL because not implemented)(missing) AGM-88 WPN page in POS mode (MISSING) : When WPN page in POS mode is selected as SOI we should be able to cycle between submodes EOM/PB/RUK with PINKY SWITCH or TMS UP LONG (missing) TMS RIGHT cycles between threat tables (implemented), TMS LEFT cycles threat selected in the current table (missing) HAD page (MISSING) : We should be able to cycle manually POS sub modes EOM/PB/RUK with TMS UP LONG with OR without a handoff (partially implemented only with a handoff) The HAD should select automatically the submode used depending on PGM quality, unless you decide to cycle manually to change it (missing) HSD (MISSING) : Theat circles should be stored as steerpoints TMS up on a SAM threat on the HSD should select it as a steerpoint This one is related to this post from last year : It would be amazing to see it in next hotfixes ! I cross checked with the aircraft manual, correct me if I wrote something wrong. Thank you for your hard work. Kind regards

One thing that the modules are missing are a series of additional keybinds that takes advantage of individual players' HOTAS setups. Not everyone has a button in the right place, and some of us don't have any three position switches at all. I think that this is a missed opportunity to make the F1 an easier plane to configure for HOTAS inputs. Here's an example of what I'm talking about: I was practicing aerial refueling today in the F1EE. In the real world, I'd keep my right hand on the flight stick and keep my eyes on the tanker while I feel for the refueling guard switch, and push the underlying switch forward. When I'm done, I again use my left hand to feel for the switch and guard and drop both. Since we aren't actually in F1 cockpits, you have only two options: you look down and fumble with the mouse to click the guard and the switch individually. Depending on your zoom, you might have to try multiple times. Keep in mind that you're in formation with a tanker and one or more of your wingmen, so a moment of you being heads-down could mean the difference between being alive one moment and collision the next. The alternative is to use keyboard or HOTAS bindings. HOTAS is preferred, since there are no native keyboard mappings for the refueling system and the keyboard is cluttered with bindings already. If you're going to have to use bindings, to perform the above workflow you'd have to give up FOUR bindings. One to open the guard, one to push the refueling switch forward, one to push the refueling switch back, and one to close the guard. Given differences between people's setups, that's not realistic to expect people to dedicate that many bindings, since there are many switches that can be time critical (in the sense that you need to do something very quickly but you can't take your eyes off of the HUD). Speaking for myself, I'd have to dedicate four switches to the refueling system- and my setup only has four! These switches are Up = Pressed continuously and Down = unpressed. If changes are made, we can cut down the number of binds to just two: the ability for one bind to do two actions each. There are two ways of doing this: 1. Implement a ON else OFF-style bindings. Imagine a simple switch like I have. I'd like to be able to flip my switch up and have the refueling guard go forward and up. When I flip that switch back, the guard returns to its back and closed position. Since the switch holds the input continuously, I don't need to hold down anything to keep the guard forward. 2. Implement toggle buttons. While not ideal for my setup, other players will appreciate it, too. Some players may want to map the refueling guard cover to a pushbutton. Holding down a pushbutton isn't feasible, so this should instead be a simple toggle. Press it once, the guard flips open. Press it again, it closes. Simple. I think that all switches/toggles/guards should get this treatment. However, in the interest of focusing on the ones I feel are important, I've made a list to help. By no means is this list supposed to be exhaustive. It's focused on mappings that otherwise require excessive bindings and may be used in critical stages of a flight, such as in combat or while in formation. A summary: X else Y - When pressed, is in state X. If not pressed, will give state Y A/B - When pressed, toggles from state A to state B. When pressed again, goes from state B back to state A. ***All Airframes (F1CE, F1BE, F1EE, Presumably F1M as well)*** Master Arm switchology: Armament Master Switch Guard: Open Else Closed Armament Master Switch Guard: Closed Else Open Armament Master Switch Guard: OPEN/CLOSE Armament Master Switch: On Else Off Armament Master Switch: Off Else On Armament Master Switch: ON/OFF Armament Panel: Auto/Manual Firing Selector switch - AUTO else MAN Auto/Manual Firing Selector switch - MAN else AUTO Auto/Manual Firing Selector switch - MAN/AUTO Bomb/Rocket selector - 1+2/INBD/OUTBD Bomb/Rocket selector - INBD/OUTBD Fuselage Bombs Pushbutton - ON else OFF Fuselage Bombs Pushbutton - OFF else ON Wing bombs pushbutton - ON else OFF Wing bombs pushbutton - OFF else ON Fore/Aft selector switch: AFT else FWD Fore/Aft selector switch: FWD else AFT Fore/Aft selector switch: FWD/AFT MATRA 550 or Sidewinder Missile Switch: ON else OFF MATRA 550 or Sidewinder Missile Switch: OFF else ON Stores Jettison: Selective Jettison button guard - OPEN else ClOSE Selective Jettison button guard - CLOSE else OPEN Selective Jettison button guard - OPEN/CLOSE Emergency Jettison button guard - OPEN else ClOSE Emergency Jettison button guard - CLOSE else OPEN Emergency Jettison button guard - OPEN/CLOSE ***F1EE-specific*** Refueling: Transfer/Filling switch guard - Open Else Closed Transfer/Filling switch guard - Closed Else Open Transfer/Filling switch guard - OPEN/CLOSED Transfer/Filling switch - REMP. VOL (AERIAL REFUELING) Else TRANFERT (TRANSFER) Transfer/Filling switch - TRANFERT (TRANSFER) Else REMP. VOL (AERIAL REFUELING) Transfer/Filling switch - TRANFERT (TRANSFER)/REMP. VOL (AERIAL REFUELING) ECM: BARAX state Selector - ON else OFF BARAX state Selector - OFF else On BARAX state Selector - ON/OFF/TEST BARAX state Selector - ON/OFF BARAX emission ready korry - pressed else released BARAX emission ready korry - released else pressed BARAX emission ready korry - pressed/released

When I'm NOT using TARGET with the Thrustmaster Warthog HOTAS I have no issues using the flaps switch to control the state of the flaps in the Harrier. I just use the stateful configuration options for the throttle. If however I use TARGET software I cannot use the stateful joystick binds on the throttle switch (Cruise else AUTO and STOL else AUTO) as the are only usable on a joystick, not keyboard. Perhaps there's something simple I'm missing. Has anyone worked through this that can help? Thanks

Currently the F/A-18C binding options for the radar elevation is setup like the real jet, where the position of the axis controls the slew-rate of the antenna elevation, I applaud ED's choice to do this as it works great for people that have HOTAS setups specifically tailored to the hornet. However, I very much would appreciate it if ED could add a second axis bind to treat the antenna elevation axis as an absolute position, like the viper and other modules. For people who do not have antenna elevation axes with a sprung center, the current iteration is very difficult to use; this would remedy the issue. Furthermore, I think the current iteration potentially creates a fair amount of issues where newer players (without the sprung-center radar control) do not notice their radar slewing up into the heavens or full down and end up wondering why their radar cannot find any targets. Cheers.

I have somehow successfully launched Mavs before, but I cannot repeat it consistently. When I gave up the other night I'd discovered that no matter where I mapped the SSS depress down, it did not work. Even though that button would work for anything else. I just want play with the module and have never ran into such a convoluted process for weapons release on prior modules. Yes I'm aware that nozzles must be a 0 degrees to fire. Video should be at the part where I have an issue. Any help or even a good Hotas mapping of the T16000?

Hallo Freunde, ich stelle hier mal für Interessiere meine Kneeboard-Seiten zu den Funktionen sämtlicher HOTAS-Schalter der Hornet zur Verfügung. Da die HOTAS-Bedienung nicht in allen Bereichen dieses Musters intuitiv ausgelegt ist und sich die Informationen hierzu über das gesamte Manual verteilen, hoffe ich, dass damit relativ schnell die Funktionen erkannt bzw. nachgeschlagen werden können. Als Basis dient selbstverständlich die Belegung der "echten" F/A-18C. Ich habe deshalb diese und meine Übertragung auf das Warthog-HOTAS-System beigelegt. Zur Download-Seite

I have just bought the module I did the keybindings of all my 3 cougar mfd's in controls menu. Although main buttons were already mapped for right and left I have checked them also and corrected contrast and brightness mappings. But most of right mfd keybindings do not work. I have thrustmaster cougar mfd's. Left and center one works but for right mfd only 4 or 5 buttons in total are operational. I do not see the button in the cockpit moving. In controls menu everything is fine and buttons are all highlighted when I press them. I have no problems in Hornet, Harrier and F-16 or any other module where I have mapped right mfd buttons. Thanks in advance for solving this problem.

Guten Abend DCS Gemeinde Was mir schon bei vielen Modulen (Flugzeuge) aufgefallen ist, dass es gewisse Schalter gibt, die man mit für die es die Option hoch und runter gibt. Als Beispiel der Auswurfschalter (Düppel und Fackeln) der F/A-18 Hornet. In Verbindung mit der Funktion «In Game» kann ich die Schalter über meine Schalter am HOTAS steuern. Fehlt so eine Funktion dann muss ich z.B. für jede Schalterposition einen eine Schalterstellung auf dem HOTAS belegen. Wenn ich Pech habe, dann springt der Schalter «In Game» zurück. Meine Schalter auf dem HOTAS haben eine fixe Mittelstellung – Schalter am HOTAS nach vorne drücken und er springt wieder zurück. Bei der A-10 habe ich dieses Problem mit dem Autopilot-Modusschalter. Kann man in der Config was machen, damit ich durch die Schalterstellungen hoch und runter schalten kann? Evtl. eine alternative Software? Danke im Voraus.

Hey all! I recently picked up a bunch of gear and quite a lot of it is stuff that's superfluous for my setup, so here's your chance to get some barely-used, essentially brand-new hardware without the backorder wait times, at a sweet discount. Virpil Stuff Virpil CM2 base with Alpha Constellation L grip, and a Z-extension. VPC ACE Collection Pedals The bundle price for these through Virpil USA would be $959.76 with shipping, and of course are all backordered for god knows how long. Monstertech mounts 2x black Monstertech stick/HOTAS chair mounts (form 2, for most gaming chairs) and one VPC CM2 base adapter AND 2x Monstertech swivel and quick release adapters for quickly stowing chair mounts. 2x black Monstertech mouse extensions for chair mount. One left, one right. 1x black Monstertech chair mount keyboard tray. (In the box to the right of frame in the picture) 2x black Monstertech VPC control panel mounts, 1 center and 1 side. (Pictured in box) 1x black Monstertech throttle add on with VPC throttle plate (Pictured in box) Quite a lot of misc extra mounting hardware, cleaning kits, etc. There are lots of end caps and such for making the ends of the extruded aluminum tracks look nice. The price for these through Monstertech would be ~$976.00 with shipping. Chair DXRacer King chair. Retails for $500. Total retail price: $2435.76 BONUS: I'll throw in a Logitech X56 HOTAS with monster tech mounting plates as well (not pictured), so you can have a fully functional setup right off the bat. Retail price: $250 for the HOTAS, plus the plates. Unlike the other components which are essentially brand-new, these have seen a few years of use but have been well cared-for. Your price: $1000. I've gotta get this stuff out of my cubicle at work now that I'm actually working in the office again, so we both win if you pick up this sweet pile of gear for a fraction of what it's worth. Pickup at my office in Emeryville, or willing to make reasonable accommodations to meet you somewhere safe and public. More / detail pictures on request.

Hallo DCS und MSFS Fliegerkollegen, ich brauche eure Hilfe bei folgendem Problem (das vielleicht auch andere Piloten betrifft). Ich verwende einen Spiele PC mit einer RTX 3080 und 24 GB SSD RAM und verwende seit Kurzem einen Pico 4 Headset. Ich spiele DCS seit geraumer Zeit auf meinem Breitschirm in 2D. Ich habe dazu meinen HOTAS X-56 als Stick und Throttle gemappt. In 2D läuft alles wunderbar und ich bediene DCS und MSFS praktisch ausschließlich mit meinem HOTAS. Sobald ich aber DCS in VR starte, erhalte ich zwar ein hochauflösendes Bild in meinem Headset aber weder HOTAS noch die Keyboard Commands funktionieren. Ich habe alles möglich probiert aber nichts hat funktioniert. Nachdem ich eigentlich nur mehr in 3D fliegen möchte brauche ich eure Hilfe dieses Problem zu lösen. Herzlichen Dank und viele Grüße Ronald ------------------------------------------------------------------------------------------------------------------------------------------------------------ Hello fellow DCS and MSFS pilots, I need your help with the following problem (which may also affect other pilots). I am using a gaming PC with an RTX 3080 and 24 GB SSD RAM and have recently started using a Pico 4 headset. I have been playing DCS on my widescreen in 2D for some time. I have mapped my HOTAS X-56 as a stick and throttle for this. In 2D everything runs wonderfully and I control DCS and MSFS practically exclusively with my HOTAS. However, as soon as I start DCS in VR, I get a high-resolution image in my headset, but neither HOTAS nor the keyboard commands work. I tried everything possible but nothing worked. Since I only want to fly in 3D I need your help to solve this problem. Thank you very much and Cheers Ronald

Does anyone have a layout for how the F15E should be binded using the Thrustmaster A10 Hotas? Any help would be great!