Community Manager

Re: Engine Error: FS_CheckAsyncRequest

Our team is indeed working to get this fixed up. 🙂

The workarounds mentioned earlier are a few steps that may allow those affected to continue playing while the team is working to correct the issue itself, not as a replacement for a fix.

Repairing doesn't seem to have any effect on this particular issue as you've noted, so switching to DX11 or increasing your model detail so it's not using the low settings are two ways to potentially avoid this particular issue while it's being worked on, thanks for hanging in there in the meantime!

15 Replies

NoCureForFailur
2 years ago
Hi @EA_Mako, is there a fix ready? 🙂 Or will there be a fix with the new update in 2 days? Thanks in advance!
its-raijinmaRu
2 years ago
I know this might sound absurd, but I am getting the same error as anyone else on this thread but I noticed something. I tried with all different model settings, but the game always crashes when it tries to load the model of the 30-30 repeater. I tried to get close to one on the ground several times and as soon as it goes inside the FoV the game gives the error. I hope this helps in solving this because it is ruining my gaming experience right now.
its-raijinmaRu
2 years ago
@EA_Mako Checked at it several times and it is the 3030 repeater model that makes the game crash. this is not a joke.
GhostingGordo
2 years ago
How am I just now getting this issue, trying everything and nothing works??
GhostingGordo
2 years ago
@GhostingGordo 30+minutes of this *, just let me play man
BoogerRag
2 years ago
@GhostingGordo having the same issue. just started today after the new update. tried everything but it keeps crashing
662244662244
2 years ago
I have this error today when I open the rank game, this error is happening after a short update
Photon000
2 years ago
I've been playing pubs duo all day.
I haven't enabled DX12, and my models are set to high already, so I can't increase that.
Got the crash once on Olympus, twice on King's Canyon so far.
No one in my team interacted with any beacon scan. Just happened once when we were looting through Hammond Labs, once when a team pushed us outside containment, and once just after I died, next to Market.
Not sure what causes it, or what I can do to fix it. @EA_Mako
EA_Mako
Community Manager
2 years ago
Hi @Photon000,

Thanks for the additional details.

This is still being investigated, though if the current workarounds don't apply in your situation I'm afraid we don't have others to try at this time.

Thanks for hanging in there in the meantime.
Photon000
2 years ago
After verifying files in steam, I have not had the crash. It found one bad file. @EA_Mako
EA_Mako
Community Manager
2 years ago
Hi @Photon000,

Actually ran into this myself a few times last night, with the same fix of repairing through Steam seemingly doing the trick as well.

Glad to hear that helped out for you, thanks for the update!
Anonymous
2 years ago
Approved
Hey Yall,

So I have had the same issue, happened 3 times over ranked, now am banned for noone knows how much time due to this error and still even with the files thru steam it couldnt fix it.

I load the game, I drop down to play, 1 sec and i get the error, what else I can do to make it work?
KayJaded
2 years ago
Having the same issue, once last night and my first game tonight. Error.png and DxDiag.txt for reference.
DxDiag5_26_2023.txt106 KB
XHelperZ
Hero+
2 years ago
Hey guys,
So, it seems that a second instance of this issue has started manifesting.
Same error, different cause.
The DX12 issue is still being looked into, though it seems like they've got a patch ready.
Though with the recent update it seems like some players are getting the same error despite them playing on DX11 and whatnot.
It seems like this issue primarily happens when loading into a match, though it's possible that there are some other triggers.
This issue is also being investigated, though no ETA has been provided.
MoreJIa
2 years ago
@Photon000 i had 5-7 games, i mean i tried to play, but i crashed at least 15 times.
while the game was not launched i tried the verifying thing in steam and it helped.
the path is right click on Apex in library => properties => Local Files => Verify integrity of game files...