Skip to main content
edited tags
Link
Kromster
  • 10.7k
  • 4
  • 54
  • 67
Tweeted twitter.com/StackGameDev/status/879379769510551553
Removed meta tag, cleaned up question, inlined animated variant
Source Link
Gnemlock
  • 5.3k
  • 5
  • 28
  • 59

In my latest game I'm making, you can slice a 2D object arbitrarily, demonstrated in this gif:

enter image description here
(Click for animation.)
enter image description here

You can continuously cut it continuously into hundreds, or thousands, of pieces. This doesn't create a lot of lag, because they're always in a sleeping physics state, but there's a problem when you cause them to move.

I'm not really sure how to deal with making it so there's not so much rubble from cutting something apart. I don't really want to delete them after a certain amount of time becausetime; I don't like how, if you go back to something you cut up after a while, it randomly disappeared.

Anyone know of a good way to handle thisHow can I clean up excessive player-created rubble?

In my latest game I'm making, you can slice a 2D object arbitrarily, demonstrated in this gif:

enter image description here
(Click for animation.)

You can cut it continuously into hundreds, or thousands, of pieces. This doesn't create a lot of lag because they're always in a sleeping physics state, but there's a problem when you cause them to move.

I'm not really sure how to deal with making it so there's not so much rubble from cutting something apart. I don't really want to delete them after a certain amount of time because I don't like how if you go back to something you cut up after a while, it randomly disappeared.

Anyone know of a good way to handle this?

In my latest game I'm making, you can slice a 2D object arbitrarily, demonstrated in this gif:

enter image description here

You can continuously cut it into hundreds or thousands of pieces. This doesn't create a lot of lag, because they're always in a sleeping physics state, but there's a problem when you cause them to move.

I'm not really sure how to deal with making it so there's not so much rubble from cutting something apart. I don't really want to delete them after a certain amount of time; I don't like how, if you go back to something you cut up after a while, it randomly disappeared.

How can I clean up excessive player-created rubble?

added 111 characters in body; edited title
Source Link
doppelgreener
  • 7.3k
  • 7
  • 43
  • 69

Unity - Good way to How can I clean up excessive player-created rubble?

In my latest game I'm making, you can cutslice a 2d2D object in any kind of wayarbitrarily, demonstrated in this gifgif:

Problem is, youenter image description here
(Click for animation.)

You can cut it continuously into hundreds, or thousands, of pieces which. This doesn't create a lot of lag due to the fact the parts are usuallybecause they're always in thea sleeping physics state of sleeping, but do withthere's a problem when you cause them to move.

I'm not really sure how to deal with making it so there's not so much rubble from cutting something apart. I don't really want to delete them after a certain amount of time because I don't like how if you go back to something you cut up after a while, it randomly disappeared.

Anyone know of a good way to handle this?

Unity - Good way to clean up rubble?

In my latest game I'm making, you can cut a 2d object in any kind of way, demonstrated in this gif

Problem is, you can cut it continuously into hundreds, or thousands, of pieces which doesn't create a lot of lag due to the fact the parts are usually always in the physics state of sleeping but do with you cause them to move.

I'm not really sure how to deal with making it so there's not so much rubble from cutting something apart. I don't really want to delete them after a certain amount of time because I don't like how if you go back to something you cut up after a while, it randomly disappeared.

Anyone know of a good way to handle this?

How can I clean up excessive player-created rubble?

In my latest game I'm making, you can slice a 2D object arbitrarily, demonstrated in this gif:

enter image description here
(Click for animation.)

You can cut it continuously into hundreds, or thousands, of pieces. This doesn't create a lot of lag because they're always in a sleeping physics state, but there's a problem when you cause them to move.

I'm not really sure how to deal with making it so there's not so much rubble from cutting something apart. I don't really want to delete them after a certain amount of time because I don't like how if you go back to something you cut up after a while, it randomly disappeared.

Anyone know of a good way to handle this?

Source Link
Garflington
  • 1.1k
  • 2
  • 9
  • 22
Loading