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

Visible Collision Shapes (Debug) for Raycast node stucks on red color after first hit #52051

Closed
starcin opened this issue Aug 24, 2021 · 2 comments

Comments

@starcin
Copy link

starcin commented Aug 24, 2021

Godot version

3.4.beta4.official [6a058cb]

System information

Windows 10, GLES3

Issue description

In 3.4.beta4.official [6a058cb], if "Visible Collision Shapes" setting is enabled, a raycast object is rendered as a blueish narrow pyramid.

In 3.3.2 stable, the same object is rendered as a orange line:

v3 4 beta4_before_hit
v3 3 2 stable_before_hit

During the raycast detects a hit, they both render the shape red:

v3 4 beta4_during_hit
v3 3 2 stable_during_hit

But after the collision (when there is no hit anymore), the v3.4 one stays red:
v3 4 beta4_after_hit
v3 3 2 stable_after_hit

Steps to reproduce

You just need to collide a raycast with something.

This is the whole moving object in my scene:
resim

The script only contains simple impulse force funcitons to be able to move it with arrow keys.

And this is the whole scene:
resim

Minimal reproduction project

Here is the project.
SampleRaycastBug.zip

Sorry I couldn't delete a plug-in. Even it is not enabled, Godot file system doesn't let me delete it and if I delete it in Windows File Explorer, I can't open the project because Godot crushes during opening the project.

@Calinou
Copy link
Member

Calinou commented Aug 24, 2021

This is likely a regression from #49726.

@fabriceci Do you know what could be causing this?

pouleyKetchoupp added a commit that referenced this issue Aug 24, 2021
[3.x] Fix Raycast3D color update when not colliding anymore (Fix #52051)
@pouleyKetchoupp
Copy link
Contributor

Closed by #52056 on 3.x (issue already fixed on master).

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