Results 1 to 17 of 17

Thread: takeObject is taking objects with their colliders on

  1. #1
    Join Date
    May 2016

    takeObject is taking objects with their colliders on

    I am using an asset bundle as a regular-style bag (not infinite). When I take objects out of it (also asset bundles) their collision is still active. So as they fly across the table they hit other things and scatter them.

  2. #2
    I really hope this is fixed because it broke my mod that I spent over 500 hours on.

  3. #3
    also noticing strange behavior with putObject(). it is back to things running into each other and getting caught on other bags in collision. guessing related? can change takeObject param to smooth false, but i don't think the param exists for putObject

  4. #4
    Is this problem to do with custom 3d objects?

  5. #5
    Join Date
    May 2016
    Specifically ones with custom colliders

  6. #6
    Ok, thanks. I suppose if all else fails, I just take those out of the memory bags and figure out another way.

  7. #7
    Going on 6 weeks it looks like, since this thread was started. Is progress being made to address it?

  8. #8
    Join Date
    Jan 2014
    Can you guys post a save file / link to a workshop that can reproduce this bug?

  9. #9
    I'll post one up tomorrow

  10. #10
    Join Date
    Jan 2014
    I have a fix for this now actually, thanks tho.

  11. #11
    I know I complained about it across multiple platforms. I appreciate that you are addressing it, however I am still having the same issue. I'm on update 10.2 hotfix 1. Is that correct? I tried to upload a video example to youtube but it is rejecting the file and won't let me upload.

  12. #12
    Over a week and no answer? Please address this. Once this is fixed, I will no longer update because it seems shit gets broken all the time. Why should I spend a huge amount of time (over 3 months) making a mod that is destroyed in one fell swoop.

  13. #13
    They *did* address some issues about concave coliders and takeObject() in the latest hotfix.
    You can employ workarounds (lock/setPosition on the objects that are getting yanked) like 99% of others doing any complex interactions.
    There are issues dating months/years, I'd reccomend trying to work with what we have, "one week" is nothing

  14. #14
    Well, this has been broken for a lot longer than a week. What I meant was, it's been over a week and there hasn't even been a reply to my post. Whatever they "addressed" did not fix the issue for me. As shown in the video.

    What do you mean by lock/setPosition? I'm using MrStumps memory bags.

    It is extremely frustrating how the updates break shit. I was using a Kingdom Death table that became very unstable when they updated the physics and since that mod used a lot of collisions. So, I went off to create a whole new table from scratch. There was a huge amount of work put into it. And then, just like that, it's ****ing broke now. Frustrated.

  15. #15
    Instead of just doing takeObject(...) -> obj.setPosition(...) for every taken object, do takeObject(...) -> obj.lock() -> obj.setPosition() and after taking everything like this, do obj.unlock() for each. And everything stays calm regardless of colliders.

  16. #16
    here is the code section from MrStumps bags. It looks like he already has set lock

    function buttonClick_place()
        local bagObjList = self.getObjects()
        for guid, entry in pairs(memoryList) do
            local obj = getObjectFromGUID(guid)
            --If obj is out on the table, move it to the saved pos/rot
            if obj ~= nil then
                --If obj is inside of the bag
                for _, bagObj in ipairs(bagObjList) do
                    if bagObj.guid == guid then
                        local item = self.takeObject({
                            guid=guid, position=entry.pos, rotation=entry.rot,
        broadcastToAll("People of the Sun Loaded", {1,1,1})
    I am getting this problem with memory bags that only have cards in them. Cards do not have custom colliders correct? So maybe this issue has to do with something else?
    Last edited by; 01-21-2018 at 12:34 PM.

  17. #17
    It only locks whatever was locked when it was saved into the bag if I read this correctly.

Similar Threads

  1. Replies: 4
    Last Post: 10-02-2017, 03:34 PM
  2. takeObject issues - Custom Objects
    By Tanners in forum Scripting
    Replies: 5
    Last Post: 03-28-2016, 12:59 PM
  3. Non-convex colliders tips?
    By MzTTS in forum General Discussion
    Replies: 2
    Last Post: 01-30-2016, 11:00 AM
  4. Replies: 1
    Last Post: 12-23-2015, 05:52 PM
  5. Replies: 5
    Last Post: 07-21-2015, 12:21 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts