FIXED:BSolver COMP Actor COMP and Object CHOP

Hello,
having these three nodes in a network, with the object CHOP referring to an actor COMP creates a cook loop.

I feel like the object chop would be a pretty good tool for using in the context of the bullet feedback CHOP parameter so I’m inclined to think this may be a bug.

The demo file is on 1200 but I initially found it on the alpha build.

Thank-you

actorcomp_cookloop_bug.toe (7.1 KB)

For simulation feedbacking, and more generally, to get the simulation data into CHOP-space, you should use the Bullet Solver CHOP. There’s a few OP Snippets showcasing the workflow.

Hi Eric,

The cook loop also seems to happen if the object CHOP references a Geo COMP unrelated to the simulation.

In my use case I am using the bsolver CHOP while the object CHOP does some calculations in relation to other (non actor) geos in the network.

edit: sorry went a bit fast there and didn’t check the full error log. I still get a cook loop even without the object CHOP now. I’ll look into it a bit more.

actorcomp_cookloop_bug_withgeo.toe (7.0 KB)

Hi again Eric,

In regards to my previous post. My mistake was that the bullet solver COMP loads with an error regardless of anything else in the network .

As for the bullet solver CHOP I’ve found how I can replace the object CHOP in my network.

Thank-you for your help!

1 Like

Is the cook loop warning still there and an issue? I’m not able to reproduce the warning on start-up that you mentioned.

Hi, yeah I’m getting that error on 12000.

oops spoke too soon again regarding the bsolver CHOP solving my issues.

Using a bsolver CHOP requires that I make my geo COMP an actor which adds a bit of complexity to my simulation regarding collisions etc.

In this case I can use a parameter CHOP to get the txyz parameters instead but it does seem that the object CHOP has some weird behavior when used in-line with the feedback CHOP parameter of an actor.

bulletsolver_cookloop_incontext.toe (9.1 KB)

Thanks, I can reproduce the cook loop issue now. I’ll take a look into it.

The cook dependency loop bug will be fixed in the next official build we release: 2023.12150+. Thanks for the report.

1 Like