Moonshine

Interesting topic, however to get back on track with this post, we should probably move the RWR discussion into a different part of the forum, as its not part of the amraam bugs

i mean, just because the missile doesnt see the target anymore (thats the notch for you), does not mean the RWR does not detect radar emmissions from the missiles radar. but i assume the frequency of a missile that is actively guiding is different from a missile that is searching (same with radar spikes or just nails), PRF changes and the RWR detects that, hence it knows if something is just looking or guiding. (im sure someone with more knowledge can explain that better than me lol)

i see what you did there sir also yes it is true, the times arent synced when cold starting, really hoping for this to get changed / added maybe with the work on the TIME page and the various other DED pages we still are missing. (at least for the missions set in years after the GPS implementation)

Fine, guess we are splitting hairs now. The title is like that because thats what the initial thought was. The „TMS not working“ title is the result of the range issue. At no point was bugging something so delayed in RWS in the past, now suddenly, with no information about any radar changes this is what it is now? Of course people start to wonder if their hardware is broken or if TMS suddenly doesnt work anymore because we cant get a solid radar contact promoted to a bugged contact. Besides the point that the way it is behaving now can hardly be „correct as is“ i mentioned towards the beginning of this thread that it is describing the same issue explained in the other post here and should probably be merged..

lol this is ridiculous

did a quick test, both cold started and airspawn. ofc make sure you got the pod and the left hardpoint is powered no issues in both scenarios HTS_Airspawn.trk HTS_Coldstart.trk

Do you guys have any track replays of this? It might help finding the issue if there is one. I have not had any problems when i used it after the latest patch but i have not flown a lot

lets not forget these posts that were created pretty much after the release of the new missile API. : this one is even tagged as reported, no news since then: then there is also these: should be enough material in addition to what came up in the last 2 days...

While prior to the latest patch you couldnt bug anything in TWS for a very long time despite having contacts promoted, therefore solid tracks, it seems that the same functionality has been moved over to RWS. At least dont label this post as „correct as is“ if clearly it isnt. Along multiple posts people have been sending in tracks and even PMs highlighting the issue at hand, as reported here as well. I doubt there would be so much attention on the formus all around to this topic if it were a minor issue. Again i want to reference to this post, as it highlights the same issue; https://forum.dcs.world/topic/299740-dcs-f-16cm-apg-68v5-look-down-issues-and-also-weird-aim-120c-behavior/

is reported here:

Sorry but "i've seen a tv episode..." is never a good baseline to build an argument on. i bet if its true that there is flight instructors and weapons instructors within the group the OP mentions, their knowledge will be more fact based than a TV episode. with answers like this the post is dragged into the depths of the DCS forums again and no one will look at the very core issue the OP wanted to shine light upon. a lot of us here do not want this post to be locked due to going off topic too far or being just a standard internet argument.

added track. as you can see, the red DL contact is filled out (so my own ship radar has contact) at around the 40nm range (this seems reasonable), and the brick is visible below the red contact..weird that one. then i try to bug it with no chance for a solid 5 seconds, only getting a bug when the target gets within 32nm. multiple people have now reported the same issue in various posts, most notably this one: in the track as well as the videos of the linked post you can observe the same issue very clearly. Video 1 of the above linked post at the 1min mark for example. RWS_Bugging_Contact_issue_2.trk

ran the track again, here is the log as NL said, there is some sort of blinking happening which looks like it drops the lock, not sure if the lock really drops or if its just a symbology shenanigan and the lock is kept throughout. dcs.log

downloaded his track and ran it on my end, no mods, latest public OB version, same result as OP. as he bugs the first contact and fires, the lock drops as you can see from the symbology. this happens 2 more times before he then switches to the second contact to engage. after that, the locks are held with no issue. maybe run it with the exact same OB version as the one we report the bugs from and from which the trackfiles are created? if its no longer an issue in an internal build, one can only hope that this makes it into the next patch then, alongside the other radar threads

okay. getting consistent lock ranges of 30-32nm against any fighter size aircraft. guess thats the "expected" range... feels rather underwhelming at least they arent stuck in place anymore. thanks for that

Track Attached. as you can see, i am spamming TMS UP as soon as i get radar return, but cant get anything to bug for a long time. then within 20nm it finally works, so im trying to lock the second guy up in DTT, same issue, cant get him hooked. im happy with the DL contact finally not being stuck anymore but with a radar like this where you now cant even lock something up within useful ranges, it is arguably even more useless. sorry for the harsh wording, been a while that the Vipers radar is a pain to work with. RWS_Bugging_Contact_issue.trk

This. Can get radar returns (bricks) but cant bug for a long time as described above.

as Bignewy said, providing a track replay will help find and track down the issue. in addition to that, make sure you are not running any mods and see if the issue presists. this way bugs will be found and reported the easiest. i havent had any issues with JSOWS so far but its been a while since i used them last.

never had this happen in all my hours of flying the viper. got a trackfile or video that shows this? are you using any mods? if so, uninstall them and try again

This is the same issue reported here already:

not to mention the fact that the DL cuts out (at least wont get any blue icons on the HSD for your own flight) when the plane has a different Date than the mission. Happens on marianas quite often as the shift in timezones is around 12 hours from Zulu to local, therefore the mission will have a high chance of having a different Date than the aircraft (or when flying around midnight local time). However, datalink can only update the position of friendly units if the AWACS can actually see them. so in mountains and through valleys, DL might be outdated until the aircraft gets out of the terrain again edit: found the bug report

all the issues have been reported with trackfiles too and also been flagged as such. hoping to see some progress in the near future

he is talking about this: this: this: so all in all lots of things with the radar modes that do in fact limit its usefulness and force pilots to workarounds for these specific issues at this point in time. in RWS the contact gets stuck upon break lock so to fix that, just use TWS. however in TWS you cant bug anything until close to R max whereas in RWS you can get a bug as soon as he appears on the B-scope. and then the antenna elevation does not match the numbers shown next to the radar cursor so you have to first either switch radar mode or move it quickly over the edge of the B-scope to show the correct numbers again. i guess thats what he meant with "radar does not work all too well lately"..

already reported here: