Forum Discussion

Aldebera's avatar
Aldebera
Seasoned Veteran
2 years ago

Latest update - new Crashes etc

Switch player here.  Yet another update, and yet another slough of crashes.  Previous complaints related to freezing of TDM, and other mixtape modes (S19 & 20).  Patches released in the previous season, and the latest season release seemed to improve the situation, however, it was not fully fixed.

Now the latest update is causing crashes, now typically in Lockdown.  If I get an error, it is now saying "code:clock" whereas before it was typically "code:leaf" or "code:cloud".  It is rare to get an error though, as the game freezes as you spawn, or about to spawn on the map.  These errors have typically appeared post game when returning to the lobby.  So it returns you typically to the initial splash / server selection screen.

Since I cannot review the source, it is difficult to analyse what is causing this issue, however, if I were to make an educated guess, I would surmise that there is cached data stored on the console that renders a session as basically impossible to engage.  I start the Apex Legends app, and it loads, but there are these freezing and or crashing events.  I have to do the most severe type of reboot to my console to resolve the issue.  This type of reboot, deletes all stored caches of all games, etc. The manufacturer notes that this should only be done when all other methods have failed, as it is hard on the system.

Surely, there can be a code written for application startup to refresh all data, rather than using old data that may not allow for effective sync with your servers?

I would also surmise that this code would be effective on other platforms as well, as I have seen similar complaints from players using other platforms.  

I would also suggest that if there is "old" data stored on your end, it is refreshed at application startup as a proactive measure as well.  Since the application requests precache, your systems are at some level aware that an application is being started up.  The problem seems to only manifest from startup.  It does not come into play if you are returning from "Disconnected Player" status where you are returned to the main splash / Server Selection screen.

I have also reported this issue to Nintendo Developers, in the event this may be caused by their operating system as well.  It is doubtful the issue is on their end though, as this would affect other games similarly (which it is not), however, it is worth reporting to them as well.

Devs are welcome to contact me directly if they want additional information.  They can DM me for my Discord if they wish.

No RepliesBe the first to reply