Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Does anyone else have rope that just "die" and have to be ripped out and re built?
#1
Its happened a couple of times now, a rope will just no longer have physics and I'm wasting a lot of time rebuilding them. Literally just becomes a pole, no gravity, not movement, no ability to alter length... like the backend code has somehow broken.

Is there some way to refresh a bugged rope or shall I rip it out again and rebuild?
Reply
#2
(09-02-2024, 11:29 AM)Mulbin Wrote: Its happened a couple of times now, a rope will just no longer have physics and I'm wasting a lot of time rebuilding them. Literally just becomes a pole, no gravity, not movement, no ability to alter length... like the backend code has somehow broken.

Is there some way to refresh a bugged rope or shall I rip it out again and rebuild?

Hi!

Never heard of anything like this, to be honest. Things off the top of my head that could cause similar outcomes:

- Are there any errors popping up in the console (these can prevent your game's code to continue running)?
- Is the solver's sleep threshold too high? (this freezes particles in place if they're below an energy threshold)
- Is the solver included in a ObiFixedUpdater component? if the solver's not updated, no simulation will take place.

Also, what do you mean by "ripping out and rebuilding" a rope? Creating a new ObiRope component, re-generating the blueprint, taking it out of the solver and back into it...?

kind regards,
Reply
#3
I had something like that when I tried to duplicate a rope along with blueprint. I think what happen was some internal references inside the new object ended up pointing to an old blueprint or something like that. And after that I had to rebuild the rope from scratch.
Reply