Forum Discussion
@Falkentyne, thanks for the confirmation!
As for Intel acknowledging the hardware flaw... I personally doubt that will ever happen. They weren't that interested in looking into it for us without an easy repro. And you saw how they dismissed your report with "it's their software problem, our CPUs are great" (to paraphrase). My skeptical self thinks they are a large corporation that would see admitting a rare flaw as only harmful to themselves.
So, we called them out a bit in our patch notes, but I doubt it will go any further than that. Which I think is a shame, really. They had a repro case to find and fix a flaw in their designs, even though it rarely triggered. Looking into it could make all their future CPUs even more solid.
But even if Intel does fix this flaw in firmware, I'm glad we have a proven workaround. I expect that most people don't bother updating their CPU firmware, unless Microsoft forces it on them with an automatic Windows update.
I did leave a way for the game to run the old code that would crash Intel chips, but I didn't investigate whether the compiler generated the same assembly. You can get the old C++ code with setting "old_gather_props" to 1 in the console, or by passing "-force_old_gather_props" on the command line. I'll hit up Intel again and see if they care to fix this; if they don't, I'll remove the old behavior in a future patch.
Thank you.
Tried the command line launch parameter and the errors are back! 🙂
5 minutes of play at 1.270v, LLC6, 5 ghz:
A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 11
The details view of this entry contains further information.
(How do you open the console anyway?).
- 7 years ago
To developers:
About the problem in the lobby "The team is not ready" When a check mark is not set and your team starts without you, do the developers know?
I tried on different systems and on different hardware, with different Internet and different processors, from the whole team I have such a problem. I think on some part of windows, maybe an update package or some kind of video driver module.
Another problem is:
In the settings of the video does not go to make the quality of the models to low, put back to highIt feels like after the end of the match the lobby doesn’t get to the end, if you stand in the lobby for a long time before the match, the problem with checkboxes appears again, you have to leave the team and come back. The solution to the problem, I think will be adding the function "Restart Lobby"
Sorry for writing to you, I don’t know how else to write 🙂
- OrioStorm7 years ago
EA Staff (Retired)
@Falkentyne thanks for proving that the bug happens if we don't change anything!
I'm actually not sure if we ship the console in the retail game or not, or if we ship it disabled and you have to do something to enable it. If it's shipped and enabled, you press the ~ key to open it. If it's not shipped, you can only access it indirectly through the command line or possibly config files.
- 7 years ago
@OrioStorm what's interesting is that the GAME hasn't actually crashed yet.
It's just triggering CPU Internal Parity Errors and correcting them, but not crashing (yet).
I think the compiler possibly changed something also.
It's acting like the original pre-pre patch, when I was getting parity errors but almost never crashes (rare).
then the patch after that (where you started doing logs) it crashed a lot more often.
But this is just random guessing, left to the realm of programmers.
About Apex Legends Technical Issues
Community Highlights
- EA_Blueberry7 years ago
Community Manager
Recent Discussions
- 3 hours ago
- 4 hours ago
- 4 hours ago
- 7 hours ago
- 11 hours ago