skywalker22

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

Sorry, I did now thats from the same track.

ED, I think what guys are saying here are 100% correct. Just check this image, which means RWR in current version in USELESS! pic: each line represents one moment (f10 map and rwr situation at one point) I was really suspicious about RWR behaviour, specially on Sunday's TACT Persian Gulf mission , I just couldn't get any decent info from RWR, now I know why. Thx guys for all the contribution, I hope ED sees their error. And now I did this simple test of comparison real situation from F10 map, and RWR. And here is the strange result. There is no threat that EVER comes into inner circle. Strange, right? From so close distance that the bandit shots at me. f16_RWR_issue.trk

What are you saying, that lethality level depends solely on the distance? I assume you guys are only doing test against AI, right? You don't even know exactly how are they paint you in which mode (tws, rws, azimuth deg, numnber of bars) and so on. Lethality level depends also on more other things such as the type of radar or other emitter being used by the threat, to determine the level of lethality. Therefore, if two threats are emitting signals at different strengths, but one is using a more lethal type of radar or emitter, the AN/ALR-56M will prioritize the more lethal threat over the other. The point is, there is numberous of things that determine the level of lethality, and its far from being simple.

Man! You are the man. I never actually knew I can drop bombs later (closer to the target) when the max toss anticipation cue ends flashing. Everyone is telling & showing to start pulling up exactly into toss when that cue (circle) ends flashing. Your explanation was perfect! And I also now understand the whole concept. God damn, you saved my day, if not a year Tested, flew straight for 5 more seconds and then went into toss - and you won't believe, bombs went off my wings in my very 1st attempt. Finally one with some correct information. Thanks so much mate, I buy you a beer if we 2 ever meet.

Please try higher angles, you will see how hard, or more close to impossible it is.

At low altitude, does it also work at angles higher then 30deg (40,45, or higher)? Because to me it seem to be closer to mission impossible. @BIGNEWY I would strungly suggest that you try toss by your self, there is definitely something not right, please. ps: if you check my tracks, you can see there is nothing wrong with my technique, if it is, can someone please show/explain how it should be done correctly.

Look at this, it was almost perfect pull-up, and no bomb release. 45deg release angle. Almost mission impossible to release bombs over 30deg. f16_CCRP_toss_bombing5_45deg_NOT_OK_2.trk

I did some more tests, and the whole point is not to pull 4G, but to be at all time of the pull-up on the Horizontal bar (horizontal bar is the indicator of pull-up rate). What I also found out, is setting Release Angle up to 30, makes releasing toss bombs way, way easier (whole process is not as difficult and precise as when using higher angles). I also managed to release bombs at Release Angle of 35, 40 and 45, but its so damn hard, specially keeping the FPM on horizontal bar all the time of pull-up. So now, what can be wrong? If we suppose to have a constant pull-up of 4Gs, there is something wrong with the travel of Horizontal Bar indicator, because if you don't follow it, you will never be able to release bomb(s).

Since last update, CCRP TOSS bombing just doesn't work (again). Issue: flight path marker cannot reach the solution cue to bomb release. Did many different kind of tests (faster, slower G pull-up), but nothing seem to work (and with neither bomb). Note: I start pressing and holding the bomb release button just before going into toss (like Tricker explains it here). PS: I also tried same thing in DTOS mode, and the same result, not dropping bombs. And track files f16_CCRP_toss_bombing1.trk f16_CCRP_toss_bombing2.trk f16_CCRP_toss_bombing3_3_attempts.trkf16_DTOS_bombing4.trk

Correct. AIM-120C in BORE mode only looks straight ahead, so through the center of the HUD (missile diamond symbology).

Indeed insane details. I just hope optimization will be done properly, else we will need state of the art pc

FCR on off, launching AIM-120C-5 missile in BORE mode with a use of JHMCS, currently in DCS does not work either. Not even inside of 120deg (60 on each side from the bore line). Not sure if its a bug, or a work in progress.