Jump to content

Recommended Posts

Posted

I'm still new to DCS, and I realize there's a 90% (prob higher) chance my issues are user-errors... But, I really struggle to get TWS to behave like the manual and related videos suggest it should. 

Main issue: I see several Track Targets and from what I read, I should be able to TMS Right to convert all those to System Targets (empty boxes).  That does not seem to work any time I've tried.

Sometimes a TMS Up with cursor over a Track Target will convert it to Sys Tgt, but not reliably.  And I can never TMS Right to cycle thru System Tgts, probably because I never have multiple, even though there are multiple radar contacts.

Ad a result, I find myself way behind when I'm in bvr.

Couple more questions, including how to achieve DTT, but I'll wait on that.

Thx for any help.

Posted
vor 1 Stunde schrieb Keith Briscoe:

I'm still new to DCS, and I realize there's a 90% (prob higher) chance my issues are user-errors... But, I really struggle to get TWS to behave like the manual and related videos suggest it should. 

Main issue: I see several Track Targets and from what I read, I should be able to TMS Right to convert all those to System Targets (empty boxes).  That does not seem to work any time I've tried.

Sometimes a TMS Up with cursor over a Track Target will convert it to Sys Tgt, but not reliably.  And I can never TMS Right to cycle thru System Tgts, probably because I never have multiple, even though there are multiple radar contacts.

Ad a result, I find myself way behind when I'm in bvr.

Couple more questions, including how to achieve DTT, but I'll wait on that.

Thx for any help.

Can you upload a track file of the situation?   This will help to identify potential user errors.

Posted (edited)

Ok. So I just completely failed at making a post. I had a bunch of images and an explanation but it all got lost.

Instead I made a short youtube clip to show what I mean. Please forgive my utter incompetence at making videos.

F16 TWS Datalink problem

Edited by Tenkom
  • Like 2
  • ED Team
Posted

folks please attach a short track replay showing an example, use single player and you can control the situation more, when you exit the mission you can save the replay during the debrief screen.

thanks 

  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

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

Posted
3 hours ago, Tenkom said:

Ok. So I just completely failed at making a post. I had a bunch of images and an explanation but it all got lost.

Instead I made a short youtube clip to show what I mean. Please forgive my utter incompetence at making videos.

F16 TWS Datalink problem

 

The example WITH data link is exactly what I'm experiencing. Cannot "soft lock" as Tenkom says. Technically I think that is actually meant to be turning a target track to a System track (using TMS Right). And therefore cannot cycle thru system track to select one to bug.

Posted (edited)

Here is a track.Datalink-issue.trk 

The difference: hollowed squares versus none hollowed squares after bugging the tracks in TWS

Datalink off: 1. TMS right long = RWS to TWS 2. TMS right short = white hollowed squares

Datalink on: 1. TMS right long = RWS to TWS 2. TMS right short = still fulfilled yellow squares

With Datalink on, you can't see anymore which tracks you have bugged because the yellow squares stay fulfilled, no hollowed squares anymore.

Edit: I don't know if this is right or wrong, but I am interested in the answer too, so I thought I might could help out. 😉

Edited by Nedum
Edit
  • Like 1

CPU: AMD Ryzen 7950X3D, System-RAM: 64 GB DDR5, GPU: nVidia 4090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal, OS: Windows 11 Pro, HD: 2*2TB Samsung M.2 SSD

HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts

HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick

Rudder: WinWing Orion Metal

Posted (edited)

Same.  It feel like it has never worked as instructed.

23 hours ago, Keith Briscoe said:

Exactly. I always ha e these filled yellow squares and tms right short does nothing.

I kinda want to trial the f18 and see if same thing happens. No idea if radars work similarly.

Little different.  General more reliable as you cycle through hits, but not datalink boxes.  Doesn't like to do that (yet?).  I suck at air to air combat with the Hornet.  IDK if it's just that the F-16 will always be my first love, or that the radar requires a bit more work so my head is in the cockpit more, or if the plane just straight up isn't as good.  It's probably me.

