dutchili Posted March 2, 2022 Posted March 2, 2022 1) 3 targets visible on RWS scan (1 left, 2 right) 2) turn right into 2 bandits 3) switch RWS to TWS with the intention to create sytems targets for the rights bandits - expect targets to remain visible / appear after 1 scan - reality: targets are not visible on radar screen when pressing TMS right to lock al system targets, they appear out of nowhere some time later as system targets with one bugged target. radar targets not shown.trk 1
Frederf Posted March 3, 2022 Posted March 3, 2022 The reason the targets weren't shown was because your radar was aiming below them. They weren't detected in both RWS and TWS for approximately 45 seconds in the middle of the engagement. 08:00:10 target detected only once (RWS) 08:00:13 contact mark degrades into 1st stage history 08:00:26 last history contact times out 08:00:37 switched to TWS 08:01:01 detected and bugged track. Here's the exact same track but taking over and aiming the antenna a few degrees higher. radar targets not shown2.trk
Moonshine Posted March 3, 2022 Posted March 3, 2022 while that is true with the antenna elevation, there are currently lots of things wrong with contacts disappearing in TWS as well as Datalink in RWS, maybe its an unfortunate mix of both. one can only hope that changes rather soon.
dutchili Posted March 3, 2022 Author Posted March 3, 2022 @frederf Thanks for your reply. I watched your track. I noticed you make a 45 degree bank instead of 90 degree bank. I tested this and it helps to maintain track in RWS. @moonshine I am afraid you are right, because: - an immediate switch form RWS to TWS does not make the target re-appear on the rader screen in this scenario - switchting from RWS to TWS with the nose pointing directly at the targets, range > 20 nm, does not show targets - in TWS with targets visible, TMS right, sometimes have no effect until seconds later (>3 seconds) It is either buggy, or the radar is not really supportive of the pilot.
Moonshine Posted March 3, 2022 Posted March 3, 2022 both bug reports are commented as "reported" and i assume it will be fixed. just sad it might be open until the end of march as it makes the A-A stuff in the viper absolutely terrible for a total duration of almost 2 months.. but id rather have them fix it properly
dutchili Posted March 3, 2022 Author Posted March 3, 2022 Do you know if CCIP is also reported? I can't find the latest on that. I experience inaccuracy in both cluster and non-cluster bombs.
Moonshine Posted March 3, 2022 Posted March 3, 2022 (edited) is also reported as far as i know. gotta dig deep into the bug reports to find it, exists for a while now. if anything though, open a new topic instead of putting it in here to not mix topics. makes it hard to track bugs Edited March 3, 2022 by Moonshine 1
ED Team BIGNEWY Posted March 3, 2022 ED Team Posted March 3, 2022 Please do not go off topic in the bug reports. Keep the report for the users first post, already reported issue will be fixed when the team is ready. This particular track I am not seeing a problem as Frederf points out radar elevation management played a role here. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
dutchili Posted March 3, 2022 Author Posted March 3, 2022 @BIGNEWY: - noted: one topic onluy - What is the normal behavior when switching from RWS to TWS? Should track remains visible or is scanning required?
Moonshine Posted March 3, 2022 Posted March 3, 2022 16 minutes ago, dutchili said: @BIGNEWY: - noted: one topic onluy - What is the normal behavior when switching from RWS to TWS? Should track remains visible or is scanning required? when bugging a target in RWS and then switching to TWS the bugged contact should remain bugged and launch and steering infromation for your selected weapon will remain, however when not bugged, radar contacts will have to go through the promotion process in TWS
ED Team BIGNEWY Posted March 3, 2022 ED Team Posted March 3, 2022 I'm going to mark this as reported earlier, we do have an issue in TWS when bugging the targets and one will be removed, I am testing a fix for this currently. thanks 2 2 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Frederf Posted March 3, 2022 Posted March 3, 2022 4 hours ago, dutchili said: @BIGNEWY: - noted: one topic onluy - What is the normal behavior when switching from RWS to TWS? Should track remains visible or is scanning required? Radar is always making and maintaining tracks in either mode. It takes a few detections to make a track. If the track exists when switching to TWS then it will be displayed immediately.
dutchili Posted March 4, 2022 Author Posted March 4, 2022 then there is a bug when switching from RWS to TWS 2
Frederf Posted March 4, 2022 Posted March 4, 2022 It's one of the first things I tested and I found that tracks generated invisibly in RWS were immediately available as tracks in TWS when switched. In the first track the radar actually lost complete contact with the targets so there was no track in the background to be shown. The only thing that looked wrong is that TWS bugged the target on redetection practically immediately instead of showing a contact and then developing it into a track. But I don't know if the user was mashing TMS forward or something unusual at that moment or not.
dutchili Posted March 5, 2022 Author Posted March 5, 2022 It was unclear to me how the viper was responding to my commands. Previously it was just doing exactly what is explained in the video by Wags. Now it doesn't.
Recommended Posts