4.37 killed the AMRAAM
-
@sungad said in 4.37 killed the AMRAAM:
@VIPER-0 said in 4.37 killed the AMRAAM:
if you want a headache, work with a SPO-10
I never understood why the Soviets the most important instruments their faces were the smallest, let’s say in spo-10 it is small like the face of a wristwatch, like the hydraulic pressure indicator on the booster and main systena. but other instruments such as the ash-1 clock, their dials are the size of a frying pan lid. The same in the transport avacion the torque meter that indicates the power that the engine is generating is just as small.
-
@VIPER-0 Priorities of course…
-
@WPNS24 - you know, after sleeping on this observation a couple nights, I have to ask - aren’t the AI bogeys subject to the same blackout/redout model that us Viper drivers are?
Seems to me that this bogey should have blacked out at the very least…and broken his jet…resulting in “a kill’s a kill”.
What the hey?..
-
@Stevie see other thread on bogey/wingman G forces … they’re an illusion
-
@Stevie ikr. I have a few acmi’s I’m going over to get to Mav about the acceleration rates and such
-
@WPNS24 said in 4.37 killed the AMRAAM:
@Stevie ikr. I have a few acmi’s I’m going over to get to Mav about the acceleration rates and such
I m not interested in ACMi
I’m interested in repro cases
-
@Mav-jp copy
-
@WPNS24 this is bad yep i agree on this i saw it too.
-
TacView 1.9.0 is out and just curious if the improvements make the tapes you all have more accurate or not.
-
I can confirm, the AMRAM ist dead…
It started with U1 and continued with U2. The missile drives totally crazy in the endgame.Take a look to the ACMI at the missile I shot (KEULE) at 00:54:15, or enjoy the video!
Here is the Link to my GDrive : LinkIt is the craziest move of an 120 I ever saw.
-
@EuKeule said in 4.37 killed the AMRAAM:
I can confirm, the AMRAM ist dead…
It started with U1 and continued with U2. The missile drives totally crazy in the endgame.Take a look to the ACMI at the missile I shot (KEULE) at 00:54:15, or enjoy the video!
Here is the Link to my GDrive : LinkIt is the craziest move of an 120 I ever saw.
There is no missile launch at 54:15…
-
The only thing I see in this ACMI is the sort of trick shot that we see at 15:54:30…
Now, the way I see it, the enemy goes back into the missile vision range and it has enough energy to follow him down…
Not obvious to say it is problematic IMHO.
-
@MaxWaldorf
We had a look at the ACMI in yesterdays debriefing and every missile that was launched by @EuKeule showed ‘glitches’ in tracking. The most funny one is what you see in the video. -
@Razor161 interesting. Does it happen only for him? Sp or MP? What is his hardware?
-
@Seifer
As far as we know he is the only one who is left with this issue. It happens in SP and MP as well.
We had another one in our squadron who had the same issue. It turned out he had a faulty RAM installed. Replacing the RAM fixed these ‘glitches’ for him. We’re now discussing (internally) if the behaviour if the missiles and the AI opponents is what we would expect. Stay tuned.
Anyway… @EuKeule did a check of his RAM and didn’t find any errors. So we’re a bit lost here. Any help for him is welcome. -
@Razor161 you see, when something like that happens only to a group of people, we need to rule out some possibilities before doing SW investigation. In this case, since it happens just to one person, we really need to rule out a HW issue. A memory stress test may not be enough.
I need details here anout his HW. Specially if he is overclocking, even if XMP.
We must work together to understand what is going on.
-
@Seifer
The first time this problem occur was with the U1 update.
I doesn’t matter witch theater, or if I fly SP or MP. Deploying the 120 ends up with this strange behavior in the endgame. So BVR with AMRAM makes no sense for me anymore.
(maybe I become a striker now… )
I had a longer conversation with @Mav-jp about this topic. He provided a “new” EXE for me that fixed the problem (of course only on my pc, not MP capable). I guess the EXE was compiled on another way… but I’m not a programmer. Maybe he has more information about it. So my big hope was that with U2 the problem was fixed.My PC is dedicated only for flying BMS (since years without any issues).
Windows 10, BMS, and some tools I need to drive my full-scale cockpit.
No OC or something like this.On my GDrive I provided some HW information (as pictures) that maybe help.
If you need more or other information please let me know.
-
@EuKeule please, tell your specs. Which processor, GPU, memory speed (XMP?) etc.
-
As I wrote in the post before:
You will find all on my GDrive! -
@EuKeule said in 4.37 killed the AMRAAM:
with @Mav-jp about this topic. He provided a “new” EXE for me that fixed the problem (of course only on my pc, not MP capable). I guess the EXE was compiled on another way