Chief Instructor Posted November 23, 2010 Posted November 23, 2010 Hello all, This is my first post after lurking for quite a while! I have done a search and read several acounts of what appear to be the same problem, or similar but I have yet to find a solution. In essence, I can release weapons by holding down SPACE+RALT but when I map my X52 to do the same thing, it simply won't work. All of my other mappings seem to work fine but not this one. I read somewhere that you have to hold the keys down for a second or so because there is a delayed firing response. My experience would seem to confirm this. However, could it be that the Saitek profiler is not sending a long enough command to the simulator? Furthermore, is there anyway of modifying the profiler's behaviour in this respect? Any feedback would be very gratefully received! Best wishes, Luke (The CFI) :thumbup: CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System
Lixma 06 Posted November 23, 2010 Posted November 23, 2010 Sounds like the Saitek software is having trouble with the key combination. Try remapping 'Release Weapon' to another (preferably single) key in the options and then point the profiler to that. Alternatively, don't know if you knew this but you can have all weapons fire from the trigger if you want. All the cool kids are doing it. Here's how.... http://forums.eagle.ru/showpost.php?p=620292&postcount=53 ....makes life much easier and frees up a button on your controller.
Chief Instructor Posted November 23, 2010 Author Posted November 23, 2010 Ah yes- fabulous reply, thanks! I like the sound of a single trigger. It may not be strictly authentic but then neither is taking a keyboard flying with me! Cheers! CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System
bogusheadbox Posted November 23, 2010 Posted November 23, 2010 The SST programming software has no problem with the configuration. So the problem is, you have something else programmed to the same key or you have not programmed it correctly or have not held the button on the stick long enough. You have two ways of mapping the desired commands. You can map using SST software or you can map directly to a button using the DCS menu. If you are having trouble using SST software to bind this command, just simply bind the button directly to the command using DCS. Just remember you don't need to map everything using SST, sometimes it quicker just to map directly and my profile has a combination of direct and SST mappings.
Chief Instructor Posted November 24, 2010 Author Posted November 24, 2010 Got the problem sorted out. Thanks very much. It somehow makes so much more sense when someone spells out to obvious!!! Many thanks for your help :-) Luke CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System
Recommended Posts