Main issue is the missile can still guide after that point its not an end all for the missile. Not to mention not all nations use multispectral smoke.
Depends how it’s modeled, and if you are still designating a target, that means you still have Line of sight so are exposed, and can only designate one target at a time(since buddy Lazing is not yet implemented).
Which defeats the point of Fire and Forget, especially if multi-modal seekers are not implemented solves the issue.
That can easily be abstracted as a “Gaming convention” and conferred to the generic defensive Smoke grenade, problem solved.
As otherwise the 66mm smoke launcher is used by all of the NATO nations anyway, so I don’t particularly see an issue there, extending it to the others for fairness.
I mean you don’t see people complaining that the RR-144 or RR-129 covers the wrong bands (or the Bloomed RCS is too high). And with the way RWRs are implemented it’s the band coverage that matters, not the actual Bandwidth of the system that is taken into account especially for edge cases.
As long as a radar could operate in the Bands an RWR could cover it will be detected.
A method I was always told when it came to KH-38s was to move behind cover like a house or rock or whatever, those same people could use their own advice to counter MMW
The main problem is the damage. With hellfire i can oneshot tanks easilly, i think it happens because hellfire has overpressure like high caliber HE shells, JAGM on the other hand has a lot less TNT filler so its damage is much closer to something like TOW-2 or Vikhr. So i think its better to bring Agm-114 to kill enemy tanks, but JAGM SAL is much better anti-heli missile.
Well small issue is they have no idea the missile is coming so that rules that off.
You should check the dev they updated the pen
Now all we need is proximity for both the 30MM and the JAGM and it should be peak.
the dual seeker mode as well, that will make it truly peak
I dont know about others, but i can live without it, mostly because im scared to think of the number features that will be broken when gaijin tries adding this one.
and? you have less time to react to a KH38MT than a JAGM, so still fine by their logic
I worry now that we have 16 gaijin isnt gonna give us proxy
at minimum we need it for the missile i can live without it on the gun
The 30mm proxy is probably a higher priority, as its got more chances to straight up no-sell incoming radar missiles, while the CIRCM handles IR threats.
HOBS on the missile would be nice sure, but is only really useful against Aircraft, due to the way existing proximity fuses are modeled as minimum distance fuses so don’t actually airburst like they should , and as such don’t confer a the benefit to the fragmentation pattern.
@Gunjob Can you explain this response please?
“The source does not contain any information about the use of these missiles on the AH-64E.
Reports like this require direct proofs, not guesswork.”
Legitimately, what did they mean by this? Do I need to make another report pointing this out, Do I need to go looking for proof that FIM-92A’s are no longer in US inventory, where is the Guesswork I’m being accused of? Gaijin are the ones that added the basic ATAS & ATAL to the AH-64E why would I need to provide proof that they are right?
Do I need to go back to my LW30 XM1121 HE-VT report and prove without a doubt that the AH-64 uses the M230 30mm chain gun, and that it does in fact chamber 30x113mm ammo?
I don’t know if they have eyes, but the ATAL is the Launcher that the AH-64 uses to interface with the unmodified Stinger missile AUR. And quoted from the report is rated for Basic, RMP and RMP Block I missiles with no modification
- Launcher Fires two Basic , Reprogrammable Micro-Processor (RMP) or RMP Block I Missiles; No Missile Modifications required"
Hell FIM-92A’s ceased production in '87, making the youngest missiles that a Production AH-64E, with ATAS carriage (the -V6) 2018 making the (production) missiles somewhere between 31-40 years old, and as implied with the refenced Stinger-SLEP, that FIM-92E, which began production in '95 and under went the SLEP starting 2014 to extend their Service life another 10 years, obviously don’t have a 30 year Service life. So why does it have access to the Basic FIM-92A ATAS?
That is a perfect and detailed bug report, I guess they don’t want the guardian to shoot down aircraft :D
The mods on bug report seem grumpy, they reject and approve whatever they want
Is there anyway we can make the devs fix the accepted bug reports? We have made many on the apache and some are fixed but most are just accepted and passed on
Not really, only by showing that many people “have the same issue” are they actioned fast assuming it’s not obviously game breaking.
Let’s just hope more people “i have the same issue”
My reasoning for the missile proxy was really for anti helicopter work because it would make the apache pretty deadly against other helicopters
Even with the 16km range of the jagm i fear it requiring a direct hit is still gonna make it iffy against helicopters vs other missiles like vikhr with proxy
Sorry mate, I’ll have to get back to you on this, I’ll have a discussion with the person in question.
Thanks, I get that may be reaching for the -92K specifically may be construed as further than is supported, but at very least the -92C or -92E is supported by the provided documentation.
And again it’s just to go to the Dev’s for final approval so it’s ultimately up to them.
Further, the Proxy fuse(M934E7) is a drop in replacement for the M934E6 legacy contact fuse.
" The STINGER Proximity Fuze and Warhead Body Assembly with Antenna will provide a near miss capability against UAS targets while maintaining all legacy fuze functions against standard STINGER targets. The procurement of the legacy configuration STINGER M934E6 Fuze and Warhead Body Assembly will be in direct support of active and potential Foreign Military Sales (FMS) case requirements.