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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
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.