Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-12
Regression
No
Inspector displays incorrect type size alignment when inspecting Components
Reproduction steps:
1. Open the attached project "Case_1412002.zip"
2. Open the Components window (Window -> DOTS -> Components)
3. Find and select "New Component" in the Components window
4. Observe the value of "Alignment" in the Inspector
Expected result: the value of "Alignment" is 1 B
Actual result: the value of "Alignment" is 16 B
Reproducible with: 0.50.1-preview.2 (2020.3.35f1)
Notes:
- The project contains a script "Example.cs" that calls "UnsafeUtility.AlignOf<T>()" which displays the correct alignment
- While testing with byte variables, it was found that defining an odd number (excluding 1) of byte variables shows the alignment as 16 B, an even number (up to 8) shows as many bytes as there are variables defined, more than 8 shows 16 B and 1 shows as 1 B
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
This issue is fixed by renaming the field to "Component Alignment in Chunk", which reflects the proper field content.