Search Issue Tracker
Fixed
Fixed in 2021.3.39f1, 2022.3.28f1, 2023.2.20f1, 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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment