M4ND4L0R3

Seriously cmon man... Read the information. Please. Im just not sure what your missing, I thought Mike's explanation was like 110% clear what the issue was with the hotas, im kind of lost as to why this conversation is still going or how you think your information is still relevant but I enjoy responding to you for some reason lol.... - I tried the switches. Its a low res video, sure, but you can still see how I have it set up, and I still explain it in the video. Im assuming your not deaf, so for someone who should be familier with the game you would know what screen im on and I physically tell everyone what I had them set to.... the main point of the video was to show that the inputs were not working/not being recieved by the game. This also doesnt require HD, you can see if the screen moves on the control menu whilst I am pushing something that the game is receiving information, if it DOESNT move you can see that its not working. Im unsure why you keep mentiong the low-res when you dont need 4K fidelity to hear/see what is going on... lol. But whatever. Sorry you cant watch it in HD man im not sure what to say, my friends in Australia can watch it and understand the issue fine. - The mode select switches on my hotas stop transmitting. This still directly applies to using the switch, which, as I said already, I initially used but was having issues and was continiously having to flick the switches on/off to get a response because EVEN THOUGH I ENGAGED THE SWITCH, I would still accidently turn my engines off after a period of time because the game no longer registered the switch was active. Does this make sense? Because it does to me. See the below, if you really need to have clear mapping diagrams and 5 page essay's for you to understand. Red circle is the " mode select " switch, with 3 settings, M1, M2 and S1 ( but I just call it M3, relevant button maps are Buttons 34,35 and 36 on the logitech throttle, I mentioned this before.... ) For my F18 map, Yellow toggle was: - > M3 = Autostart - > M1 = ATA Mode Now if what you said was true and worked ( but it doesnt because the red switch stops transmitting after X amount of time ), then yes. I would just click the switch and Autostart would only happen whilst the switch had activiated " M3 " ( Throttle button 36 ) , and ATA mode would only activate once M1 ( Throttle button 34 ) had been activated by the switch, right? Wrong. Because these buttons stop working, the game loses the information of what " switch " is active, and I would initiate autostart instead of ATA mode ( M3 was my landing/take off settings, M1 was Flight/Radar ) So, Thus, Therein, Therefore, Visa-vi, Mike's " elaborations" on modifiers are still 100% relevant when it comes to the mode select switch on the HOTAS, which, has literrally been the entire focus of this thread, Just incase that wasnt apparrant. Once again... If the mode select switches cant work, then Mikes suggestion of using the stick button modifier in tandem with the throttle buttons is the most efficent method. You are 100% correct. I could set one of these other buttons as a switch, and it would work. But as I said earlier, then I would need to remember if I activated the switch or not and I felt like in my situation that this was not a very efficent method to use. I have only ever been relating to the mode select buttons/logitech software in this post, because as mentioned my other process works with the other modules. Ok? Exactly! Its irrelevant information as its not the same setup thus any data you find during whatever testing you do is literrally useless, as this thread is literrally naming the issue hardware. Again, using cars as an example, if my forum post says " Help my BMW has an issue ", you are literrally a guy who owns an Audi saying " Well man I tested my car and it works fine so yeah stop making such a big deal " lol.... Would you like another example of how helpful your testing is on different hardware? As they say in Thailand, " Same Same But Different " Absolutely! This has never been an elitest " Im pro logitech " forum post, I have not slandered nor belittled other hardware. I have simply asked for assistance with my hardwear setup and issues with the game. I suggested in my video's that maybe DCS should integrate with logitech and other hardware providers, and then Mike told me that actually ED is partnered with thrustmaster, which is great really, to be honest. I have a thrustmaster lying around that I use for some other games because it has the throttle/stick linked to the same control input. My main point, is that, I CAN use the software provided with the hardware ( which to be fair is actually pretty good and makes the hardware even more diverse etc etc etc ), yet it doesnt work with the F14 module. What else shall we argue for literrally no reason about?

Draconus, man.. Sometimes I dont know if your actually helping or deliberately trying to argue with me on the forums. Please, have a good look at this: I realise english isnt your first language mate, but I feel like theres been several times where things have been misunderstood. The problem ( regarding to using the ingame modifiers/switches ) is that the stick stops communicating with those three " mode select " buttons. That line itself is enough to show that trying to use those three buttons as a long turn solution is not going to work, either as a modifier or as a switch, due to the lack of communication between the game and controller. So logically with that explanation: It wont. And doesnt, Ive already tried it when I first bought FC3 and was trying to figure all of this out. Ironmikes explanation of whats happening with those buttons makes crystal clear sense with the amount of hours ive sunk into testing WTF is going on with those buttons. ( in regards to using the ingame control assigns ) And overall, lets look at this logically: - Logitech sells a controller with a " mode select " button - After hours upon hours of issues, finally revealed those buttons dont work with the game because they stop transmitting and the controller loses " where it is " when playing with the in-game control settings. - An alternative is provided to using the " mode switch " by instead using a button on the stick to act as a modifier. Am I then going to continue to f*** around with trying to set switches as well using the same alternative? and try to remember if I clicked the " switch " button on the stick/throttle/rudder or not? Or would I just use the more efficent choice between the two, and simply use the button press modifier so I dont forget where I am in my map? THE ENTIRE POINT of the " mode switch " ergonomically in the design of the controller is to allow you to easily identify where you are in your map. Yet its not working with this module. So again, logically, the most efficent process would be to use the button press modifier as suggested by iron mike, rather than set up a switch somewhere else on the controller where I cant easily identify where I am in my control map. As a DCS player, I would think you would understand with the amount of s*** going on when your flying, the last thing you want to be worried about is " Did I click my switch modifier? " Can you see where my frustration comes from reading/responding to your post's man.... im honestly trying here.. No, Im not. I actually tried switches in the first place, because thats how I thought the game would accept the " mode switch " buttons in the first place, not as modifiers. If you check my first video from 1:35 you can see when I bring up the controls page I already had a " Mode 1, Mode 2 " etc set up in the switches, attached to those buttons, from when I was testing the profile previously. So no, theres no confusion, at least not on my side. Also, as an additional point: Correct, a T16000M doesnt have mode select and your even using a hardware provider thats partnered with ED, so to be fair any kind of testing you could be doing is irrelevant in my situation and kind of useless. Its kind of like comparing two different manufactuers of cars " Oh well I got in my car and turned the key and it turned on, so I guess you could be more specific as to what your issue is? " Your never going to be able to replicate the issues I am having with the game. Its resolved dude, for now. Let it rest, we are done here, RTB and move on.

Draconus... Regarding DCS modifiers with logitech/saitech: The " mode select " buttons wont work for an extended period of time. What Mike said is these three buttons/switches basically stop transmitting after a period of time, thus inducing the feeling that the " mode select " is not functioning as Logitech/Saitech said it would, which makes complete sense with all the testing I have been doing. DCS needs a constant input to consider it a switch. Mikes process works fine, because I am constantly holding a button down on the stick whilst using a toggle on the throttle. I then release the stick modifier and can use a different setting on the same throttle input, basically giving me the two " maps " I was looking for when using the " mode select " switch. So anyone looking to use their logitech setup can use this, it works great. I am using the " B " button, or joy_3. Regarding the logitech/saitech profiling app: Mike has offered ( from my understanding ) to assist me having a look at how the profiler interacts with the game doing one macro at a time. I will probably invest some more time into this after I have logged some more hours with the F14 (but then again probably not). As I said, I can adapt to different situations and this method of setting a modifier is actually allowing me to play the game, which is what I wanted to do initially. This method also still allows me to use my own " basemap " that I have across most of my planes ( landing gear in same location, flaps in same location etc ), so for me this is more than acceptable. In Closing: I will use the profiler for FC3/F18 ( and probably A-10 ll ), and I will use the stick modifier method for F14 until a future time where I have some time to make some video's showing the macro process in a one by one step phase. Thanks Mike / Draconus, you can consider this topic answered. Any future issues I will just PM Mike directly.

Hi Mike, First of all, Thank you for finally taking the time ( really, honestly thank you ) to reply, and a wall of text with explanations is far more preferable than getting it in tidbits. The truth is the truth and if it means I need to adapt again, and that adaptation allows me to play the game, then so be it. I am sure you may have guessed, but I am not afraid of adapting and as I have said several times I am happy to be wrong, I just want to be able to play the game. Thank you for explaining this. I did mention I wasnt sure about how it should function, and I can readily admit my frustration with the situation surely caused a lot of oversight in the mechanical side of why it might not be working. This explains why when even in the control menu I couldnt see the control presses, and has been a long time suspicion of mine back from when I was attempting to do this for FC3 and F18. I knew 100% that if I set a map where I was pushing two switches simultaniously, i was getting the desired result, yet felt I was losing functionality with this process. Again, not DCS's problem and I can understand. I was hitting the backslash key by accident during my rant, yes, and I had already set the throttle to M2 which was supposed to be the default settings. I did also try a few other times during the video while the mode select was in M2 and it still didnt work. Generally before I go hot under the collar on a video I have already tried before hand several times so that im not making a complete idiot of myself ( just a slight idiot ) in a public forum. The logitech software is still active, but there is no map loaded in it as the software was not assisting at all. only the default profile loaded with the software on startup was loaded ( blank slate ). So im unsure why it wasnt working either, yet it turned off once I was off the ground. IMHO, The logitech software does work. It is simply macroing the input to whatever command you input into it. The mode switch then changes what macro is being outputted at that control point to a new assignment. The software also enables additional functions for each of the inputs, such as increasing the hat range from 4 to 8, or enabling the radials to " simulate " a button push at certain % of rotation. This is how I developed the process of simply adding keyboard commands and removing all of the bindings from the game outside of axis commands. So does the software " give more buttons than you have ", no, but it allows you to change the function when you flick the same switch. I am happy to make another video flying the F18 module to show this. With all due respect, this is a fair response, but also still should prompt an investigation of some kind, rather than lean heavily on assumed inaccuracies of the hardware/software being used by the customer. Especially when I have shown evidence that it does work. Just my honest opinion. Fair enough. I will definitely try this, thank you. Let me be clear. DCS high fidelity modules are amazing, well built, and definitely well appreciated ( although it would be nice to be able to read a little bit clearer what all the instrumentation is labled in the cockpit, a popular complaint I am sure yet surely valid, generally only when learning the aircraft, and yes, as an aircraft " pilot " i should know what each switch does ). But I can with all honesty say I am an " Auto-starter ", as much as that probably brings me a fair amount of shame in the sim community. Its a matter of time for me, I dont have a lot of it, I am quite busy here in China and when I have time to fly in custom solo campaigns or online with friends, running through the pre-flight checklists is the last thing I am worried about, but I still appreciate all the effort that has gone into these modules. As I have mentioned in one of my video's, in the F18 module I use the mouse quite a lot, because a lot of the aircrafts inflight operations are with the DDI/UFC, so its actually great to get on the mouse and do what I need to do and its actually very efficent. However. For me, its not about " mapping them all ", its about efficency. Im not a pilot, but I would assume that the Pilot would NOT want to take his right hand off the stick whenever possible ( unless in auto-pilot obviously ), and would probably use his left hand to flick most of the things in the cockpit where possible. Unfortunately I am not very good left handed with the mouse, therein most of my binds ( yes I had the master reset set, but thats because in the F18 it goes off all the time if you forget something and its easier to flick it off and fix the issue ) are set up so that lever's/switches/buttons can be accessed with my left hand on the HOTAS. My F18 sim set up on the logitech app includes one of the hats and some of the buttons converted to a mouse function, because its easier to use my custom snap views set up on the DDI's and then quickly change what page I am looking at or a side bar setting using this method than it is to: - Take my hand off the stick - Adjust my view so that I can actually focus and read what im doing - Move my hand to the mouse and then make my changes to the DDI as required Yes mapping views might be a commodity, but when you dont have a VR headset, it definitely helps to have a good field of view, like you would as a real human being and a pilot, and still be able to quickly adjust your focus view without taking your hand off the stick and wandering through the numpad and / * keys to adjust the zoom everytime you want to take advantage of Again, thank you actually for the wall of text, it shows that you took time out of your day to give me a structured response and as another busy person to another, I appreciate it. I will use your advice and try again to create a map that I can use on the simulator. Still, it would have been nice to continue to use the keyboard macro system provided by saitech to play the module, but as I said before I am not above adapting and actually really just want to play the f****** game. If for some strange reason this still doesnt work I will contact you via PM, Kind regards, Josh.

Draconus, Im sorry man, but yes I know. For example, there are 7 toggles right? I used to have the red one circled set up as modifiers, Red was L/Shift and R/Shift, and yellow was also L/Shift and R/shift. THIS works, but then im losing functionality, and you ALSO have to constantly hold these in position while you hit the other switch that you want to modify. And unless you have three hands this still doesnt really help to have more than one " profile ". I also used to run this as a modifier, depress it once to activate the modifier, depress it again to turn it off, right? This also has the same issue as the mode switches on the throttle. Sometimes it works, othertimes it stops responding. Again, ive been tackling this issue for a long time before I came to the forums for help. And the OVERALL point is still the same. - Why does this work with F18/FC3, but not with F14. If its really the same game, then this shouldnt be happening. Yes man your right, I have seen this issue written about before.

Hi guys, I have a new video showing that the method of " adding modifiers " doesnt work, or works inconsistantly. Even in this video, pressing backspace which is supposed to remove the stick from the field of view doesnt work until the aircraft is at least in the air. Flaps are also still down after I take off ( after 20:00 mark ) regardless of how many times I try to adjust it using the controller OR the keyboard. Video link: https://www.bilibili.com/video/BV1n64y1U72G - To skip the introduction/rant, please start watching from 15:00 to 20:00. - You can see clearly I set the modifiers for button 36 ( M3/S1 ) and Button 34 ( M1 ) in my DCS control profile. - I then proceed to check the bindings in the DCS adjust control menu before returning to the game to find that yet again, this method produces inconsistant results. Please explain to me how am I supposed to play your module... with ONE profile? You run out of buttons pretty quick, especially as the pilot, I can only hazard a guess at how many options the RIO has to use consistancy as I havent even had a chance to TRY being the RIO yet as I cant get the pilot mode to work consistantly. So I just fly with one profile and use the keyboard for everything else? Like cmon guys. Again. My original method of only setting keybindings and using the logitech app to macro assign the keyboard shortcuts works 100% in FC3 and F18. Right now I just want a refund, this is absoutely pathetic. I can understand if I was just raving incoherrently on the forums with no evidence or knowledge, but I have provided MORE than enough evidence and time to you guys that SOMETHING is wrong with your module, yet almost a week later not even ONE response from someone at Heatblur. Please, FFS, - Investigate why the keyboard macroing process wouldnt work with your module when it works with others - Investigate why the game stops recieving the IN GAME BOUND MODIFIERS inconsistantly. Unbelievable.

Sorry, I know Draconus has attempted to help and even with video's I have still out lined the issue here on the forums, Is there really no kind of offical response from Heatblur on this...?

Test mode is the only way that the macro'd settings will activate in the game. Unfortunately. Yes, I am aware of how to set the buttons 34-36 as modifiers, however the issue is that the game sometimes has issues reading what mode its in. Randomly it might not turn off, randomly it might not turn on. The amount of times I have accidently turned off an engine in the F15 is ridiculous.

Any assignment I put in the keyboard segment is recognised when using the keyboard to activate the shortcut, there is no issue there. Im unsure why it is sometimes, but in my video's you can see that any of the modifiers with L/R shift, L/R ctrl, or L/R Windows are not working. L/R Alt works if it is a DEFAULT hotkey programmed into the game. The second I try to take those hotkeys that are " working " and move them to another function, they stop working. Its literrally bizzare. In my 3rd video you can see that I am just trying to use the display screen activation hotkey, such as L/shift+1, and even though I didnt move that hotkey, I just used it as the default hotkey and assigned it to the map on the logitech app, when I trigger the macro on the button it only triggers " 1 ", which is something else. The shortcuts from the logitech app ONLY work while the app itself is in TEST mode. This is also ONLY for DCS. Other games I have that I use the macro function in the app do not need the app to be in the applications testing mode.

This is what I am using now, but literrally only from no other option. This method works, to a degree. Sometimes the game doesnt register the " modifier " correctly, which is why I was investigating and figured out how to use the app instead. The app also provides more customisation options, I;E, I can turn my hats from 4 way into 8 way, or register them as a mouse etc. DCS only recognises the 4 way hat. Anyway. My main point is: Why does this process work fine for FC3 and F18 but not with F14.

Draconus... man... "That is adding keyboard binding. Of course it won't be recognized when you selected X56. If you want to add key binding, please select the command on the keyboard column. If I misunderstood, please describe your process in a few words. So I'd like to ask again what command are you trying to assign to your HOTAS, not keyboard, so I could test if it works with my hardware. That's how we test. Obviously I will not be able to test "modes" on my HOTAS. " I shall give you the benefit of the doubt, and provide you with a detailed explanation. Please see the following screen shot of my F18 map for DCS, as an example. As you can see, there are no bindings in the controller columns. There are only bindings in the keyboard column. Please see below screenshot of Logitech HOTAS app. Now what the logitech app does, is alow you to attach the inputed macro for each toggle/switch/rotary/button, and then by turning the very bottom left " mode selector switch ", you can then engage which column of functions you want the switches to be active. So, Yes, you are right. If I inputed keyboard commands into the controller columns.... it wouldnt register... but thats not what I have done. BACK TO THE ISSUE: In simple terms, the F14 module simply does not register the inputs from the controller if they include modifiers. Infact, I even tested the theory that if I took the default hotkey's provided by the game, and re-assigned them to different functions then maybe it would work... This is also incorrect. Tonight I attempted to move some of the shift/ctrl/alt orientated modifiers ( default hotkeys from other functions ), and strangly enough, once I had re-assigned the exact some hotkey to another function, they stopped working. The game only registers letters/numbers/characters, it doesnt register attached modifiers. And, once again, This method of using the logitech app to macro keyboard commands in DCS works without issue in the FC3 and F18 modules. So far its only the F14 module thats not working. I also bought the A10 ll module during the steam sale, but I havent had time to test it on that module yet. IN CLOSING: So its very clear that there is an issue here, and its proven to be a very time consuming one to test/reproduce. I can guarantee that the issue is somewhere between the Logitech app and the F14 module, since I have been left with no other option but to use the in-game control mapper to resolve my flight issues. For example, if I was using the Logitech application, I would be able to set ONE of my throttle hats to be an " 8-way " instead of a " 4-way ", meaning I could assign all of the Jester command wheel clicks on a single hat! Yet now I am stuck using BOTH of my throttle hats for 4 functions a piece as DCS wont recognise any more than 4 inputs. I can guess, within your 4500 odd posts and time on the forum, you have seen your share of players who havent exactly thought everything through before they rush to the forums and demand answers, but this is where " judging a book by its cover " becomes relative. You should allow some benefit of the doubt before you start insinuating people are wasting time on " simple issues " Also, game on sale 24/4/2021 was 429 CNY which converts to 85.4 AUD. Now that the steam sale has finished, the current price of the module is 511 CNY, which converts to 101.7 AUD. Maybe we can start over, be friends, and act like mature adults and try and help each other? I am willing.

Its not entitlement, its a response to paying $80 for a module and then being unable to play it using the exact same method and setup as I use to play FC3 and F18. I am unsure how I shouldnt be at least slightly annoyed by this, let alone the amount of time I spent trying to fix it myself before I even came to the forums to be " entitled ". As for the arrogance, im sorry, but everything asked by draconus was literrally covered in my other post/video's replicating the issue. I am also unsure how polite I am supposed to be to someone who wasnt being polite in their first instance? I still think I have been overally polite, considering. I am very happy to be wrong, I am even very happy to find out its something small and stupid on my end that im doing wrong ( although I dont see why, as mentioned other modules work fine.. ), I just want to be able to play the module that I paid for. Is that unfair?

Wow... Like seriously dude, The whole point of making the video's, is replicating the issue so that everyone can see the exact situation the issue is occuring. Low res has something to do with your bandwidth buddy, Its at least 720P and its not like the APP or even the game needs to be in HD for you to see the issue I am presenting. What cave did you crawl out of? 1. " DCS support devices, not some apps. Do you even need one? " Yeah, actually, if i want to use my > devices < multi-mode select, which then allows me to actually use most of the important keybindings required to operate the aircraft without taking my hands off my >device <. So if DCS supports devices, then where is the support? 2. "People don't usually have time for 20+ minute low-res videos describing simple problem." Wow, Yeah man. And people dont usually have time for spending 6+ hours figuring out why the f****** game isnt accepting commands from a device that its supposed to support. Let alone a module thats been out for 2 years. This process I am using works 100% with FC3 and the F18 module. 3. " So can you name one F-14 command and which HOTAS button you want to bind to it?" Yeah man, ALT-M -> Master Caution Reset, which is a default hotkey provided by the game, works fine assigned to any button on the HOTAS. for example SW1. 4. " Is it binding problem where DCS does not recognize the button push? Or is it problem with the bound button not working in game? " Both. Any additional hotkeys added to the profile are not recognised by DCS. AS YOU CAN SEE FROM MY VIDEO, Other default hotkeys that are assigned, such as ALT-M and G, are working fine, yet when I add custom hotkeys with multipliers ( such as right shift+X ), it does not accept the command. 5. " You do realize that many commands work only in special conditions? Like you can't gear up on the ground or sweep wings without hydraulic pressure, etc. " Yes, Sherlock, and if you actually read my post you would see I specified the 3rd training mission in the game, wherein the aircraft is already completely turned on and ready to operate. Thus, Therein, Therefore, wingsweep should actually work. 4554 posts and you didnt read, watch in its entirety, nor add anything intelligent to this discussion. *slow clap* Well done. P.S On my " Low-res 20min video " ( its 14 minutes... )", I also added timestamps in my original post if you wanted to skip through what I was talking about.

Hi Team, So after about 6 hours of troubleshooting, I have finally determined that I am unable to assign my own custom hotkeys in your module. I will link my previous post with video's and more detailed info below. IF I use the hotkeys you already assigned by default, I can take them and re-apply them to different functions and they will work. The point is, assigning custom hotkeys with modifiers is already programmed into the game. The method I have found ( and have been using for the FC3 and F18 modules ) works perfectly, but not with your module. Again, im unsure why I seem to be the first person reporting this issue after the module has been out for 2 years, but maybe you guys can invest some time into figuring out why some of the basic functions of the game dont work with your module. Even on sale, this is an $80 AUD module, and I am yet to even get the plane off the ground in the third training mission because I havent been able to assign some key functions ( like wing sweep ). Please see link to my other post which contains video material of the issue. Please fix this because this is just ridiculous.

Hi guys, Dont use the bindings assigned to the mouse, you cant edit them. Use the other row's listed with horizontal view/vertical view and you can assign either the throttle or stick mouse to it. I personally use the throttle mouse stick for look around while I wait for the piggy bank to afford a VR headset. I have a fix for some of the other issues with the X56 and DCS here in my post.

I know this is an old post, but its one of the ones I was looking at lately over the last 4 months whilst trying to address issues with the X56 and DCS. The problem is definitely with DCS, the X56 works fine with every other game I own. Check out my post and first video, I have a solid fix for the mode select issue and it works 100% with the FC3 and F18 Module.

