4.37 killed the AMRAAM
-
@Aragorn said in 4.37 killed the AMRAAM:
@Seifer said:
Except, perhaps, the size of your panties (although I suspect Aragorn will find it useful).
I already KNOW the size of his panties.
FFS - will you people stop underestimating me.
I have been stalking him for WEEKS.
Cause or consequence?
-
This is an ACMI of a TvT running on Falcon online as we speak
https://mega.nz/file/ELhC3D7S#rYmysDa1Vqaf4xAF7sQV9Y_yNOQNy4B2zcFdVAnydu0
out of the 45 missiles AHR type fired in a massive MP environment, none of them have shown any problem of guidances like the ones you guys have in your ACMI
i freaking dont understand it drives me mad
-
I will make the tests you recommended.
Standby… (weekend is normally family time, I’ve to negotiate with my president…) -
Tested with just the “if all above tests failed” new Misdata files only. All ok. No overclocking.
-
@EuKeule said in 4.37 killed the AMRAAM:
I will make the tests you recommended.
Standby… (weekend is normally family time, I’ve to negotiate with my president…)External view?
-
@WPNS24 said in 4.37 killed the AMRAAM:
Ok, now in all 100% seriousness with a reply of yes or no. I want you to say yes the slammer should hit or no the slammer should miss to this engagement.
I am clearing a Mig-23 off my wingman that is at 12k alt. I am at 25k and in a dive at .65 Mach and increasing, the Mig is at .71. The distance is 10.63 nm and I launch my slammer.
The Mig goes immediately cold and increases speed maxed out at mach 1.13, my speed has increased to .94 mach. Time elapsed is 57 seconds and slammer dies.
Mig knows missile defeated and turns hot toward me 12 miles in trail at 18k alt and .92 Mach. Mig is at 4000 ft and 1.13 Mach, turns hot at 4.4 G and loses 2 kts airspeed. Points its nose at me and sees another slammer launched again pulls a hard right at 9.9 G’s (losing 15 kts airpseed) and accelerates to 1.11 Mach in seconds again. At the point it turned cold again, my missile was 4.39 nm from the Mig and couldn’t catch it. The Mig just sprinted away until it finally turned back in AGAIN after the 2nd slammer missed and at this point I was only 6 miles away this time and finally killed it with a 3rd slammer…
Do any of those scenarios sound reasonable? Yes or NoLooks like the problem isn’t with Amraam.
The problem in the flight characteristics of some AI bot aircraft, allowing them to abruptly run away from any missile that was launched from afar. -
@LorikEolmin said in 4.37 killed the AMRAAM:
Tested with just the “if all above tests failed” new Misdata files only. All ok. No overclocking.
i’m confused , you were able to replicate the original bug (weird trajectories - avoidance at last second ) on the first place ???
-
@SpbGoro said in 4.37 killed the AMRAAM:
@WPNS24 said in 4.37 killed the AMRAAM:
Ok, now in all 100% seriousness with a reply of yes or no. I want you to say yes the slammer should hit or no the slammer should miss to this engagement.
I am clearing a Mig-23 off my wingman that is at 12k alt. I am at 25k and in a dive at .65 Mach and increasing, the Mig is at .71. The distance is 10.63 nm and I launch my slammer.
The Mig goes immediately cold and increases speed maxed out at mach 1.13, my speed has increased to .94 mach. Time elapsed is 57 seconds and slammer dies.
Mig knows missile defeated and turns hot toward me 12 miles in trail at 18k alt and .92 Mach. Mig is at 4000 ft and 1.13 Mach, turns hot at 4.4 G and loses 2 kts airspeed. Points its nose at me and sees another slammer launched again pulls a hard right at 9.9 G’s (losing 15 kts airpseed) and accelerates to 1.11 Mach in seconds again. At the point it turned cold again, my missile was 4.39 nm from the Mig and couldn’t catch it. The Mig just sprinted away until it finally turned back in AGAIN after the 2nd slammer missed and at this point I was only 6 miles away this time and finally killed it with a 3rd slammer…
Do any of those scenarios sound reasonable? Yes or NoLooks like the problem isn’t with Amraam.
The problem in the flight characteristics of some AI bot aircraft, allowing them to abruptly run away from any missile that was launched from afar.when you suddendly see a <M> on your RWR, do you turn max G and full AB or do you continue flying peacefully ?
-
@Mav-jp
I aggree with you that so far no other flight was affected by this issue. Not in dogfight module nor in other TE’s or campaign flights.
It looks like the problem only occurs in this TE with Mustang6 flight. As @Prot explained he did stuff with MC to clone flights and so on.Could you check if anything in the TE is ‘broken’ or at least not as it should data-wise?
-
@Mav-jp Of course, i would have run away if he saw “M” on the RVR But running away and maneuvering sharply, i would have lost a significant part of his energy during maneuvers. But the MiG-23 cannot see the “M” on the RVR
In the situation described above from WPNS24, the MiG-23 almost does not lose energy while maneuvering and accelerates very quickly.
If I understood his message correctly, of course.
-
@Mav-jp said in 4.37 killed the AMRAAM:
@LorikEolmin said in 4.37 killed the AMRAAM:
Tested with just the “if all above tests failed” new Misdata files only. All ok. No overclocking.
i’m confused , you were able to replicate the original bug (weird trajectories - avoidance at last second ) on the first place ???
No, it was all ok.
-
@LorikEolmin asked:
Cause or consequence?
Consequence.
But - had I known beforehand - for sure would have been cause.
Dude has an AMRAAM.
-
@SpbGoro said in 4.37 killed the AMRAAM:
@Mav-jp Of course, i would have run away if he saw “M” on the RVR But running away and maneuvering sharply, i would have lost a significant part of his energy during maneuvers. But the MiG-23 cannot see the “M” on the RVR
In the situation described above from WPNS24, the MiG-23 almost does not lose energy while maneuvering and accelerates very quickly.
If I understood his message correctly, of course.
What do you mean the mig23 cannot see the M on the RwR?
-
@LorikEolmin said in 4.37 killed the AMRAAM:
@Mav-jp said in 4.37 killed the AMRAAM:
@LorikEolmin said in 4.37 killed the AMRAAM:
Tested with just the “if all above tests failed” new Misdata files only. All ok. No overclocking.
i’m confused , you were able to replicate the original bug (weird trajectories - avoidance at last second ) on the first place ???
No, it was all ok.
Okay then no need testing for you
-
@Mav-jp said in 4.37 killed the AMRAAM:
What do you mean the mig23 cannot see the M on the RwR?
SPO-15 “Birch” from the 80s - does not display the symbol “M”. Displays only: Direction, emission of radar groups, radar acquisition, launch.
-
@SpbGoro said in 4.37 killed the AMRAAM:
@Mav-jp said in 4.37 killed the AMRAAM:
What do you mean the mig23 cannot see the M on the RwR?
SPO-15 “Birch” from the 80s - does not display the symbol “M”. Displays only: Direction, emission of radar groups, radar acquisition, launch.
The aim120 pitbull is a radar emitting
-
here we go: Link to GDrive
Test with the changed Falcon BMS user file:
2023-02-04_08-43-16_Alpha_SP_setup1.zip.acmiTest with changed MisData part 1 and original Falcon BMS user file:
2023-02-04_09-56-18_Alpha_SP_MisData1.zip.acmi
2023-02-04_14-14-05_Keule_SP_MisData1.zip.acmiTest with changed MisData part 2 and original Falcon BMS user file:
2023-02-04_14-51-09_Keule_SP_MisData2.zip.acmiThe result is always the same: The missile drives totally crazy at the endgame.
Additional information:
I’ve a dedicated PC only for BMS with Win10, Falcon BMS and some necessary tools to drive my pit. No VR! -
@EuKeule said in 4.37 killed the AMRAAM:
here we go: Link to GDrive
Test with the changed Falcon BMS user file:
2023-02-04_08-43-16_Alpha_SP_setup1.zip.acmiTest with changed MisData part 1 and original Falcon BMS user file:
2023-02-04_09-56-18_Alpha_SP_MisData1.zip.acmi
2023-02-04_14-14-05_Keule_SP_MisData1.zip.acmiTest with changed MisData part 2 and original Falcon BMS user file:
2023-02-04_14-51-09_Keule_SP_MisData2.zip.acmiThe result is always the same: The missile drives totally crazy at the endgame.
Additional information:
I’ve a dedicated PC only for BMS with Win10, Falcon BMS and some necessary tools to drive my pit. No VR!it’s not a question of “end of the game” the first missile you fire in
2023-02-04_14-51-09_Keule_SP_MisData2.zip.acmi
is already busted and does not fly as it shouldwell i’m sorry to say that i am totally out of ideas
i can’t reproduce and neither can the people from TvT for now
-
Okay
i have another crazy idea :
could you set up your MIG29S in your database (both KOREA and BALKAN without CHAFFS and FLARES)
nChaff 0
nFlare 0in Mig-29S.dat in both balkans and KOREA
-
@Mav-jp said in 4.37 killed the AMRAAM:
Okay
i have another crazy idea :
could you set up your MIG29S in your database (both KOREA and BALKAN without CHAFFS and FLARES)
nChaff 0
nFlare 0in Mig-29S.dat in both balkans and KOREA
(why both? Want to rule out potential erroneous use of KTO files?)