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

Array with inner class type(Array[InnerClass]) breaks debug with failed to encode a path #94583

Closed
GustJc opened this issue Jul 21, 2024 · 3 comments

Comments

@GustJc
Copy link
Contributor

GustJc commented Jul 21, 2024

Tested versions

-Reproductible in: v4.3.beta3.mono.official [82cedc8]

System information

Windows 10 - Vulkan (forward+) - dedicated

Issue description

Having a var that has a type of Array[InnerClassType] breaks debug with failed to encode path

When using a breakpoint, it spits out errors. Still works, but won't show the type on the debug console.
It'll keep spitting out the same errors every time the debug tries to show the variable.
And it won't show the class runtime debug when selecting the node inside the remote tab.

Steps to reproduce

  • Put a breakpoint anywhere inside a class that uses an Array[InnerClassType]
  • Play the game
    Result: Errors spit in console. Don't break, but can't show array of innerclass variable. Trying to select self in debug spits errors again.
  • Select the node inside the remote tab while the game is running
    Result: The node is not shown/selected. Errors spit in console

Errors:
error

Min code:
min_example

Minimal reproduction project (MRP)

Min project:
MRP_has_inner_class.zip

@AThousandShips
Copy link
Member

@GustJc
Copy link
Contributor Author

GustJc commented Jul 21, 2024

Indeed it has. Just tested on the latest build (v4.3.beta.gh-94503 [34fd39e8e])
And it is now fixed.

Sorry for this. I'll make sure to test on the latest dev build before opening issues again.

@GustJc GustJc closed this as completed Jul 21, 2024
@AThousandShips
Copy link
Member

No worries! It would be very helpful if you are able to build the engine yourself to verify

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

2 participants