What's going on with my collision?

[Encario]

I was trying to clean up my collection file to make it easier to navigate, so i tried putting all of my collision into a game object.

When I have debug enabled and I build the program now, it shows the collision boxes and they still collide with things, but the player character and camera doesn’t move with them. (I thought they would since they’re in the same game object (Player) in the collection)
If I remove them and leave them in just the Player Game object, the camera and sprite works as expected with the collision but the collision boxes don’t appear when I have debug enabled. What is going on here?

Another oddity with my debug mode is that I have collision on my tilemaps and when i run the program, two of my areas look normal, with just lines to show the collision shape:

but one of my areas does this, showing the collision boxes of the area like how it does for characters, and i’m just confused as to why theres the difference in debug mode, everything seems to be the same between the tilesheets/tilemaps

[britzl]

@Encario

When I have debug enabled and I build the program now, it shows the collision boxes and they still collide with things, but the player character and camera doesn’t move with them.

Your player script is on the “go” game object. Isn’t the script moving that game object and not the one with the sprite and camera?

@Encario

and i’m just confused as to why theres the difference in debug mode, everything seems to be the same between the tilesheets/tilemaps

Could it be the amount of debug vertices that is drawn? There is a max debug vertices option in game.project. Try increasing it!

[Encario]

The player script isn’t in the go game object, this is it when closed

[britzl]

Oh, ok. I didn’t look close enough! Can you share a minimal example project?

[Encario]

what’s a minimal example project?

[britzl]

@Encario

When I have debug enabled and I build the program now, it shows the collision boxes and they still collide with things, but the player character and camera doesn’t move with them. (I thought they would since they’re in the same game object (Player) in the collection)
If I remove them and leave them in just the Player Game object, the camera and sprite works as expected with the collision but the collision boxes don’t appear when I have debug enabled. What is going on here?

It is hard to tell what is going on by looking at the screenshots and your description of the problem. In order to help you I ask that you share a small project where the problem can be observed.

[Encario]

so a version with unnecessary aspects to look at the problem removed or should i just zip the actual file and send it? It’s not a large file, zipped is 40,000KB

[Encario]

Here’s a onedrive link to the full thing, it is like 42,000KB, if you need me to cut it down i can
MoA Test (2).zip

[britzl]

@Encario

When I have debug enabled and I build the program now, it shows the collision boxes and they still collide with things, but the player character and camera doesn’t move with them. (I thought they would since they’re in the same game object (Player) in the collection)

@Encario

Here’s a onedrive link to the full thing

Thanks. The problem is that you are resolving collisions for the child game object named “go” (the one with the collision objects) and not for the parent object. This means that you are able to freely move the game object with the player sprite, but the child game object (named “go”) with the collision objects get stuck. I think it would be easier if you put the collision objects in the same game object as the sprite and the rest of your scripts.

[Encario]

okay thank you, I’ll just leave it all as it was before with it all in just the player game object, looks a bit messier but yeah, it works