Guys, I've post version 2.1 at first post, primarily fixing the radar using this information and parameter:
Scan mode: +/- 25* horizontal, +/- 10* vertical (almost sure about the second one, the first one is just something reasonable bc I read it's 30* which is most certainly bullshit )
Track mode: +/- 60* horizontal, +/- 20* vertical - but still, scale goes up to 10* and beyond something like 15* it would be off screen - radar probably still wouldn't lose it as long as it is within head movement range (60/20), you just wouldn't see anyhing until you'd manouver your plane so it is back on screen
Also you'll need to move the target inside the lock-on gate (target must be below the upper horizontal line and above the lower horizontal line. These lines are adjustable using radar gain key.
cheers,
S3
You didn't read the conversation between me and DeJotPe, did you?
OMG I'm so stupid
I forgot to fix that post.
Anyway, checkout posts from #355 to #357
The +/-60* and +/-20* is actually 60* horizontal and 20* FOV (aka +/- 30* and +/- 10*) + me being stupid and failing at reading comprehension. That's hardware limit and it's the same for both modes.
Also, yea, as DeJotPe pointed out, the horizontal scale shows range in track mode, when 2 vertical range markers go over outside ring it's 10km and when they go over inside it's 5 km. As of what this scale indicates regarding bearing, I have no idea at this point. You may want to just go back to the previous version with just those +/-30* and +/-10* limit - unless you've got better source, bc you said you do have some source, and since you live in Vietnam (do you? Bc I have just shown my poor comprehension above XD) which also used MiG-21, it may not be less credible than mine.
Alternatively just send me the code and I'll try to fix the shit I've done myself XD
We really need someone who actually flown MiG-21 and operated Sapfir radar...
Anyway, at least scan mode has correct values
, although I noticed something strange regarding ranging but I have to check it further. EDIT: 0 km in scan mode seems to be near the outer optimal lock-on range marker (the horizontal line with a dot below it - at least I think it shows that, honestly I have no idea what this marker means but it sounds like a cool temporary name
), instead of at the bottom of the screen.