fixed Unable to set Acquisition source to point correctly.

[FalcoGer]

Today this happened to me. I was trying to set the acquisition source to some target points. I tried CAQ, but it would briefly select the point under the cursor as acqusition source then switch to T56, but without creating any terrain points. I don't know what the TADS was slaving to, it certainly wasn't the point as indicated by the nav range.

Then I tried directly going for the point numbers in the COORD page. That was a complete mess. It selected any random target point except the one I wanted. I am not sure what happened.

Track file is too big to upload and too big to be useful, but I have footage of the issue, which happened at around 58 minutes and 20 seconds. I'll try to get a track as soon as I find someone who will ED's job of testing and bug reporting for them (for free) with me.

 

Edited August 3, 2022 by FalcoGer

[FalcoGer]

Okay, I have figured out what is happening, I think.

This is two bugs. As CPG (not sure if pilot is affected) in multiplayer only, using CAQ will select the marked point as acquisition source, but then immediately switch to an invisible terrain point (T56). The pilot will only see the selected point, not the terrain point. The terrain point is invisible, but hovering the cursor over where you clicked enter will show the white cross with "CPG" in the center of the screen with the black circle on the cursor indicating a valid selection option.

The other bug is happening as CPG (not sure if pilot is affected) in multiplayer only also. When selecting a point from the coord page and it's not from the first page, it seems to select a random point.

Here is a track from both pilots. The problem occurred around the time of the second (?) mission I think, where we were to engage an APC near a compound.

CPG was host: https://drive.google.com/file/d/1damWLSp2HNUDn3cyl5ojqfup1ALG98-2/view?usp=sharing

 

**Edit**

Turns out it's more complicated than that. It's weird. Here's a video to go with it (1:34:50).

 

Edited August 4, 2022 by FalcoGer

[BIGNEWY]

On 8/3/2022 at 11:20 AM, FalcoGer said:

Track file is too big to upload and too big to be useful, but I have footage of the issue, which happened at around 58 minutes and 20 seconds. I'll try to get a track as soon as I find someone who will ED's job of testing and bug reporting for them (for free) with me.

We will try to reproduce but please drop the attitude, if you want to help as it seems you do there is no need for such comments. 

I have asked the team to take a look, if you do get a track replay showing it happen please attach it. 

thank you

 

[BIGNEWY]

It took some time b the bug has been replicated and reported