I know there are already some threads about this issue - but I couldn’t find any solutions. Some claimed, that this issue has been fixed with Version 3 - but we work with 3.1 and this bug is still there.
We are currently producing a game for iPhone and iPad. Since every device has its own display resolution, we are loading the textures dynamically from the Resources folder (resources.load method).
At first everything went fine (Building and Editor). For the final version we put all needed textures into the Resources folder (approx. 250 MB). In the editor everything works perfectly.
Unfortunately, the project won’t build anymore. Unity reports an “Out of Memory” problem and crashed shortly afterwards.
The problem can be reproduced. If we remove textures from the Resource folder, the project is building again.
We are building on a Mac (OS X 10.6.5) with an Intel i7 2,66 GHz processor and 4 GB of RAM and the latest version of Unity (V 3.1.0f4 iPhone Pro).
The “Out of Memory” problem with the Resource folder is discussed in this forum many times. Unfortunately there seemed to be still no solution for this. We have some really nice graphics in our game and we would prefer to not compress them to death (only to work around a bug in our chosen game engine). How many Bytes of graphics is Unity able to handle without crashing? And we haven’t even implemented sound yet…
How can we solve this problem? Any help is appreciated!