You also need to set the managed stripping level to medium as this might also help in size optimisation.
Unity engine download size download#
When you upload the app to the Play Store, you can upload both builds, and the store will download the app with the architecture version of the user's device. If you need your application to support both ARMv7 and ARM64 architectures, you can create two separate builds with ARMv7 and ARM64. However, this will make the app work only for devices supporting ARMv7 architecture. You can also change your build architecture to ARMv7 to lower your build size. You can use the crunch compression value for compression, but that might not be very good for the original game quality on all the devices. For bigger model textures, you can change their max size from the image setting max size section. Doing this will save resources, and most images used throughout the game will be compressed to kilobytes in size. You should also prioritise 9 slicing for most images throughout the game. We need to do this because if the image's height/width is not a multiple of 4, the image cannot be crunch compressed or compressed to ETC2 format. When importing images or textures to your Unity project, always make sure to import the image with height/width having a multiple of 4 – like 128x128 or 256x256. Importing Images and Compressing Textures You can open the package manager from Window > Package Manager > Built-In.
You can also remove/disable them through the same package manager. You can search for unused packages through your project's package manager. So, when you compile your build, this specific 3D physics package might increase your build size by 2-3 MB. Removing those packages might contribute a lot to lessening your build size.įor example, you might have created a game that has no use of 3D physics but you could have unknowingly imported a 3D physics package into your project. When you create your project in Unity for the first, the engine might import some extra packages in your project as default that might be of no use to you. You can open the editor.log file in any text editor and find Build Report which will provide you with all details of what assets are being compiled in your build with Unity. Doing this will open your editor.log file. You can check what assets are being compiled by clicking on the 3 dots in your Unity console window. To avoid this issue, you should check and remove all the leftover assets from development that aren't used in your game. When this happens, even though the specific picture isn't visible anywhere in your game, the Unity compiler thinks that you are using the image even if it is disabled and compiles the asset into its shared assets. For example, you might be using a playerholder.png image in your development phase, but later, you might have disabled that image's game object in your project. While in the development phase, you might use many assets for your project, which can be of no use later in the production. The first thing above everything else regarding game size is the use of assets like images, sounds, scripts and prefabs. Cleaning Up and Removing Unnecessary Assets Properly handling unity scenes and use of runtime instantiationġ.IL2CPP Compilation and ARMv7 vs ARM64 architecture.Importing images and compressing textures.Removing built-in packages in your project that aren't being used.
In this article, we will be looking at some of the major factors that help in the size optimisation of a game. There are different ways of optimising a game and its size with Unity. Size factors can contribute to more user acquisition and can also affect performance. The game size is one of the key factors when developing games for mobile devices.
0 kommentar(er)
