Jump to content

Recommended Posts

Posted

Hey guys,

 

I'd like to share an issue I'm facing while playing one of the campaign (P-51D: The Blue Nosed Bastards of Bodney).

During mission 3 or 4, I was unable to trigger the guns when I actually had to. Let me explain that.

Everything was OK until we get contact with bandits @ 20,000 feet altitude. We engaged enemies, and I quickly got a FW 190 aimed... but bullets refused to spit out the guns. I disengaged to check that: everything was turned on, but I noticed I didn't switched on the gun heat. At that point, I thought guns were kind of frozen which made them inoperable.

 

I started again the mission, this time I switched on the gun heat and fire some rounds shortly after take off to make sure everything was OK. It was. Moving forward in the mission, we faced the bandits again. And again, I was unable to shoot. Again everything's turned on. I checked the joystick mapping which was OK... That's frustrating!

 

I noticed during the flight (as squadron leader) that I had to hit space bar to confirm some things (like confirming I had the bombers in sight). As it's also the key map to trigger guns, I'm wondering if it could be linked.

 

Did you guys run into such issue? If so, how did you managed it?

 

Thanks in advance!

 

Posted

Make sure that you don't have the gun trigger binded to the space bar, as that is a special  key for the mission editor.

 

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

Posted

Hi Rudel_chw,

 

Thanks for your input. Indeed, changing the gun trigger to another key solved the issue. I've also thought about that before posting.

However, I'm a bit puzzled: I'm using the default key mapping in DCS as I've configured the controls directly in the HOTAS configuration app. So I only changed the controls for axis in the game.

So it means that by default, there's something weird in the way it's programmed.

Any, hopefully, that will help somebody else (even if it's kind of obvious).

 

Cheers.

Posted
4 minutes ago, Desdinova63112 said:

 

So it means that by default, there's something weird in the way it's programmed.

 


yes, it’s a dcs design error that seems hard to fix, so ED opted to document it and there is a warning about this on the 2020 User Manual:

 

X: START WAIT USER RESPONSE – start listening for input of the SPACE BAR key to set the specified flag to on. This can be a convenient way to progress a training mission based on the player's signal. Using this trigger will prevent an input command normally mapped to the Space Bar key (usually fire gun). 

  • Like 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

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...