Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.8.0-pre.1
Issue ID
UVSB-2387
Regression
No
Debug Break Node is activated after the For Loop Node is finished and Debug Log Node is executed
How to reproduce:
1. Open the user's attached project "MyTest.zip"
2. Open the "TestScene" scene
3. Open the "DebugErrorDemo" Script Graph
4. Press Play and observe the Console window
Expected results: The Debug Beak Node sets the Editor in break mode before the first Debug Log Node is executed
Actual results: Debug Break Node is activated after the For Loop Node is finished and Debug Log Node is executed
Reproducible with: 1.7.8 (2021.3.5f1, 2022.1.7f1, 2022.2.0a17, 2023.1.0a3), 1.8.0-pre.1 (2022.1.7f1, 2022.2.0a17, 2023.1.0a3)
Could not test with: 2019.4.40f1, 2020.3.36f1 (Visual Scripting package is not available)
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:
The debug break node is not intended to function like a break point and will not be triggered in the middle of a loop. It is designed to pause the game after the completion of the current frame.