Search Issue Tracker
Fixed in 2021.3.39f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 6000.0.X, 6000.0.1f1
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.7f1
2023.2.0b3
2023.3.0a1
6000.0.0b11
Issue ID
UUM-44485
Regression
No
“USS parsing error: An unexpected error occurred” errors appear when having one or more slash in the USS file after “/*” symbols
How to reproduce:
1. Open the user’s attached “UITKTest.zip” project
2. Open the “CommonStyle.uss” file
3. Add a “/“ after the first “” and save the file
4. Focus the Editor
Expected result: No errors
Actual result: “USS parsing error: An unexpected error occurred” errors appear
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3
Reproduced on: macOS 13.4.1 (Intel)
Notes:
-reproducible one or more “/“ signs
-not reproducible if adding “/“ before the second “”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment