Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 23, 2017 1:25:33 GMT -5
I edited an EA object to make some stackable shoeboxes and they work fine most of the time. But occasionally they try to slot onto an area that doesn't exist and then crash the game. I'm fairly sure it's the slot I added that's causing this since they don't exhibit the behaviour until after you stack them, but I can't figure out why that is or where I've gone wrong. :/ My .blend & .package
Things I've tried since yesterday: - Adding the slot to a new version of the box with only the mesh edited. (I had messed with the footprint and shelf placement behaviour a bit so I wanted to make sure it wasn't any of that causing the issue.) - Using a completely different deco item as the base and keeping the rig from that item. (I used the tissue box as per this thread.)
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 24, 2017 21:32:26 GMT -5
Well, at this point I've tested stackable objects made by several other creators and was able to replicate this error with every single one. So, I guess the moral of the story is just don't put a stackable object between two benches lmao
|
|
|
Post by brujah on Feb 24, 2017 21:48:52 GMT -5
Alternatively you could place the stackables first then move the benches into place.
|
|
|
Post by orangemittens on Feb 24, 2017 21:52:36 GMT -5
If you clone an EA object and change its behavior by adding slots, it's possible that you've added behavior that the game code isn't set up to handle gracefully. If there isn't an EA item with behavior identical to what you're expecting from your item, the issue is most likely that the game isn't set up to work that way.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 24, 2017 22:06:38 GMT -5
Good to know, orangemittens . Thank you! True, brujah ! c: I mainly wanted to see if there was any way to prevent the issue so that people wouldn't have to stumble onto its existence, like I did, and then panic a bit when the cc messed with their game.
|
|