11-02-2018, 07:38 PM
(11-02-2018, 10:30 AM)josemendez Wrote: Hi Mystigan,Thank you for this info, I will definitely optimize the mesh, is it possible to pause/resume the simulation? I am thinking that cloths will only be simulated when the character does any action if they are standing idle I should not simulate them.
1200 x 9 = 10800 vertices is way too much for mobile. I'd never go over 1500-2000 in total. No wonder it lags when you set all them up. Also, if the cloth has thickness (that is, it isn't a single layer of triangles) you must use proxies to avoid the "bag" effect. This can also help you reduce the amount of simulated vertices greatly, as your simulated mesh and the renderer mesh can have different polycounts.
You should also really use local-space simulation for character clothing, as done in the CharacterCloth sample scene. This will allow you to scale cloth by scaling the ObiSolver transform (that should be at the character's root transform), as well as increase the stability of the simulation and increase your control of it (as you will be able to blend local and world space velocities).
Note that having separate solvers for each character is extremely beneficial in your case, as you can cull cloth simulation per-character (otherwise you'd be forced to simulate all characters as long as any of them was visible) and increase parallelism (better core utilization). You should not use a single solver for all of them.