Unity 2018.2.6f1 - Fatar error / Failed to initialize player when launching game

[Peter77]

Perhaps related to the following issue, which causes all sorts of odd errors and crashes:

Bug: 4GB limit to Textures in standalone build

This is a limit of the maximum file size for resources. Resources are packed into a single file during the build. The file contains a header and one of the fields inside the header is size, this is stored as a 32 bit unsigned integer, the limit of which is 4GB. There has been some research into changing the size property to a 64bit unsigned integer but it is not a simple task due to backwards compatibility. I suggest you look at using AssetBundles as an alternative, they are a much better way …

A quick test to find out, whether it’s related to the size limit, would be to resize a lot of large textures (inside Unity) to 64x64 pixels for example, replace large sound files with silence, etc. Just to make sure to get the build size much smaller in a short amount of time.

If the game works with these modifications, then it’s probably related to the linked bug. In this case you might want to look into asset bundles, to by-pass this Unity limitation, as suggested in the linked forum thread.