Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raycast 2d Collision TIlemap #71353

Open
Polar2b opened this issue Jan 13, 2023 · 2 comments
Open

Raycast 2d Collision TIlemap #71353

Polar2b opened this issue Jan 13, 2023 · 2 comments

Comments

@Polar2b
Copy link

Polar2b commented Jan 13, 2023

Godot version

v3.5.1.stable.official

System information

Windows 10

Issue description

Raycast 2d will only collide at intersections of tilemap collisions. There was a thread from 2020 on this same issue meaning it has been prevalent for 3 years now and if not fixed will likely carry over into godot4, I would say this is an important thing to fix as using raycast2d for collision has advantages over just a collisionshape2d. I will link the prior report as well. This is not a project specific issue so I hope the lack of reproduction project is okay. #44003

First.Platformer.C.DEBUG.2023-01-13.13-54-22.mp4

Steps to reproduce

Step 1 - Make Tilemap Node
Step 2 - Make a Tileset with a collision and make a basic platform
Step 3 - Make a basic character with a raycast 2d for ground collision
Step 4 - Ensure that collision layers are correct
Step 5 - See problem
(should take like 5 minutes)

Minimal reproduction project

N/A

@Calinou
Copy link
Member

Calinou commented Jan 13, 2023

This is not a project specific issue so I hope the lack of reproduction project is okay. #44003

Please upload a minimal reproduction project to make this easier to troubleshoot.

@kleonc
Copy link
Member

kleonc commented Feb 9, 2023

Raycast 2d will only collide at intersections of tilemap collisions. There was a thread from 2020 on this same issue meaning it has been prevalent for 3 years now and if not fixed will likely carry over into godot4, I would say this is an important thing to fix as using raycast2d for collision has advantages over just a collisionshape2d. I will link the prior report as well. This is not a project specific issue so I hope the lack of reproduction project is okay. #44003

@Polar2b #44003 (which this issue seems to be a duplicate of) has been fixed in 4.0 since way before this issue was reported (#54857 was merged on Nov 11, 2021).
So if anything I guess what's being reported in here is that #44003 is still present / not fixed in 3.x? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants