Forum Discussion
@Falkentyne, I honestly don't know how Easy AntiCheat works (I wasn't involved in integrating that), so I can't speak to whether it's a factor.
I do think it's related to the actual instruction sequence, and possibly it's offset in memory. I can try making a standalone test program, that's a good idea. But it's not as trivial as you might think. This function does connect with the rest of our engine, so we have to sever those connections to make a standalone program, but we have to do it in a way that doesn't change the generated assembly.
If that doesn't work, I guess I could write an assembly language file that just has this function exactly as it is in the live game, and try to have external code feed it the data expects in a way that won't crash.
Another tricky thing is that the path through this code depends on branches based on what you can see in the game. If a particular path through the code is causing the bug, you'd need to replicate the live data that causes the crash. That data can be different for every viewpoint in King's Canyon, so even replicating all of the code may not replicate the crash if we don't replicate the control flow decisions. There are things we can try to force different control flows, but it's not guaranteed to repro.
Still, it's worth a shot!
I strongly advise everyone in here to revert their overclocking CPU settings back to default,
and disabling Intel SpeedstepTM in their BIOS.
I am pretty sure this has solved my problem as no longer do I have these crashes with logs.
Before it used to be all the time, now I can go for days without a single crash.
As I read here, since the problem was CPU related I tried different things.
But as mentioned over, im 99% this has solved my problem completely.
im using 7700k and 1080 ti, if any others at least try stock clock speeds and disabling Intel Speedstep,
it would be very interesting to see if the crashes are actually stopping.
- 7 years ago
My crashing stopped as well, I'm using an i9-9900K. I was stable at 4.7GHz (Turbo Boost) so I just introduced overclocking back and went to 4.8GHz to see if I'm stable. I'll report back soon.
About Apex Legends Technical Issues
Community Highlights
- EA_Blueberry7 years ago
Community Manager
Recent Discussions
- 52 minutes ago
- 5 hours ago
- 5 hours ago
- 14 hours ago