MYSE1234

Thank you very much! Yes, that is correct and they are simulated. You have a CW signal and a HPRF (>5 kHz) signal. Both of which should be fairly common to hear, specially the HPRF one. Here you can listen to both of them: CW CW.mp3 HPRF.mp3 HPRF HPRF.mp3 Not all units use signals that would use these two signals, so it's not like all locks will have the same one signal, and that all launches will have THAT one. It depends on the system.

It does the same thing there as what I've written above. It just takes the distance to the waypoint and places the far and close border accordingly. The side borders are always 20 degrees each side of the centre line. It's similar to the last image, just the waypoint is behind you, but the aircraft does not take that into account. It just does what it always does.

I think you have the wrong idea for how the system works. The times where it did not show anything on the scope is when you have terrain between you and the area that the B-scope is showing. So by having the displayed area in radar shadow you get a blank image, as the scope is only every going to show you the area (in distance) around the waypoint. In azimuth it's showing +- 20 deg each side at all times, no matter what, meaning you have to point the aircraft at the waypoint to actually see that area. I did a "quick" little illustration from the begin of your track, showing B1. The two images on top are straight from the radar scope, showing both A1 and A2 modes. The bottom left image is overlaid with the area that A2 will show, and on the on the bottom right you have that same area copied over and distorted to fit the square B-scope image. The "B-scope area" has it's borders as such: Far border: Distance to waypoint + 4 km Close border: Distance to waypoint - 6 km Left/right border: 20 degrees from the centre line Comparing the two right images show that they are practically identical with regards top the area that show returns. The gain is higher in the A1 image, but... Here's one that show that you're seeing pretty much, when you have terrain in front of you and what it does when you're not pointing the aircraft at the waypoint selected. The area inside the marked area does not have any returns and will thus not show anything on the scope in A2. In the A-A mode and the TA mode it does not do this however, which is why you say "...B-scope draws the terrain correctly" when you use those, it just shows the 1 -11 km area in front of the aircraft in those, and the same 20 deg sideways. No weird SAAB stuff going on.

I'm not quite sure I follow what you mean I'm afraid. A2 works at long ranges too for me, just need to make sure you have the appropriate range setting/antenna elevation, along with proper gain. Here's a ship at ~78 km (7,8 mil for the cool kids) distance. And a closer one. ~50km closer than the first one Between the two waypoints/ships. If you have a track showing the issue you're seeing I'll happily have a look at it.

What part of it? It being "centred" (it's really -6 km to +4 km around the WP being shown) on the waypoint is how it should be. The only issue here that I can see is that the pilot did not define any waypoints in the computer, something I very much doubt would be done IRL. And also that LS is not really selectable as a waypoint, but A2 is still working as it should. It's weird, but it is correct.

You wouldn't see the discrepancy then as they were near identical back when OB dropped. Only with 2.9 would you see a real difference as the AIM-9 family received new values with that patch.

This is not correct, Viggen uses the same AIM-9 missiles as any other aircraft in DCS does since 2.9. And I'm pretty sure the AIM-9B above is with updated values while the RB24 above uses the old ones still (not that they are in use tho). They used to have the same values, except for the proxy fuse which ED has incorrectly set to 7m, instead of 9m. From the changelog: New implementation of A2A missiles (by ED) for MiG-21 and AJS-37: R-3S, R-3R, R-13, R-13M1, Rb-24/24J, and Rb-74. Fixed inaccuracies in several versions of the AIM-9.

Since you asked. Available for download in the OP. null

Version 4.9 Added C-RAM Added the new Flap Lid and Tin Shield units

Version 4.9 Added C-RAM Added the new Flap Lid and Tin Shield units

It's the rotation angle that was set for the helipad by the mission maker. It makes it so that you can get the correct runway heading from the reference code. Only requirement is that the mission maker has rotate the unit so it aligns with the runway. The default rotation is 0, pointing directly north. Not sure why it's not 0.0 though, but I guess it's close enough..

The website not having an up-to-date ELINT database isn't really on HB though TBF. The positional accuracy could certainly be better though. I think it might be merging radars of the same kind together into a single super inaccurate box, if you get too much data. Like when doing circles around them. It's like "There a radar type X over here. Oh, now it's behind me, now it on my right." And so on. It just adds it into a huge mess of data. Is my theory of the crazy inaccuracies you get. How does it look if you just fly straight though them in a somewhat straight line? Preferably with TERNAV tracking too. The kneeboard stuff I've never used so don't know.

The Rb04 is working as it should altitude wise, so it's 100% on the SAMs as far as I'm concerned.

The aircraft has no way to actually move the switch itself. The switch to A0 is only done electrically, not by mechanically moving the switch to A0. To enable A1/A2 again you need to first go to A0 manually with the switch, and then select one of the two modes.

Excellent idea. Try this one out. It's got around half the thickness of the original lines. https://drive.google.com/file/d/13AgsKGXjg27iBHL-KBES6Eyg7CzlDZnk/view?usp=sharing

The illumination pattern does change between TAXI and TILL, but very slightly. The two landing lights are angled far too much downward, which render them close to useless when landing. I've estimated them (there's only one in DCS right now) to be between 6 and 10 degrees too low. They're pretty good at lighting up the ground below you if you have a wingman coming in behind you though. The issues above is as @Machalot mentioned is that the landing lights are missing the "glow" texture in front of them when on. And the fact they are angled down too much. TAXI TILL

Pretty sure they come out when you get the turn command to B1 in the HUD (and FLI37) after take off.

Only having LS set in CK is definitely going to cause issues in general as it's been broken the last 1.5 years. A2 (B-scope) is in the mapping mode only going to show you the area "centred" (in distance) around the currently selected waypoint. Which together with the issue above, is an issue. So without any waypoint selected (effectively what happens when you select LS currently) it doesn't have any range data, so I guess it breaks because of that. The 1km-10km scan range in front of the aircraft is for the terrain avoidance mode with the 15km setting. That is obviously not going to show as much as the normal mapping mode would though. The A-A mode however might be used for a similar, but better scan I think. It switches over when you fire the missile, and in A0 the scope is not displaying anything, it's just black. So it's unfortunately it's not that as the scope can be seen displaying stuff.

Just added a new livery to the download for those that want another Akktu stakki one to use. Enjoy!

@formaggio The issue is fixed with v3, now available for download in the mod thread. Thanks again!

Added v3 to add compatibility with 2.8.7. Available for download in OP

Copy that, will take a look soon™. Thanks for the heads up.

Version 4.8 Added F-15E Added high-pass filter for PRFs: Only PRFs above 300 Hz will be detected Changed a lot of other units for better accuracy

Version 4.8 Added F-15E Added high-pass filter for PRFs: Only PRFs above 300 Hz will be detected Changed a lot of other units for better accuracy