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.
-
@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
-
@EuKeule if you are running DDR4-3600 on a 7th gen Intel chip… with XMP enabled in BIOS or setting 3600 frequency manually – that is, essentially, a brutal “overclock” of the northbridge bus – the part of the CPU that controls communication to/from RAM.
I’m not sure what the fastest DDR4 ram existed when Intel 7th gen launched, but pretty sure it was much less than 3600. (I’m surprised the system would even boot and be stable, that way, so this may not be your problem – but hey it’s easy to check.)
Download your mobo manual and it should say what the various supported RAM speeds are/were for that socket generation… go with the highest one that doesn’t have an asterisk or “OC” warning In you BIOS settings… disable XMP and set the RAM speed manually – or let the default SPD negotiation happen.
I think I have the same high-end Samsung DDR4-3600 that you do… and I had stability problems on 9th gen Intel Core i7. I ended up turning it down to run at 3200 MHz iirc… with water-cooled cpu block.
[Edit: I’m not sure how to read the CPU-Z output … if the “1071.3 MHz” on the Memory tab is accurate, then you’re probably fine… but definitely doublecheck the BIOS settings]
-
What……
I‘ve no idea what you are talking about. This System is untouched since (I guess) 6 years.Unbelievable. I will check your recommendation and make the changes.
Thanks for that. I will let you know the result.
-
@airtex2019
According to Intel the i7 7700k supports up to DDR4-2400
https://ark.intel.com/content/www/us/en/ark/products/97129/intel-core-i77700k-processor-8m-cache-up-to-4-50-ghz.htmlUsing DDR4-3600 with this CPU does not really make sense. Let’s see what @EuKeule finds out after loading the default / optimized BIOS settings.
-
@Seifer said in 4.37 killed the AMRAAM:
@Razor161 interesting. Does it happen only for him? Sp or MP? What is his hardware?
what i know is that the guidance code is using quite precise calculation manipulating quite small numbers especially at the end of guidance…
A calculation error could explain
however i fail to understand why a RElease exe would work and not a LTCG
-
wow @airtex2019 is right… that is extreme overclock on the memory side. Please disable XMP and report back.
-
@EuKeule said in 4.37 killed the AMRAAM:
no idea what you are talking about. This System is untouched since (I guess) 6 years.
Rest well knowing you have very expensive, very fast ram. It was probably crazy, needlessly expensive, 6 years ago.
-
The drop from 3600MHz to 2400MHz might be quite substantial.
I think you will probably need to find the balancing point of least performance drop while avoiding AMRAAM shenanigans.
Maybe drop to 3200 first and do some tests, then to 3000 if you still have issues, then 2666 and lastly to 2400 if there are still issues at 2666.
I remember someone in the FL discord also had some issues with BMS and OC’d RAM, not about AMRAAMs though.
-
@unkindled no, please, let him check stock first. Then if it works, try the other way.
First optimization rule: make it work first, optimize later.
-
@EuKeule Might also be an idea to look into updating your BIOS to the latest version, as you’re seemingly running on the one it shipped with (version 0604, released in 2016), and there’s a lot of updates released since (newest being version 1301, released in 2018).
These updates include system performance/stability fixes and updates to DRAM compatibility:
https://rog.asus.com/motherboards/rog-maximus/rog-maximus-ix-hero-model/helpdesk_bios/I know some are skeptical of BIOS updates, but I’ve had no issue doing it over the last 15 years (most being Asus motherboards as well).
Just thought it was worth mentioning.