Basically, I am confused about rules regarding 3d models designing for mobile games.
I knew we require to design low poly 3d models for mobile games otherwise it takes too much load and there is a huge performance loss in the game.
In this, we required to explain this to 3d models designers who may or may not be related to the gaming field.
So they mostly design in high quality that becomes useful for PC games.
At present, I want some guidance related to game main player 3d models like a human player for 3rd person shooter game, player car in a racing game etc…
I have these questions:
how many vertices and triangles limit required to put?
any kind of texture size limit?
how many types of textures allowed? like, albedo texture, normal map texture, height map texture etc…
please advice me regarding my basketball player model designed by the designer, I have attached the wireframe and shaded wireframe images, I think its too much high detailed 3d model.
how to check the number of polygons and triangles for the 3d model?
About 100k verts in total from your camera view. Its game specific so use “Stats” window to determine how much verts there are in the view. (If your intention is to support wider range of devices (and users), otherwise double that for high-end)
I’d say there isn’t, but generally you shouldn’t go beyond 4k. Lesser - better. Also, make sure your textures are power of two. Also note that texture size affect build size. And you can’t go over 150MB with AAB. Keep in mind.
Albedo + Normal (where required). Rest is an overkill, and you won’t be able to bundle it w/o OBB.
Its too dense.
Select model file in project view. Drag up preview (at the bottom of the inspector), tris / verts should be available there.
Another thing, draw calls are also a major concern in mobile.
Make sure to abuse Dynamic Batching (with <300 verts per mesh + single material) if you’re using dynamic objects (although that might not be available for the skinned characters), or use static batching. Alternatively, for higher dynamic object count - instancing.
Total approximated drawcalls to support low-end mobile is about 50.
Use Frame Debugger to profile & determine how much you have atm.
I think you always should test on your target device.
Debug using profilers and look for GPU / CPU / Ram bottlenecks.
For mobile, this model looks far too detailed.
If not for numbers exactly, I would go for minimum number of vertices / pligons, that make model acceptable.
Mind Mobiles got rather small screens. You will not see many details. So optimise it down, until it will start look lower quality. Textures and shaders can make low poly models, to look smoother and higher quality.
Of course, you may want to look in LOD. That gives you plenty of flexibility, in case the performance start to stutter.
