if you can send either of those it would help too
I just mentioned 86 because Ive seen this and a few other references to it but the download link isnt working for me
if you can send either of those it would help too
I just mentioned 86 because Ive seen this and a few other references to it but the download link isnt working for me
thank you
looking at it again I believe the 84 one you mentioned was the one I am having issues downloading as its 84 edited in 86
are u gonna make a bug report on ACM or sth?
unfortunately I dont think one would pass as I know they’ve shot down at least one by saying the in game one is an early model
Considering the statement it should be a fair report now, since they won’t actually specify a configuration.
they claim that the in game one is a 1972 variant and use it to deny bug reports they disagree with
you just need to be short and state
acm is wrong
need change to this
this is for model ingame
model specifically ingame and match ingame description
the other guy yap too much
i know for a fact most bug report manager wont read everything
they only read general statement and sources, they dont read everything
they only read general statement and sources, they dont read everything
you mean they dont read anything and click “not a bug”?
you mean they dont read anything and click “not a bug”?
well i mean depends
tech mod would read most/all
non techmod would varies
is a 1972 variant
It can’t be, It would have access to the Pave Spike / Pave Tack and PGMs (GBU-9, -11 and assorted Paveway I & II, BOLT-117 etc.), the TISEO if it was, and use the ALR-46(V)1 not -(V)3
and circa '72; the GBU-15, was only refit to select DMAS aircraft in 1983, and the AGM-65B appears in 1975
Would it be worth it to report the erroneous PGMs then? If it’s both Sans DMAS. and held to a 1972 configuration.
Might at least get a lower BR or force a revsion.
I would if I didnt think they would use it as an excuse to get rid of them, drop it to 9es and leave it at the same br
drop it to 9es
We’ve at least got proof that, -9J’s were authorized for delivery to SEA on the 8th of June of 1972, so that at least should be fine to be retained.
But as per the “1973, F/C/D omnibus FM” AGM-65’s had not yet been refit to select older airframes(only added to newbuilds with block 48 and up at that point). That happened at some point between '73 & '90 and since with got a '72 configuration as specified.
They should be removed right?
We’ve at least got proof that, -9J’s were authorized for delivery to SEA on the 8th of June of 1972, so that at least should be fine to be retained.
I know that, but I dont trust them to try and say its representing early 1972 just to screw it over
They should be removed right?
id agree if they would add a later block with all the stuff it should have, as it is I feel like it is needed as CAS in its br range which it wouldnt be able to do if they removed mavs and GBU-8s
as it is I feel like it is needed as CAS in its br range which it wouldnt be able to do if they removed mavs and GBU-8s
Even if they did, it could still be replaced with a Targeting pod (Pave Spike) and assorted early LGBs so it’s wouldn’t necessarily be entirely losing access PGMs, just changing its options.
thats assuming they would add them, because pave spike was only from mid 70s, they could add pave knife and really early laser guided stuff, but thats still assuming they actually add it, given theyve refused all laser guided stuff for the f4e so far
, given theyve refused all laser guided stuff for the f4e so far
Likely because it had access to the GBU-15 & AGM-65 if it doesn’t anymore it will need replacements.
maybe? I dont remember their reasoning for all of that, but I wouldnt be too surprised if they still refuse it