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 Condition is forced to use Scene Variable even when a Local Variable is declared. #7385

Open
1 task done
VanCastar opened this issue Feb 10, 2025 · 1 comment
Open
1 task done

Comments

@VanCastar
Copy link

Is there an existing issue for this?

Describe the bug

When I first declare local variables and then do a raycast the result is forced to be saved only in Scene Variables and not the Local Variables as per the icons of the variables in teh image is shown.
Thus when I test the Local Variables, they are set as the original values instead of the values returned from the RayCast Condition.

Image

Windows 10
This version of GDevelop is: 5.5.224 (editor full version: 5.5.224-4d56333ae786cdf5f246fc973095808f8c7de671, core version: 5.5.224-0)

Steps to reproduce

As per description.

GDevelop platform

Desktop

GDevelop version

5.5.224 (editor full version: 5.5.224-4d56333ae786cdf5f246fc973095808f8c7de671, core version: 5.5.224-0)

Platform info

OS (e.g. Windows, Linux, macOS, Android, iOS)

Windows 10

Additional context

No response

@4ian
Copy link
Owner

4ian commented Feb 10, 2025

Thanks for reporting this! This is indeed less than ideal. We're even thinking of switching to expressions (RaycastCollisionX(), RaycastCollisionY(), etc...) for this so that it is more flexible.

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

No branches or pull requests

2 participants