Hi man, Nice to see someone else recently having issues with the F14 module. Did you physically save the profile with a name? I find that if I save the edited profile within the game using the save as function, the game retains the changes a lot better. In the meantime, lets exchange notes, check out my post/video's and let me know if you are having any of these issues.

Make sure you individually save that profile in the game, it should eliminate the issue. If you make changes to the bindings without physically saving it, it will give you this error.

Hi Everyone, Great to finally be able to get on the forums and start connecting with you guys, Im stuck in China so even creating an account was difficult. Unfortunately my first post is a bit of a ridiculous one, please see below: I have a Saitech/Logitech X56, which for FC3 and F18 ( After I found a fix) has been working AMAZINGLY for the last few months that I have had it. However, I recently bought the F14 module during the steam sale... and boy oh boy.... Let me first explain my fix for the famous Mode 1/2/3 issues ( unable to use the mode select in the game, even with the app ). After 6 hours of trialing, I found that if you manually set YOUR OWN ( or use the provided ) keyboard shortcuts to ALL the buttons in the app ( not the game ), that you can actually use the mode select, and without issues. This is the case in my experience with the FC3 and F18 modules. Once I painstakingly assigned all the keyboard shortcuts in the game, and then replicated those into a control map on the X56 app ( what a garbage app btw ), I was really enjoying those two modules and havent had a bad experience since. ( please also remember to put the app in test mode, I DONT know why, but DCS doesnt recieve your map inputs unless the X56 APP is in test mode ) Can someone at ED please explain to me WHY, When its possible for FC3 and F18, I cant assign my own hotkeys with multiple modifiers? Just as an example, I have tried assigning hotkeys with modifiers to moving the wings forward/aft/auto, and so far if I try to add multipliers, it DOESNT register? Only ( so far, only had the game since 26/4 and limited time to troubleshoot eveything ) the provided hotkeys are working. Since I am in China, I am unfortunately stuck with Chinese youtube to host the video showing the issue. Feel free to watch the entire rant ( It was midnight and after 3 hours of troubleshooting ) OR: - Mode select issue explanation 1:10 - Explanation of mode select fix 3:42 - BONUS Did you know? can set radial percentage 8:00 - Video segment showing Method working for other modules, but not F14 8:30 Video link: https://www.bilibili.com/video/BV1MV411n7Y1 Anyone who has any different experiences or fixes, please feel free to add below. Im only showing what I have had to do in MY experience. I have a chinese friend who also has an identical hardware set up to me, yet has NEVER had any issues playing the game ( yet, albeit, hasnt tried to use the mode select on the controller or app ) Thanks! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -= UPDATE =- So after another 1.5 hours of troubleshooting, and another video showing the evidence and process of how I am checking everything, I can confirm that the F14 module only responds to keybindings ( using my method ) that were provided by ED as a default for the module. Feel free to watch my second video, a lot shorter than my first rant. Video Link: https://www.bilibili.com/video/BV12A411V7bz To be absolutely honest: This is a 2 year old module now. I still dont believe I am the first person to have this issue, please shout out if you also had this issue. ED please invest some time into making sure the BASIC FUNCTIONS of your game works with EVERY module that you have. These issues are literrally in the most basic parts of a game and yet differnet modules have different results..... Fix it please. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -= UPDATE =- So after almost 12 hours of testing and troubleshooting, I have finally figured out that the Logitech APP and the f14 module are losing communication somewhere. Any modifiers set in the game are not being recognised ( outside of alt, but then alt doesnt always work either ) I have unfortunately resorted to using the DCS control assign page, but again, using the M1/2/3 triggers as modifiers sometimes and randomly stops working or you have to flick to and from several times to get it to engage etc. Here is my video link on the issue: https://www.bilibili.com/video/BV1FA41157Qp I realise that its not DCS's problem as a whole that the two programs arent communicating properly, but I have shown several times that it works with other modules, and so far it only has issues with the F14 module. I still honestly believe this should be looked into and resolved. The customisation and utility of the logitech app naturally make the modules much more immersive and involved and really bring much more out of the game. Again, Please fix it.