Search Issue Tracker
Fix In Review
Fix In Review for 6000.3.4f1
Votes
0
Found in
6000.3.5f1
Issue ID
UUM-133560
Regression
No
Issue with hash when checking for GhostFields
While investigating a concern about field ordering related to a Roslyn source generator from the Netcode for Entities package, a bug was discovered:
How to reproduce:
1. Create a component with two fields:
public struct MessyComponent : IComponentData
{
[GhostField] public int ValueA;
[GhostField] public int ValueB;
}
2. Create a build with that component
3. Switch the order of the two fields in the Editor:
public struct MessyComponent : IComponentData
{
[GhostField] public int ValueB; // swapped order
[GhostField] public int ValueA;
}
4. Create a client system reading the values
5. Run the Editor connecting to the older build
Actual result: The value updated server-side is going into the wrong field client-side
Expected result: the value updated server-side goes into the correct field client-side
Reproducible with: 6000.3.5f1
Reproduced on: Windows 11 (user reported)
Not reproduced on: No other environment tested
Note: This issue was not tested by CQA
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
- Root Motion Node option does not revert when changing the selection and clicking "Revert" in Inspector
- VFX Graph prefabs are not fully instanced when they are instantiated via a script
- All 2026-promoted builds incorrectly display outdated copyright year © 2025 instead of © 2026
- Shadow cascades and lights flicker when using Shadowmap Sampling
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
Resolution Note:
Fixed in next Netcode release 1.12.0
Resolution Note (fix version 6000.3.4f1):
Fixed in next Netcode release 1.12.0