Hello, I have been trying to get bulletphysics/softbodies in a poser scene for a while now. I thought the original problem was a model having 140k polies, until i loaded a scene with the model and NO bullet painting. Preview slows to a crawl with live simulations enabled, ticking what would be a frame every 10 seconds even without any weight painting on any model.

I have an i7 a d a 1060gtx so I am findi g it hard to believe my hardware is at issue, and not an internal parameter (i hope). I have seen tutorials with people using less powerful hardware. Any help woumd be extremely appreciated.

That is a big assed model to begin with and I would expect any computer would slow to a crawl with it loaded. why not start out experimenting with smaller models and work your way up to higher poly count?

W10, Ryzen 5 1600x, 16Gb,RTX2060Super+GTX980, PP11, 11.3.740

V4 is only 66k polys and that is considered a dense mesh

W10, Ryzen 5 1600x, 16Gb,RTX2060Super+GTX980, PP11, 11.3.740

Preview is totally fone when not using live simulation. I should also add that i have tried bullet on v4 and same thing happened, its just slightly faster. But, its happening even when no ohysics paint are applied. I have no idea what my issie is. My laptop is fairly beefy. Are there parameters or preferances i can adjust? Maybe bp os attenoting to use integrated graphics instead of my gtx? How can i check things like that?

ghostship2 posted at 11:51PM Fri, 28 February 2020 - #4382090

That is a big assed model to begin with and I would expect any computer would slow to a crawl with it loaded. why not start out experimenting with smaller models and work your way up to higher poly count?

Physics engines aren't made to deal with high-res meshes (not only in Poser). Use a low-res proxie to manage objects with high poly-count.

Background: Even without anything special defined the physics-engine has to compute real hard maths for every single vertex (4 per polygon).

---

Another question to ask will be (given some measure of doubt about multi-threaded bending improving performance) is the physics simulation code written to take advantage of multiple CPU cores/threads simultaneously? Do we have confirmation of that?

---

My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.

What exactly are you trying to do? I'm trying to learn how to use Bullet Physics more effectively, and I haven't had any slowing to speak of. The one issue I do currently have has nothing to do with the number of polys.

Trying to make softbody physics. Particularly, breast, butt and thigh jiggle.

EClark1894 posted at 5:35PM Thu, 05 March 2020 - #4382127

What exactly are you trying to do? I'm trying to learn how to use Bullet Physics more effectively, and I haven't had any slowing to speak of. The one issue I do currently have has nothing to do with the number of polys.

There is apparently a coding script to have bp utilize openGL for graphics computation. But i dont think poser makes use of this in any way.

an0malaus posted at 5:36PM Thu, 05 March 2020 - #4382111

Another question to ask will be (given some measure of doubt about multi-threaded bending improving performance) is the physics simulation code written to take advantage of multiple CPU cores/threads simultaneously? Do we have confirmation of that?

How do you mean? I am using Aiko 4 for v4. She apparently buffs the usual poly count to 133k. Just peeped that lmfao. Could i not just reduce her poly count to 40k ? What do you mean by a proxy?

adp001 posted at 5:39PM Thu, 05 March 2020 - #4382108

Physics engines aren't made to deal with high-res meshes (not only in Poser). Use a low-res proxie to manage objects with high poly-count.

Background: Even without anything special defined the physics-engine has to compute real hard maths for every single vertex (4 per polygon).

I tried simply reducing the models poly count to 40k and that barely did any justice. As a matter of fact, it made things harder to work with, destroying all my grouped morph hierarchies. I would love if you could either provide a tutorial or some instructions to your wwy going about this.

adp001 posted at 5:59PM Thu, 05 March 2020 - #4382108

Physics engines aren't made to deal with high-res meshes (not only in Poser). Use a low-res proxie to manage objects with high poly-count.

Background: Even without anything special defined the physics-engine has to compute real hard maths for every single vertex (4 per polygon).

Start with not using all actors. Set only those actors to dynamic you need to "jiggle" (chest, thigh). Most polys are in head, fingers and feets. And set Sub-D to 0 while working on your figure.

---

For the record, I have used V4 in Bullet and had no problems. I was just writing a new blog for my website on Bullet Physics in Poser. One of the chief changes I advocate for is a list of Poser Presets or at the very least tutorials that show you how to set up for a jiggly body or bodyparts.

Here is a thread I found at the old SM forum that MAY help. It doesn't explicitly lay out step by step what you need to do, but I thought it might help you figure it out.

https://forum.smithmicro.com/topic/2101/all-of-the-best-features-of-poser-in-one-animation-nsfw

This is useful. Im learning grouping and control props now so i think some knowledge there will go far come time for incorporating physics.

EClark1894 posted at 4:02AM Fri, 06 March 2020 - #4382690

Here is a thread I found at the old SM forum that MAY help. It doesn't explicitly lay out step by step what you need to do, but I thought it might help you figure it out.

https://forum.smithmicro.com/topic/2101/all-of-the-best-features-of-poser-in-one-animation-nsfw