You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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.
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.
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)
Additional context
No response
The text was updated successfully, but these errors were encountered: