Pyker Posted July 3, 2020 Posted July 3, 2020 (edited) Hi, I'm practicing BFM against an AI A4, guns only. Quite often, at the critical moment, that is, when the A4 crosses in front of my windshield, I squeeze the trigger but the gun just won't fire. Of course Master Arm is on (at other moments the gun will fire normally). This happens both with radar lock and without. Now, with radar lock, when this happens, there can be a cross flashing in the HUD telling me that I'm too close or something. I don't understand. How can I be too close for guns ? Or does it mean something else than too close ? I looked in the manual and in Chuck's guide and I can't find any hint or explanation. What am I doing wrong ? Thank you in advance for your help. Maybe important: - I'm still on version 2.5.5. - I use a TM Cougar and TARGET - First stage of the trigger is mapped on UI VR zoom + turn labels off (because I use dot labels when I'm not firing the gun). - Second stage of the trigger seems to work perfectly in any other circumstance. Edited July 3, 2020 by Pyker
Pyker Posted July 3, 2020 Author Posted July 3, 2020 Additional information: It seems to happen only when I squeeze both trigger detents at once. If I already have the first detent pressed, then the gun works fine. But if I suddenly squeeze both detents, then (even in free flight) randomly the gun won't fire about 1/5 time. So maybe it's a bug ? I haven't tried to repeat that with other planes or another joystick (that's the only one I have with two detents).
Pyker Posted July 3, 2020 Author Posted July 3, 2020 I removed the "labels toggle" key bind in the first stage of the trigger and it seems that it solved the problem. Probably when I squeezed the trigger the TM target software had to do 3 things at the same time and that was too many. So I was not doing anything wrong :-). How can I delete this thread to avoid further embarrassment ?
probad Posted July 3, 2020 Posted July 3, 2020 its probably better left as is to serve as a reference for the inevitable dude that also bumps into a similar problem
key_stroked Posted July 3, 2020 Posted July 3, 2020 How can I delete this thread to avoid further embarrassment ? It's not embarrassment, it's called learning. Leave the thread and share the information for others who might run into the same issue you did.
IronMike Posted July 5, 2020 Posted July 5, 2020 I second this, it is a great learning experience for us all and in that sense we are very greatful to you for laying it out. This community has always grown in knowledge together. Thank you. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
lxsapper Posted July 5, 2020 Posted July 5, 2020 @Pyker, TM Target handles doing multiple things on one press quite nicely. But you have to be carefull about the assignments you make. For example if second detent to fire the weapon works with "Space" and your first detent has a Ctrl, Shift or Alt Modifier, DCS will only see and interpret "Ctrl+Space"(ex.) not "Space" as you need to fire your gun. So using the keyboard macros on your HOTAS can be quite detrimental to your simming. Keep as many commands as you can aford as DX inputs (If you use the the 128 inputs mod for Targer you can will have more inputs avaiable than your Warthog has button/switch positions even if you program them to the off position of a switches). Or at least be very carefull with commands that can be used at the same time that use keyboard modifiers, even if they are generated from another button/switch it will still cause you problems.
Pyker Posted July 6, 2020 Author Posted July 6, 2020 Keep as many commands as you can afford as DX inputs. Yes, good idea. Thanks!
Recommended Posts