If you are pasting something you copied onto a physics entity, then it will assume all bricks in said object are solid, and then it will refuse to let you update them.
IE, you place an object on an entity. You then try to disable collisions for the object, but the hitbox does not update even if all the bricks you added are set to no-collide.
#Collisions Copy-Paste bug
spice nest
lofty yarrow
physics grids require a collision hitbox, if you disable all collisions then the physics default to the grid hitbox to prevent crashing the physics engine.
you must have atleast one brick with collisions enabled, which could just be a 2x2 microstud brick somewhere attached to the grid
spice nest
physics grids require a collision hitbox, if you disable all collisions then the...
This isn’t the problem.
The object in question had plenty of bricks with a collision, and if I placed bricks normally on it, I could disable their collisions.
The issue is that you cannot disable the collisions on bricks that are copied and pasted onto said object.
lofty yarrow
ah I see. The problem is you said "even if everything is set to no-collide", so long as that isnt the case it should be behaving as expected.
So to be clear, the bug is that bricks copy pasted onto physics grids have bricks that cant have collision configured?
blazing heart
post a repro case
spice nest
Will do when I get home
spice nest
upon recreating the bug, it does not want to appear
however @gleaming token was there to see it, so I know i'm not tweaking.
WAIT
this may only happen with microbricks
boom
on the object I am pasting them onto, there are already multiple existing hitboxes, so it's not the problem BT mentioned above.
modest elbow
it's possible this is a weird thing with how collision works
idk for sure if it's the same issue, but here's some posts about what it might be
#1402760921968807957 message
#brickadia message
#gameplay-help message