Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a17
Issue ID
621594
Regression
Yes
Can't connect MD debugger to standalone builds
-e: see title, ends with an error "could not connect to the debugger"
-issue reproduced for windows/osx/linux standalone
-repro:
--build windows standalone that has an actual script with Script Debugging enabled
--run build
--open MD
--try to attach to the standalone player
--NOTICE MD error and you are not connected to the player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment