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 JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment