skywalker22

Indeed I have to apologize, you were correct. I completely forgot that emitters colored green mean that they are actually not active, as you also stated. And as you already figure it out with your test, HTS has an azimuth scan of APPROX. 120degrees in total. I did some serious calculations using angular functions stuff, and after that did some "meter by meter" tests in DCS to fine tune when the HTS sensors starts seeing emitters. And this is what I came up with: - horizontal aspect: 130deg (+-65deg) - vertical aspect: 111,4deg (+-55,7deg) So its not an actual circle what the sensor really see, but its a bit of an oval (cone).

Not true. Take the plane up in the air, and do a proper test, not from the ground. I did a test yesterday, I had 10 radars along one side of mine in the length of 80nm. I flew all the way near by them, and I saw at least 9 if not 10 constantly all the times, even behind.

This is just that: Thanks so much @Texac

DoF seems to still be an issue, I would say its more related to Nvidia (latest drivers v.531.68). Check this comparison pic. FPS hit is quite high, also cpu and gpu load is way higher using bokeh or simple type.

No HTS here, sorry, my bad. Fixed my post. Thx mate, still mixing these expressions all over the place, mainly I do it correctly, just type it incorrectly Do you maybe have any scan time results from the past, so you could compare the old and new ones?

There seems to be an issue for the HAS mode, its about scan cycle(s), they seem to be broken. Here is an example I just took: Issues we have atm: 1. there is no difference in scan timing according to selected Field of view (Wide, Center, Left, Right) 2. if all 5 radar threat emitters are selected, the cycle time is 5 seconds (if only 1 selected, cycle is 1 second) 3. note from the video: count down starting times 13, 22, 31, 40 and 49 and counting down for 1,2,3,4 or 5 respectively Question: do these reduced scan times really influence on detection time on emitters or not, specially compared to how it used to work before? How it used to work, you can check this WAG's video from cca 2 years ago, HAS had different, much higher cycle times and changing FOV did make a difference (now it doesn't). So, which is more correct, I don't know. That's why I am creating this topic, to find out, if current state is more correct, or there are issues.

My bad, I meant HAS mode. And I am sure the OP is talking about same scan timing. i did a short video of the issue we are talkin about.

FCR - main radar (but not for missiles). For missiles, for example, some of F-16 have AN/AAR-47 system onboard (not block 50 which we have in DCS), that the MWS toggle switch

The AN/ALR-56M RWR is not designed to directly measure the distance (range)to a threat. For this there are other systems onboard aircraft. Instead, it detects and analyzes the electromagnetic radiation emitted by the threat's radar system, and uses that information to determine the location and type of the threat. RWR uses a technique called direction finding (DF) to determine the direction of the incoming radar signals. This is typically accomplished using a combination of multiple antennas and triangulation. ps: current DCS version of ALR-56M works way more accurate then it used to be in the past, although it's less practical.

There is some issue with this app, it stops working by it self, and disappears from task manager, but the shape of it stays (just gray window). I have seen this few times by now. null I can also move this window around the desktop. If I start the app all over again, it opens another instance of the app (new windows), but I get this error warning dialog box:

yee indeed it was a dumb question, maybe there was really the crosswind influencing on plane's steering.

At that speed rudder cannot work properly yet. Rudder work at much higher speeds. But I also find it strange, why F-16 seems to steer into one side at all times while driving on the runway, I was always wondering why is that so. Why I just cannot go straight.

ASEC (Allowable Steering Error Circle) remain on FCR when going from A2A back to Navigation mode which is NOT OK, but it disappears from HUD, which is OK. It can only be rest if going into Dogfight mode and back to Navigation mode. Check the track file attached. f16_FCR_ASEC_issue.trk

Awesome news, really appreciate it.

Check this out:

Thank you for clarification. So there is a progress on the whole earth 3d model (as MSFS 2020). Amazing news.

Just wondering, if this has changed anything, with new maps, specially now with Sinai. Curvature plays quite an important roll in military aviation, check it out here:

I use analog axis on my throttle for zoom in/out.

If you use the ATC in F10 menu to land on any airport, you cannot use it again to take off from there. The traffic controller (the AI voice) only says to park and that's it. It seems that "the code" it does not resets. And if you want to take off after landing, you just have to do it without any ATC assistance. And that goes for all the maps and airfields. This issue is there since I ever. Would be time to fix it. When you land and park, there is just this message left:

Current taxi lights are very dim, you can barely see a thing, they are almost in no help. I doubt they are like so in reality. Here and here are videos which might help adjusting the brightness and a color. Taxi light and orange lines on taxi way, barely can see anything.

When it will be available to download? null

Remove all mods from current locations if you have any. Comms from F10 menus works just fine for me.

Oh, 18 means 180degrees, right? Straight towards you.

I would say that jumping threat on RWR is caused by RWR lost track with it. You did evasive maneuvers, and RWR came into a blind spot, that's why it lost track, and appeared again when RWR got a signal back. But strange was a moment when the threat appeared for a second on left side of the RWR, although it should be always on the right. -- Lets go a bit more in depth, using BVR missiles on the same example, and I did some evasive stuff to keep the fight going. Also mission file included. Now RWR seems to work even better then in the previous example (where AI was only using Fox2 missiles). Only question is, what kind of threats come into inner circle? @NineLine can you please explain if this is how it really goes, how it should go (as @Moonshineexplained well), or is somehow different? nails -> outer most circle - spike -> middle circle - active missile launched -> center of RWR f16_RWR_issue4.trk a2a_f-16_rwr_testing.miz

I did some more tests, using missiles. Now the threats go into the inner circle, but only when they fire a missile towards you. If this is ok or not, I don't know. f16_RWR_issue3.trk