Jump to content

Attack format TDC slew rate way too slow


Hulkbust44
 Share

Recommended Posts

https://youtu.be/Mn1sBfIlUjY?t=1152

This is the only evidence I have to bases this on, but the DCS TDC slew rate seems way too slow.
In this video (which is clearly not a lot 20 or even a charlie) we can see that the TDC is moved effortlessly around the attack format. While this is a completely different model, I guarantee that the later Hornets TDC slew rate never dropped to the level that we have in DCS. If it was that slow IRL the TDC bump functions would be almost pointless.

Here is Redkite's radar video 

Even at supposed max deflection has he slews the cursor from right to left I still seems to be three times slower that the real aircraft above.
This makes effectively using the TDC "bump" functions much more time consuming than they should be. I know DCS has the limitation of everyone not having the same hardware, but there's got to be something that can be done about this. 

I'm not at my PC so I don't have a track, but this has to be the most easily reproducible thing...

Thanks, 
Mobius708

Link to comment
Share on other sites

I agree. This is also quite noticeable when comparing to other modules (eg F-15C) where you can make fast movements if necessary and that looks much closer to what the real world video shows.

  • Like 2
Link to comment
Share on other sites

1 hour ago, Hulkbust44 said:

I know DCS has the limitation of everyone not having the same hardware, but there's got to be something that can be done about this. 

This is certainly a problem sometimes , but we have the ability to turn the sensitivity / saturation on any axis *down* if we want to. Having it be on the high side by default so that people can reduce it as needed would be better than it being too low I think. 

 

Of course things get more complex when a single axis controls multiple sensors with different slew rates. That's where things get crazy in the Hornet right now. TGT diamond slewing in the HUD is crazy sensitive while the RDR Cursor is downright sluggish. It'd be nice to get things leveled out a bit.

  • Like 4
Link to comment
Share on other sites

24 minutes ago, Bunny Clark said:

This is certainly a problem sometimes , but we have the ability to turn the sensitivity / saturation on any axis *down* if we want to. Having it be on the high side by default so that people can reduce it as needed would be better than it being too low I think. 

 

Of course things get more complex when a single axis controls multiple sensors with different slew rates. That's where things get crazy in the Hornet right now. TGT diamond slewing in the HUD is crazy sensitive while the RDR Cursor is downright sluggish. It'd be nice to get things leveled out a bit.

May be remembering wrong but I’m pretty sure in the JF-17 special options you can set the TDC sensitivity differently for the HUD, MFDs etc. something like that would be ideal.

  • Like 1
Link to comment
Share on other sites

May be remembering wrong but I’m pretty sure in the JF-17 special options you can set the TDC sensitivity differently for the HUD, MFDs etc. something like that would be ideal.
You can indeed. That'd be the best option for the Hornet as well, a coefficient for the HUD and another one for the displays. The slew axis can be left as is and the coefficients can simply multiply the input from, let's say 0.5 - 2.0. That'd be the cleanest way to deal with this.
  • Like 3

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

1197644828_Screen_200911_044202-Copy.png.74d8c09ee9060cffd7408a75ab2c13ef.png

HP Reverb G2, Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 32GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum

F/A-18C, AV-8B, F-16C, JF-17, A-10C (C II), M-2000C, F-14, BS2, UH-1H, P-51D, Sptifire, FC3

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...