Drawcall optimization.

Unity3d supports mobile platforms, but sometimes applications developed using unity3d and games running on mobile terminals have obvious efficiency problems, such as card and image quality. I occasionally get what I do when I develop games. Summarize the main factors that affect performance.

 

Main factors include:

1. The saved by batching value is too large ----> this value is mainly for batch processing of mesh. The higher the value, the more stuck the application will be.

2. The drawcall value is too large ----> the drawcall value is too large, and the required GPU processing performance is high. As a result, the CPU computing time is too long, so it gets stuck.

3. There are too many points and faces ----> there are too many points and faces. The GPU calculates based on different effects, and the CPU calculates a large amount of data, so the results come out, but Kaspersky

Due to the card problem caused by the saved by batching and drawcall values being too large, I have optimized the following methods:

1. For the model: mesh merge, there is a good plug-in (drawcall minimizer ---> download it directly from asset store, free of charge, and documentation, it is easy to get started)

2. for UI: Try to avoid replacing ngui or ezgui with the built-in unity3d GUI, because the two UI plug-ins place UI images in one atlas for image processing in the UI, and one Atlas corresponds to one drawcall.

3. For lighting: You can use the lightmapping plug-in provided by unity3d to bake the Lighting Effect in the scene to the object material.

4. For scenarios: You can use the occlusion culling plug-in provided by unity3d to bake elements in a static scenario.

4. For special effects: try to combine the texture

The number of drawcalls supported by unity3d on mobile terminals is mainly related to the sub-host performance. Of course, it does not mean that the performance will be okay if the value is small, there are also 17 cards, mainly because the texture of the model is too large), I am currently doing around 70, OK, quite normal

Http://blog.csdn.net/jeksonal/article/details/8804196