When I first started working with mgear1 I was always incredibly happy with the general performance of the rigs. However on the current project we are working on we are using mgear2 for the first time (just updated yesterday from 2.5.24 to 2.6).
And I have the feeling that everything feels a bit less fluid.
After building the default biped guide and setting two keys on the world_ctl I get about 40fps in parallel mode with gpu override. 16 in the first DG playthrough, getting a lot faster afterwards (using DG is not an option as soon as there is binded geometry).
so 40fps does not sound too bad, but that is without skinbinds or any other additional fancy stuff. With slightly heavy character I am currently working with fps drop to 32fps during playback, and 24fps during manipulation if the the spine is involved. Still workable but before adding a face rig I kind of would like to improve on this somehow but I am kind of stuck by now because I can not think of any particular way to optimize the rig more except for removing modules entirely (which is not an option).
Dirty propagation for the spine takes up to 220ms and evaluation about the same according to the profiler which seems a bit long.
I’ve tried replacing more contraints with decompose matrix connections and replacing modules with seemingly simpler ones but nothing proved to be really successful.
Baking the keyframes to the joints I get way above 100fps though.
So well yeah any advice?