#after i think

1 messages · Page 1 of 1 (latest)

manic gust
#

could be that the collision happens between the time the bigger cube created and the merged ones removed

#

try to remove them before you create a bigger one

reef helm
#

alright i modified the code to do that

#

hmm it still does the weird thing

#

oh right the parent ill try with no direct parent

manic gust
#

btw, you also need to take account that destroying gameobject happens on the end of the current frame.
But I think you can just simply disabling colliders on the little one before creating the bigger cube

reef helm
#

even with no set parent it does the same thing

#

i'll try disabling colliders

#

destroying gameobject happens on the end of the current frame.
regardless of order?

reef helm
#

if you watch the second video more closely, its like the extra cube gets pulled in somehow

manic gust
#

🤔 try adding debug.log before creating a cube, also add the cube size to the log

#

and check the who is creating the big cube
So you can know who is creating that big cube

reef helm
#

is this alright?

#

oh wait before

reef helm
#

there were 3 objects involved that i placed

manic gust
#

how do you check the collision? using ontrigger?

reef helm
manic gust
#

wait, where do you put oncollisionenter?

#

on the transparent cube that you can move around?

reef helm
#

no

#

the function is on all the different cubes

#

the transparent cube is just a cursor representation and holds no weight/force

reef helm
#

however this is added after the name change

#

-# the name change was required for one of the if statements

manic gust
#

my guess is that the size 1 cube collides with the small cubes when it was created. try assigning the newcube to different layer, just to make sure

reef helm
#

different layer?

#

my unity crashed i need a sec

#

because icloud broke my whole game i now have the opportunity to go back and see anything i can change to fix it