can not reproduce FCR MARK error

[Mr. Wilson]

The mark-point is not created in the place indicated by the radar, it is created with a very large error, it is very clearly visible on the track.

 

FCR MARK EROR.trk

[Frederf]

Can't look at it because I don't own Syria. Can you describe it or recreate it with an included terrain?

[Mr. Wilson]

52 минуты назад, Frederf сказал:

Can't look at it because I don't own Syria. Can you describe it or recreate it with an included terrain?

you can do it on your mission and see everything ...

[Crptalk]

 

[Frederf]

It might be related to the above double-movement. That should only apply in FZ though. Another thing might be that you're not CZ'ing after selecting the new markpoint. This would cause initial cursor placement to be mark point plus previous slews.

Here's a track of an FCR GM mark involving slews. You see that when I select STPT 26 the cursor jumps away due to my existing slews. When I press CZ the cursor returns to the location that I marked.

F16 FCR mark and CZ.trk

[Mr. Wilson]

This test shows how the weapon misses the aiming point of the FCR. The distance of the error is very significant. Perhaps for the same reason, the mark-point is not being generated correctly...  

FCR EROR.trk

Edited December 6, 2021 by Mr. Wilson

[Mr. Wilson]

14 часов назад, Frederf сказал:

It might be related to the above double-movement. That should only apply in FZ though. Another thing might be that you're not CZ'ing after selecting the new markpoint. This would cause initial cursor placement to be mark point plus previous slews.

Here's a track of an FCR GM mark involving slews. You see that when I select STPT 26 the cursor jumps away due to my existing slews. When I press CZ the cursor returns to the location that I marked.

F16 FCR mark and CZ.trk 39 \u041a\u0431 · 0 скачиваний

I pressed CZ but it didn't fix the situation

Edited December 6, 2021 by Mr. Wilson

[TEOMOOSE]

What do you mean exactly ?

The markpoints working just fine. There's no issue with it.

Note: don't forget to clear the offset after you placed the mark.

49 minutes ago, Mr. Wilson said:

This test shows how the weapon misses the aiming point of the FCR. The distance of the error is very significant. Perhaps for the same reason, the mark-point is not being generated correctly...  

FCR EROR.trk 1.18 MB · 3 downloads

 

https://youtu.be/-pe5v5jqgQg

[Frederf]

CZ, not FZ

[Mr. Wilson]

11 часов назад, Frederf сказал:

CZ, not FZ

I was mean CZ too )) sorry)

[Frederf]

Have you seen my track? It's an example of an FCR mark and mark was accurate.

[Mr. Wilson]

1 час назад, Frederf сказал:

Have you seen my track? It's an example of an FCR mark and mark was accurate.

thanks for the track, I'll watch and write

[Mr. Wilson]

20 часов назад, Frederf сказал:

It might be related to the above double-movement. That should only apply in FZ though. Another thing might be that you're not CZ'ing after selecting the new markpoint. This would cause initial cursor placement to be mark point plus previous slews.

Here's a track of an FCR GM mark involving slews. You see that when I select STPT 26 the cursor jumps away due to my existing slews. When I press CZ the cursor returns to the location that I marked.

F16 FCR mark and CZ.trk 39 \u041a\u0431 · 4 скачивания

I watched your track. But he doesn't show anything... 

You didn’t show the accuracy of the point, you didn’t even use the zoom, you didn’t use the weapon, you didn’t look into the TGP at the created point, you did not check the place where you put the point.

I showed in my track that the radar creates points in the wrong places with a very large error

Edited December 6, 2021 by Mr. Wilson

[Mr. Wilson]

17 часов назад, TEOMOOSE сказал:

What do you mean exactly ?

The markpoints working just fine. There's no issue with it.

Note: don't forget to clear the offset after you placed the mark.

https://youtu.be/-pe5v5jqgQg

The point that the radar generates does not coincide with the one that we see on the FCR page and TGP

[Mr. Wilson]

If we switch the radar to FTT mode while there is a page with mark-point on DED, pressing the TMS back command will reset the active sensor from FCR to HUD and also reset the FCR page on mfd and with the complete loss of the previous location...  

Is this the correct behavior or not?

[Frederf]

5 hours ago, Mr. Wilson said:

I watched your track. But he doesn't show anything... 

You didn’t show the accuracy of the point, you didn’t even use the zoom, you didn’t use the weapon, you didn’t look into the TGP at the created point, you did not check the place where you put the point.

I showed in my track that the radar creates points in the wrong places with a very large error

 

My track does. I probably moved too quickly. I also didn't make too much fuss about the precision as my slews were very large. I'll make another slower one. I never saw the Syria track because it requires that I own the Syria terrain to view it.

Be aware there is another bug related to the radar where it doesn't move the imagery properly until 1 or 2 azimuth sweeps are completed. The cursor will appear to "snapback" after slewing until the picture updates which makes refinement of the cursors more difficult to do precisely as it would otherwise be. The cursor placement isn't as it appears until you allow the radar to do 1 or 2 passes after the last time you slewed.

26 minutes ago, Mr. Wilson said:

If we switch the radar to FTT mode while there is a page with mark-point on DED, pressing the TMS back command will reset the active sensor from FCR to HUD and also reset the FCR page on mfd and with the complete loss of the previous location...  

Is this the correct behavior or not?

DCS radar doesn't do FTT mode fully yet. The TMS forward from GM/GMT/SEA produces a sort of middle ground freeze that I've seen documented for AGP-66 MLU radars. Proper "full" FTT completely blanks the display except for the target diamond and crosshairs and is in a B-scope format not PPI.

But to your question, with MARK DED page open, TMS aft should not change the selected marking sensor as it does. TMS forward should not record coordinates onto the next markpoint slot until the radar is already in the locked state. I.e. the first TMS forward from a searching GM radar would enter a track mode and only the second would record coordinates for the mark point. In this way the radar can be locked/unlocked any number of times without recording coordinates. Pressing TMS aft should have no effect on the mark mode as it is strictly a radar control input at that point. It should not change the marking sensor to HUD. The only way to do that directly would be to SEQ from FCR to HUD.

F16 FCR mark and CZ2.trk

Edited December 7, 2021 by Frederf

[Mr. Wilson]

Thanks for the track and excuse me for the pause. I have already received a correct result of the radar and found several reasons that bothered me earlier, but I am waiting for the next patch before writing new reports