Edited by SickSidewinder9
Posted
On 11/3/2023 at 12:39 AM, Keith Briscoe said:

Exactly. I always ha e these filled yellow squares and tms right short does nothing.

I kinda want to trial the f18 and see if same thing happens. No idea if radars work similarly.

The hornet auto-boxes everything that it can detect. Then you cycle through them with the NWS button.

I think the hornet radar is generally more work but also potentially more effective.
It has much better detection range for one. But also you have a AZ/EL radar page that helps build SA enormously. You can choose to control scan zone manually or automatically while in TWS where the viper locks scan zone to the active target, the hornet can also do that if you wish.
The radar screen can get messy on servers with a large amount of planes and awacs. But you can always distinguish between targets that your radar can and cannot see.

  • Like 2
  • 1 month later...
Posted (edited)

This has been bugging me for quite a while, maybe a year. Today I accidentally found out what is happening with F-16 TWS and target management while using datalink/MIDS/TNDL

First just a small side note for those who still learn the systems. As famous Chuk's guide explains (huge thanks to @Charly_Owl for amazing work for the community 🙇) in Part 13 section 2.2 on datalink track types, datalink-provided tracks (red triangles) are correlated with FCR tracks in TWS mode and become yellow filled squares as track targets.

Transitioning all these track targets to system targets (empty yellow squares) is expected to be done with a single TMS RIGHT short press - this is what is documented in DCS guide, Chuk's guide and so on. But a single TMS RIGHT short does nothing if DL is ON (which is reproducible 100% all the time). All targets remain at track state, and it is not possible to use FCR TWS to shoot at multiple targets. 

However what works while DL is ON is TMS RIGHT short two times in a row (but not too fast) - track targets transition to system targets and simultaneously the closest target becomes a bugged target. Subsequent TMS RIGHT short will cycle through displayed system targets marking them bugged and allowing to shoot at them while in FCR TWS as expected. I haven't seen this double TMS RIGHT mentioned anywhere in docs or community videos, and wonder if this is a bug or expected behavior? When DL is OFF, everything works as documented/expected in FCR TWS - transitioning targets works with a single TMS RIGHT short.

Track attached with repro - first two targets (angels 6/7) where DL-provided + correlated, and single TMS RIGHT didn't work. I used double press few times just to show it works. Then I switched off MIDS/DL and went to next two targets (angels 33) in FCR TWS - first got them as search targets (small solid white squares) then in a while as track targets (bigger solid white squares), then with single TMS RIGHT short transitioned to system targets. Then with TMS DOWN returned back to TWS search and made transitions again, to show a single TMS RIGHT works as expected.

image.png image.pngimage.pngimage.png

 

image.png

F16-TWS-DL-NODL.trk

Edited by AndrewDCS2005
  • Like 2
  • Thanks 1
  • AndrewDCS2005 changed the title to TWS with datalink ON - TMS RIGHT does not work
Posted

After more time spent in TWS with DL ON, looks like sometimes (like 1 out of 10 times) TMS RIGHT does something - it picks nearest track target and makes it a bugged target, but does not support multi-target cycling/firing, so TWS is broken anyway. Something is not right here and seems to be specific to F-16 FCR TWS + DL since in other planes TWS works as expected.

Potentially many pilots engage multiple targets with TWS and DL - nearly every server has AWACS and I'd expect forums to be filled with bug reports about this. While there are few earlier threads around this exact bug, but otherwise surprisingly quiet.

Posted
12 minutes ago, AndrewDCS2005 said:

Potentially many pilots engage multiple targets with TWS and DL - nearly every server has AWACS and I'd expect forums to be filled with bug reports about this. While there are few earlier threads around this exact bug, but otherwise surprisingly quiet.

That fact makes me ask: have you removed any mods?  There are a number that are causing weird issues with the current patch.  Since it's not being widely reported I'd suspect a user specific issue on this one way or the other.

Posted
13 minutes ago, rob10 said:

That fact makes me ask: have you removed any mods?  There are a number that are causing weird issues with the current patch.  Since it's not being widely reported I'd suspect a user specific issue on this one way or the other.

