SWE-Timberwolf Posted April 19, 2018 Posted April 19, 2018 Hi! I'm using a Logitech X-56 and I have some problems programing it for the AV8B. It works fine when I program it in game, but if I use Logitechs software to program it almost nothing works. Has any one else had this issue? Is something wrong on my end or is it just because it is still in early access? System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel
Mapi Posted April 20, 2018 Posted April 20, 2018 Have you looked in the userfiles? There is one for the A10C, check this and change it to the AV8 https://www.digitalcombatsimulator.com/de/files/2881401/
SWE-Timberwolf Posted April 20, 2018 Author Posted April 20, 2018 Thanks, but I'm not sure how that would help me. Have you encountered the same problem your self and this fixed it? I have created my own X-56 profiles for all the other modules without any problems. But if we take the command "Slew TDC AFT" (Winkey + J I believe) as an example. If I start the game without programming the X-56 every thing works fine and I can assign the command to the button I want. When I start the game with the X-56 programmed not only does the programmed button fail, but the keyboard command also stops working. System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel
Ship Posted April 26, 2018 Posted April 26, 2018 Thanks, but I'm not sure how that would help me. Have you encountered the same problem your self and this fixed it? I have created my own X-56 profiles for all the other modules without any problems. But if we take the command "Slew TDC AFT" (Winkey + J I believe) as an example. If I start the game without programming the X-56 every thing works fine and I can assign the command to the button I want. When I start the game with the X-56 programmed not only does the programmed button fail, but the keyboard command also stops working. I also had issues with the X55 the Sim would not see the keys like the Win, Ctrl, or Alt keys. I fixed this issue by setting those keys in the programing software to repeat until I let go of the button. For example Left Windows + J in the programing software I set a advanced command and set the Left Windows key to repeat until I let go of the stick button. Here is a youtube video describing the process. if you jump to 5:28 in the video the process is described. After that I have not had any issues at all. Like you I have only experienced this with the AV-8B. It almost is as though the profile software runs the command too fast for DCS to pick up so in my case DCS only picked up haft of the keybinding. I dont know if this is what you are experiencing but I hope this helps! Matt "Ship" Shipley Virtual Carrier Air Wing 1 (VCVW-1) VF-211 Checkmates
Recommended Posts