Search Issue Tracker
Fixed
Fixed in 2022.2.21f1, 2023.1.0b18, 2023.2.0a15
Votes
0
Found in
2022.2.8f1
2023.1.0b6
2023.2.0a4
Issue ID
UUM-28270
Regression
No
Drawn arch is not visible, and “ArgumentException: slice.Length (2) does not match the Length of this instance (0)“ errors appear when using “MeshGenerationContext” with 100 Progress if it has any offset
How to reproduce:
1. Open the user’s attached “BugRadialElement.zip” project
2. Open the "NewUXMLTemplate.uxml” file
3. In the UI Builder Hierarchy, select “UIElementRadialFill” and change the “Offset” parameter
4. Observe the UI Builder
Expected result: Arch is visible
Actual result: Arch is not visible, and “ArgumentException: slice.Length (2) does not match the Length of this instance“ errors appear
Reproducible with: 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Could not test with: 2020.3.45f1, 2021.3.20f1 (Errors after project downgrade)
Reproduced on: macOS 13.2.1 (Intel)
Notes:
Reproducible in the UI Builder and Game windows
Not reproducible if the “Progress” parameter is not 100
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 2023.2.0a15):
Fixed in: 2023.2.0a15
Resolution Note (fix version 2023.1.0b18):
Fixed in: 2023.1.0b18