non-reconnecting rope
- Thread starter grazr
- Start date
I would posit that you can do nothing about it. There are a rare few things that are somehow created by the engine in a way that is inaccessible via the entity system or the round reset code. If something doesn't reset, it's likely one of these and you're screwed.
Confirming what Boojumsnark said.
I had this same problem with a map for ZPS. I tried all sorts of wacky things ranging from parenting to physics tricks to get it to work, spending days just experimenting to see if anything would work. The bottom line is that a rope will not reset if it moves.
Your options unfortunately are limited to not having it break, removing it entirely, or replacing it with a model (probably not an option since it's last minute for the artpass deadline). Though depending on how you're using it, maybe you could set up a trigger_wind to blow it around wildly so it at least reacts to the explosion.
Kep
I had this same problem with a map for ZPS. I tried all sorts of wacky things ranging from parenting to physics tricks to get it to work, spending days just experimenting to see if anything would work. The bottom line is that a rope will not reset if it moves.
Your options unfortunately are limited to not having it break, removing it entirely, or replacing it with a model (probably not an option since it's last minute for the artpass deadline). Though depending on how you're using it, maybe you could set up a trigger_wind to blow it around wildly so it at least reacts to the explosion.
Kep
I guess i could try using the null model and connecting the rope to that. That way i don't break the rope i just break the constraint between 2 physics models.
Since TF2 doesn't have a problem reconnecting the payload to it's train this shouldn't be problematic.
Since TF2 doesn't have a problem reconnecting the payload to it's train this shouldn't be problematic.