# Incorrect shared fragment hashing in Mass system

**URL:** <https://forums.unrealengine.com/t/incorrect-shared-fragment-hashing-in-mass-system/2737161>\
**Category:** Issues and Bug Reporting (Unreal Engine)\
**Tags:** unreal-engine, CPP\
**Created:** [July 21, 2026, 1:18am UTC](https://forums.unrealengine.com/t/incorrect-shared-fragment-hashing-in-mass-system/2737161 "2026-07-21T01:18:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![archimonde1111](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@archimonde1111](https://forums.unrealengine.com/u/archimonde1111)\
**Post date:** [July 21, 2026, 1:18am UTC](https://forums.unrealengine.com/t/incorrect-shared-fragment-hashing-in-mass-system/2737161/1 "2026-07-21T01:18:24Z")

</div>

### Summary

The hashing logic used by `FMassEntityManager::GetOrCreateConstSharedFragment` doesn’t take into account SoftObjectPtr properties when stored objects are not loaded.

### What Type of Bug are you experiencing?

Framework

### Steps to Reproduce

1. Create a shared fragment.
2. Create a trait with said fragment.
3. Add the fragment to the build context using mentioned method.
4. Create 2 entity DAs that reference different object in SoftObjectPtr.
5. Start PIE with debugger attached, and breakpoint set in BuildTemplate method.

### Expected Result

The shared fragments that differ only in SoftObjectPtr properties are correctly marked as different instances.

### Observed Result

The mass uses already existing shared fragment, instead of creating a new version with correct SoftObjectPtr.

### Affects Versions

5.5

### Platform(s)

Windows

### Additional Notes

I’d like to suggest reverting the change that made `GetOrCreateConstSharedFragmentByHash` private in 5.8
