PIXI Loader handling failed loads

[charlie_says]

This is more a question about how people try to do things rather than a problem with PIXI per se.

What I've found is, if I force the loading to fail (by turning off WiFi or similar) PIXI behaves as expected, an error event is fired, and then the game will play but with missing assets.

The question:

How do people gracefully handle the failure? 

 

Do you force the loader to start over?

Push the error items to an array and reload? (I think this one is good, but there's a possibility that you could get caught up endlessly in the game retrying);

Ignore it? (hey it's the internet, things break from time to time!)

Create an error screen, which has a link for the player to start over? (this is probably the best option.)

 

Thanks!

 

 

[ivan.popelyshev]

@xerver

[botmaster]

I try as much as possible to identify the problem, if internet is down I don't want my app to work anymore and I rather display an error to the user and quit everything. I usually have a fall back system with assets primarily on a CDN and a local fallback or relative fallback, if both do fail then I assume there's no internet anymore and I prefer to stop the app completely.

[xerver]

Depends on the asset. For example, if you need to load a map; and it fails, you can't play the game.

Generally what I've done in the past is catch all asset errors and if the errors were ones that a retry might fix (like a timeout, or 503, or some such) then retry those at the end. If I get a fatal error like a 404, I just show an error to the user and exit.

[charlie_says]

thanks for all the replies!