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

I fully expect it to be kept at the current level as a game convention for a long time tho. But who knows, maybe

1 Like

It is a who knows for sure, wasn’t multipath adjusted due to petition when Fox-3s were imminent?

You would be surprised. There would be those who did not. I met them on this forum.

Man, i dont remember what i ate for dinner yesterday, and you ask me about things from years ago :P

1 Like

It was, and I was one of the people pushing for the change.
Also, Gaijin has the ability in the code to give different missiles different MP heights, so one day we will see radar missiles with accurate MP.

1 Like

I think we just need more and more people to point this problem out to the devs. If enough people do this, then the change could occur and let’s be honest, we need that change otherwise these AAs will be useless because in 80% of the GRB matches, jets multipath all the time and if it flies at 50m of altitude and the AA cannot kill it, that’s outrageous.

2 Likes

Keeping you guys updated, there’s some reports that are remaining to be made :

  • ASTER 30 seeker (J band and notch gate)
  • ASTER 30 sustainer (still relatively unknown tho)
  • ASTER 30 kinematics (sources for that are given directly to devs without doing a specific report AFAIK, but it’s pretty wild, can still do Mach 4 some 50-80s after launch depending on conditions)
  • ARABEL radar : there’s direct values against different targets at different ranges.

Thanks to @Mulatu_Astatke @SP_Sabre and @DirectSupport for all the reports

9 Likes

ima report multipath

yes i’m stubborn

EDIT : nvm, @SP_Sabre already handled it, thanks Sabre !

2 Likes

careful now X)

you’ll find them on contemporary british ships >:D

Purely regarding the burn time, it seems Gaijin is correct, as shown by the following sequence

(sustainer activation at ~45s, burn off at ~49s). Although what’s a bit strange is that it seems there is a delay between booster cut off and sustainer activation, which doesn’t seem to be the case for every launch). Alternatively the video could be cut weirdly.

The energy problem seems to be more drag related.

1 Like

I’d have to imagine that in most situations the missile choses when to enable the Cruise Sustainer, that seems like the only way the missile can still reach M4 half a minute after the Main Booster is gone and reach 100+km of range.
It could even be that the missile coasts for the main portion of the flight, to save fuel for terminal guidance + PIF-PAF maneuvering if necessary.

WT can’t replicate this behavior afaik so they’d have to reduce drag a lot to make it accurate within the 40km NEZ it’s said to have.

2 Likes

That’s a good point indeed

So is this the best AA system in the game or what’s the status?

If Gaijin doesn’t sleep on the bug reports like they did with the Tan-SAM kai, it can be. We have to wait for the future dev server patches.

Currently the Buk is much better, both in radar and missile kinetics. To be seen how reports are implemented and devs continue to update the systems

1 Like

Monday passed. No report been actionned but none got denied either so guess that’s a good thing.

1 Like

Just thought about that a little more, and while it’s possible, the terminal dart would still be too draggy in game, because reactivating the dart “later” instead of after separation wouldn’t give it mach 4 again, at least not in its current state in game

Regarding things it can see it pretty much is.

It is… the cD of the missile is really quite high…

So to summarize, the main issue of the SAMP/T is:

  • Aster-30 having way too much drag
  • Aster-30 being way too sensitive to multipathing
  • Arabel not being able to detect past 20kms

I say these are rather easy to fix. At least it will still be much better than the poor SPYDER, which Gaijin straight up refuses to fix at all.

3 Likes