Jump to content

LST TADS Slew Behavior


Go to solution Solved by NineLine,

Recommended Posts

  • ED Team
Posted

Wags was in the widest TADS field-of-view when he engaged LST, which has a faster slew rate and only required a small transit time to the target. The videos you linked are under different circumstances with more narrow fields-of-view and greater slew distances. Not an apt comparison, and this is really splitting hairs.

Afterburners are for wussies...hang around the battlefield and dodge tracers like a man.
DCS Rotor-Head

Posted
19 minutes ago, Raptor9 said:

Wags was in the widest TADS field-of-view when he engaged LST, which has a faster slew rate and only required a small transit time to the target. The videos you linked are under different circumstances with more narrow fields-of-view and greater slew distances. Not an apt comparison, and this is really splitting hairs.

The second clip the TADS is stepped in one FOV, you can tell by the FOV marks. Also Wags on the second shot was stepped in one FOV as well.. so it is an apt comparison...

Posted
17 minutes ago, Raptor9 said:

and this is really splitting hairs.

Sorry if I seem like I'm splitting hairs, I'm not really.. I just want LST to be simulated properly. After seeing how IAT behaves I was hoping LST would perform more to specs.. it seems like it just pops onto the target which seems to me like corner cutting.

  • ED Team
  • Solution
Posted
12 minutes ago, JSpidey said:

Sorry if I seem like I'm splitting hairs, I'm not really.. I just want LST to be simulated properly. After seeing how IAT behaves I was hoping LST would perform more to specs.. it seems like it just pops onto the target which seems to me like corner cutting.

At this point I think that you should wait until it's in Open Beta and you can test, if you still think its wrong, you can make a bug report with the appropriate evidence. Make sure you are 100% sure the evidence you share is valid for what we are making though. Thanks. 

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Posted
Just now, NineLine said:

At this point I think that you should wait until it's in Open Beta and you can test, if you still think its wrong, you can make a bug report with the appropriate evidence. Make sure you are 100% sure the evidence you share is valid for what we are making though. Thanks. 

Will do, thank you

  • Recently Browsing   0 members

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