Search Issue Tracker
Fixed
Fixed in 1.0.X - Entities
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.0.X - Entities):
This issue is fixed by renaming the field to "Component Alignment in Chunk", which reflects the proper field content.