Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.4.3f1
2020.2
Issue ID
1274332
Regression
No
A short fixed time is given to attach the Debugger when launching Player built with Server Build and Script Debugging enabled
How to reproduce:
1. Create a new project
2. Open the Build Settings (File -> Build Settings)
3. Enable these settings: Server Build, Development Build, Script Debugging
4. Click 'Build and Run'
Expected result: the Player console displays the Managed Debugger port number and waits for user input before running the Scripts (to give the user as much time as needed to attach the Debugger)
Actual result: a 10-second countdown begins before the Scripts are run and the port number is displayed
Reproducible with: 2018.4.27f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Notes:
1. When enabling the 'Wait for Managed Debugger' setting, there's still a 10-second countdown before the port is displayed
2. The countdown takes only 3 seconds in the 2018.4 stream
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a2
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b12
Resolution Note (fix version 2020.1):
Fixed in 2020.1.14f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.15f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.31f1