dinosmike Posted February 13 Posted February 13 In all missions the gun does not fire, for me personally this makes some missions completely impassable because I do not have enough ammo, but without the gun I cannot finish off the remaining targets. Please check and tell me if I'm doing something wrong or if it's a bug? 1
Rudel_chw Posted February 13 Posted February 13 Make sure that you don't have the Spacebar binded to the gun trigger, only bind the actual Stick's trigger. This is because on most missions the Spacebar is used by some triggers to interact with the player. 1 1 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Looking Glass Posted February 14 Posted February 14 (edited) I think maybe the last update or ED has binded the spacebar to the trigger? Ive noticed that problem on another map/mission too, will check this out Edited February 14 by Looking Glass
Solution dinosmike Posted February 14 Author Solution Posted February 14 1 час назад, Looking Glass сказал: I think maybe the last update or ED has binded the spacebar to the trigger? Ive noticed that problem on another map/mission too, will check this out Yes, I confirm. The whole problem is in the space key. I also encountered this problem in another company. The problem was solved when I assigned shooting not to the space bar but to the joystick button. But it's inconvenient, now I have one more extra button. I hope this problem will be fixed somehow and everything will be like before. Well at least now I can play normally again. 1
Rudel_chw Posted February 14 Posted February 14 50 minutes ago, dinosmike said: I hope this problem will be fixed somehow and everything will be like before. It has always been like this, the Spacebar and the Backspace are special keys for use with the Mission's trigger logic and the solution is simply to avoid binding them to aircraft controls. 1 1 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Looking Glass Posted February 14 Posted February 14 I never binded my spacebar ever so not sure why it was bound this time? Is this an update thing?
dinosmike Posted February 14 Author Posted February 14 1 час назад, Looking Glass сказал: I never binded my spacebar ever so not sure why it was bound this time? Is this an update thing? This started recently, it didn't happen before. Apparently something changed after some update. And this is only in campaigns. 1
jackd Posted February 14 Posted February 14 (edited) As Rudel knows i still have problems with the FW190-a8 and the guns, especially with macros. BTW macros sent from a Razor gaming board work for the Lwin key. I get the guns stand by, firing worked some how 2 updates ago, now they are ready and loaded ok, but the red breechblock lights stay off and the guns wont fire. Ralt or Lalt + Spacebar set or totally cleared does not make a difference. Just set the keyboard binds to default, space bar is involved under stick. Reloaded the FW190-a8 module under full repair. NADA. Must be a bug IMO. Edited February 14 by jackd
Rudel_chw Posted February 14 Posted February 14 1 hour ago, Looking Glass said: I never binded my spacebar ever so not sure why it was bound this time? Is this an update thing? No, not an update thing, the default keyboard bindings for the Hornet have not changed, it has always had the space bar assigned by default to the gun trigger: You can check the default keyboard bindings by looking on the folder "C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Input\FA-18C\keyboard" ... look into the file "default.lua" The solution is simply to unbind the space bar and fire the gun using the joystick trigger's (or any other button you prefer) ... but this solution is on the user side, the mission designer at most can only document the issue so that the Campaign user does this unbinding on his DCS. 2 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Recommended Posts