fixed RDR cursur not changing FCR range in F-16C block 50

[dutchili]

Before the April 17th update, we could change the FCR range by slewing the RDR cursor to the top or bottom of the MFD. The range would immediately change.

Now, the cursor stops at the edge. To change the range with the cursor, you need to move the cursor back away from the edge and try again. Then the range changes.

Seems related to the change log item: 'Fixed: RDR Cursor movement axis bug.'

@BIGNEWYIs the current behavior as intended?

 

I like the feature of not changing the range unintentionally while trying to lock a target at the current set range, but the behavior seems a bit incosistent now.

 

Not posting a track, assuming you have test scenario for this basic FCR operation.

Edited April 19 by dutchili

[sandpatch]

2 hours ago, dutchili said:

Before the April 17th update, we could change the FCR range by slewing the RDR cursor to the top or bottom of the MFD. The range would immediately change.

Now, the cursor stops at the edge. To change the range with the cursor, you need to move the cursor back away from the edge and try again. Then the range changes.

Seems related to the change log item: 'Fixed: RDR Cursor movement axis bug.'

@BIGNEWYIs the current behavior as intended?

 

I like the feature of not changing the range unintentionally while trying to lock a target at the current set range, but the behavior seems a bit incosistent now.

 

Not posting a track, assuming you have test scenario for this basic FCR operation.

For once, this is very specifically mentioned in the changelog: Known issue: FCR range and azimuth bumping using cursor can intermittently fail.

[TheBiggerBass]

Got the same error, but I don't know how the RDR cursor behaves IRL F-16. I guess chances are low we have a F-16 pilot here.

[LoudHoward]

I've been having it do the opposite much the time, whenever I move the cursor to the top half of the radar screen (from the bottom half) it zooms it out, so after a couple of attempts to bug a target I seem to end up at 160nm

[Furiz]

It's also changing scan azimuth on its own, before you reach the edge of the display left or right side.

[dutchili]

Noted that this is a known bug in this version. 

@BIGNEWYplease don't release known issues is key features of a module. We can't do without them.

[cesarferrolho]

Yeah, me and a friend, we can confirm, the cursor works worse than before. Both the range issue and azimuth as well

[dutchili]

Thanks @BIGNEWY for hotfixing this so quickly! (haven't tested yet, but already happy with the intentions)

[BIGNEWY]

4 minutes ago, dutchili said:

Thanks @BIGNEWY for hotfixing this so quickly! (haven't tested yet, but already happy with the intentions)

No problem, enjoy 

[cesarferrolho]

Yes, i can confirm, it's fixed. The cursor works well, like before the problems.

Thank you Eagle Dynamics !

[BIGNEWY]

thank you for confirming