I never used a single mod, and exclusively fly only clean DCS with store-bought/installed airplanes.

Posted (edited)
On 12/26/2023 at 1:26 PM, AndrewDCS2005 said:

This has been bugging me for quite a while, maybe a year. Today I accidentally found out what is happening with F-16 TWS and target management while using datalink/MIDS/TNDL

First just a small side note for those who still learn the systems. As famous Chuk's guide explains (huge thanks to @Charly_Owl for amazing work for the community 🙇) in Part 13 section 2.2 on datalink track types, datalink-provided tracks (red triangles) are correlated with FCR tracks in TWS mode and become yellow filled squares as track targets.

Transitioning all these track targets to system targets (empty yellow squares) is expected to be done with a single TMS RIGHT short press - this is what is documented in DCS guide, Chuk's guide and so on. But a single TMS RIGHT short does nothing if DL is ON (which is reproducible 100% all the time). All targets remain at track state, and it is not possible to use FCR TWS to shoot at multiple targets. 

However what works while DL is ON is TMS RIGHT short two times in a row (but not too fast) - track targets transition to system targets and simultaneously the closest target becomes a bugged target. Subsequent TMS RIGHT short will cycle through displayed system targets marking them bugged and allowing to shoot at them while in FCR TWS as expected. I haven't seen this double TMS RIGHT mentioned anywhere in docs or community videos, and wonder if this is a bug or expected behavior? When DL is OFF, everything works as documented/expected in FCR TWS - transitioning targets works with a single TMS RIGHT short.

Track attached with repro - first two targets (angels 6/7) where DL-provided + correlated, and single TMS RIGHT didn't work. I used double press few times just to show it works. Then I switched off MIDS/DL and went to next two targets (angels 33) in FCR TWS - first got them as search targets (small solid white squares) then in a while as track targets (bigger solid white squares), then with single TMS RIGHT short transitioned to system targets. Then with TMS DOWN returned back to TWS search and made transitions again, to show a single TMS RIGHT works as expected.

image.png image.pngimage.pngimage.png

 

image.png

F16-TWS-DL-NODL.trk 2.28 MB · 5 downloads

 

Thank you for bringing this up again. 😉

Yes, there was a thread months ago with the same hint for something is off with TWS as long using DL.

And (as one mentioned) it has nothing to do with any kind of modding.

The F16 TWS behaves "strange" since months, and we never got any report from one of the forum Mods.

Every F16 owner can show this "bug" flying the F16 Free Flight Instant Action Mission.

The new thing you found out is, you can bug targets with slow pressing 2 times TMS right. I have to test this.

Another part for me was, as soon I have tracked one target in TWS and activate AA mode after that, TWS has to be activated again, and with that you are not able to track any other target as the first one you tracked before you switched to the AA mode. 

F16 TWS is off with DL on. Doesn't work in kind of what is showing in any known document we have.

Edited by Nedum
  • Like 1

CPU: AMD Ryzen 7950X3D, System-RAM: 64 GB DDR5, GPU: nVidia 4090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal, OS: Windows 11 Pro, HD: 2*2TB Samsung M.2 SSD

HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts

HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick

Rudder: WinWing Orion Metal

Posted

@skywalker22 thanks but in your case there's no DL correlation - you simply have your own FCR in TWS pick the tracks. This works for everyone as expected, no issues. 

As thread says, the issue is only with DL-correlated tracks, quoting my root post above:

Quote

datalink-provided tracks (red triangles) are correlated with FCR tracks in TWS mode and become yellow filled squares as track targets.

To test this, add a E-3 or E-2 to your coalition, and let it provide you tracks over DL/MIDS from further away, before your FCR can detect them (you'll see red triangles). Then after your FCR picks the same tracks, they'll correlate with DL tracks and become yellow squares. Once you have yellow squares, try converting them to system targets with single TMS RIGHT short.

Posted

same problem for me. 
Tried with the instant mission fighter intercept.

Strange thing, TMS right works the first time i played the mission. And after TMS right is broken 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...