reported earlier Laser Range Finder Range Reads 9999 On First Detent. Bug Or User Error?

[Bad Karma]

Started in version DCS 2.7.11.22041 Open Beta and continuing in version DCS 2.7.11.22211 Open Beta

As CPG and using TADS system with 30MM cannon armed I use the first detent to establish range to target. The range displays as 9999 and shows the BAL LIMIT error. I use the second trigger pull and the laser displays the correct range. I can than fire the cannon accurately without any error. I am in hover while doing this as per the Quick User Guide.

I read through the AH-64 Quick User Guide on weapon implementation on use of the cannon just to confirm I was using the system correctly.

"8. If laser ranging is desired, begin lasing the target with the laser trigger on the RHG. If both the target and the aircraft are stationary, first detent ranging may be used. If either the target or the aircraft are moving, the second detent designation should be used."

I have a Thrustmaster Warthog Stick I am using as a controller. I have the first stage of the trigger mapped to LRF First Detent and the second stage of the trigger to fire weapons.  I did change the controller mapping to see if that would change things, but it didn't affect the results. There is some odd behavior using this setup as well I can range with the second detent, but the range will bounce back to 9999 pulling through the first detent. If I hold down the button assigned to the second LRF detent I can hold the correct range to target. 

I made a video of the issue; I apologize for the quality I am by far a YouTube expert.

DCS World AH-64 LRF 9999 Bug

[admiki]

It would be a lot easier for us if you let us actually see the video (it's set as private)

[Scaley]

9999 and the BAL limit suggests that the range that's being returned is more than 10km. If you fire a pulse train (with the 1st detent) and are set in "LAST" the system will return the highest range from, any of the pulses fired.  Is it possible you are ranging something that's not solid like trees? It does seem a little odd that you get a 9999 range with 1st stage trigger, and then a valid range with 2nd stage.

[Bad Karma]

20 hours ago, admiki said:

It would be a lot easier for us if you let us actually see the video (it's set as private)

Sorry about that I guess YouTube made some changes since I used it last. It should be working now. I actually made a new video since the last one was a little hard to see. This one is a zoomed in view on the TADS display.

 

TADS View First Detent Reads 9999

Edited April 8, 2022 by Bad Karma

[admiki]

Yeah, it is some sort of a bug. TBH, with no laser detection capable targets I don't see a reason to not just use second detent

[Catweedle]

I am surprised (well, not really) that this issue got marked as correct as is. For me and other users, "TEDAC RHG laser trigger – 1st detent range, or 2nd detent Designate as required." [DCS AH-64D Quick Start Manual EN.pdf:21.03.2022, p. 340] and "If laser ranging is desired, begin lasing the target with the laser trigger on the RHG. If both the target and the aircraft are stationary, first detent ranging may be used." [Ibidem, p. 276 and p. 288] do not work as advertised, i.e. TEDAC RHG laser trigger 1st detent always shows a final range of 9999. Can we have a clarification as to why this issue got marked as correct @BIGNEWY/@NineLine?

 

[BIGNEWY]

I have miss understood the problem, please attach a track replay example if possible we will investigate 

thanks

[Catweedle]

ah64d_1st detent_issue.trk

Cheers!

[BIGNEWY]

now I understand, and it is already reported to the team 

thank you for the track

[Bad Karma]

Thanks to the few others for posting up here so I know I am not crazy. Thanks Catweedle for posting a track I guess I should get used to doing that. I did have another thought about this issue late last night. I am using a Thrustmaster Warthog HOTAS and it does work great with the A-10 modules but can have some unexpected results with others. By default the two stage trigger used in the A-10 as a hold on the first detent even while the second detent is getting pressed. This is to activate the A-10 Gun PAC (Precision Attitude Control) system on the first trigger detent and having it active while the gun is firing. When the trigger is released the PAC system turns off. So I went into the Windows Joystick Control Panel and checked the default button mapping. On pressing the first stage of the trigger one button activated and hitting the second detent the sets both trigger detent buttons to on. So this whole thing might really be more of a controller issue vs a programming glitch. I am going to have to lean some Thrustmaster Target Scripting and hopefully get the trigger to function as I desire. This might just have to do with playing JD Longbow as s teenager. Maybe we can see if other users of the Thrustmaster Warthog HOTAS are having the same issue?

 

I also included a track file of what I am seeing.

Laser Range Finder Reads 9999 On First Dentent Pull.trk

Edited April 8, 2022 by Bad Karma

[Catweedle]

@Bad Karma, good thinking, but the problem is not a controller issue. You can test it yourself by mapping 1st detent to a key on your keyboard.