i will test this soon.
so in overall to say, sometimes the rigidbodycombiner could be a bottle neck. without rigidcombine is the framerate at my test file, where some tiny calculations are shaking hands, around 30 fps.
due this behavior i have to split the combiner up in more processing parts. should be possible, right? therefor i have in mind a automatical method. thats wont be a big deal write. just counting the verts at a model divide them through the cpu processing possibility and create and assign automatical a new combiner.
if im not up coming with some question about the rigidcombiner, i have to say thank you for your time and supporting.
logan´s run