The SAMP/T 'Mamba' - History, Design, Performance & Discussion

?

ASRAAM is not AMRAAM

yep i just remember they are not in game or in the file so i just denied theyr existance

@SP_Sabre can these bugs be considered new?
https://community.gaijin.net/issues/p/warthunder/i/cxQedp8vjXXh

Usually technical moderators would like for the report to be separate for each issue. You have 4 issues wrapped up in that one report.

3 Likes

should i switch it then?

if so i ll wait for some opinions,just in case they re already flagged…

Yes, each report should cover only one report, especially when the issues are so different from each other.

It also helps the moderators that pass the sources to devs a ton, since they need to share each issues one by one, separating the reports allow them to share them much easier.

1 Like

ASTER-30 TRK not working on small/medium targets // Gaijin.net // Issues

SAMP-T visual bug // Gaijin.net // Issues

SAMP-T command center bugged // Gaijin.net // Issues

SAMP-T unable to fire if one of the two launchers is moving // Gaijin.net // Issues

also by checking first report with the IOG screenshot,what even is the drag on these damn missiles

Ps. Tag the main user for bug updates

2 Likes

I believe last one is not really a bug because switching to a launcher actually only select its missiles and unselect the other launcher’s. Rest of them seems to be bugs tho. We’ll see if any get passed

Didn t knew about this “feature”, i always believed it gave that one launcher priority, not the complete lock of the others

Well, I believe this comes to the fact that selecting the radar module and firing will fire both launchers (so 2 missiles), and selecting a launcher will allow to only fit one missile.
However the SAMPT is my first experience with multi vehicle SAM and I’ve noticed that while using the radar it sometimes fires 2 launchers at the same time, sometimes only 1 and I don’t know why.

SAMP-T visual bug // Gaijin.net // Issues
Has been accepted

It’s designed to get as close as possible yes, it’s not hit to kill

No?

Yes? Name one that doesn’t? Also bring it to the 73 thread not here

Spoiler

This text will be hidden

image_2025-10-03_130132892
Sounds like it is to me?
That’s from MBDA

1 Like

Hit to kill would mean the missile is directly hitting the target, afaik aster has a proximity fuze, hit to kill is generally preferable against tbms and large aircraft, maybe the upgraded blocs foranti TBM capability are also hit to kill

It’s design as a hit to kill missile, but also features a relatively small warhead to ensure destruction in case it misses the target basically

Yes, that is my understanding of it
My point of my original post was to point out Gaijin added this missile without modeling one if its key features, lateral thrust, that helps with its hit-to-kill reliability. The warhead/proxy is so small IRL because its a backup. While in WT its the primary mode of killing.
They should add the full features… maybe that way drones wont be invincible at least

with all of these bug reports accepted, why are they not getting fixed

2 Likes

was it not suposed to be able to kill heli and low flying targets ?

Because atm, helis are a 50/50 hit/miss, and most of the time dont hit.
For low flying target, you can litraly forget the idea of even hitting them if they are 100m-200m above ground… it feels lackluster ?

or im playing it wrong ?

1 Like