Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
1
Found in
2021.2
2021.2.8f1
2022.1
2022.2
Issue ID
1399961
Regression
Yes
[Dedicated Server] Data from mesh colliders are stripped in dedicated server builds
Reproduction steps:
1. Open the attached project "MTT-2676.zip"
2. Enter the Play Mode
3. The capsule will move in zig-zag so going through both walls in succession
4. Each collision event produces a log message in the Console window indicating when the capsule collides with each wall
5. Switch to a Dedicated Server platform and Build the player
6. In a dedicated server Build only box collider data is logged
Expected result: Data from mesh colliders are not stripped in dedicated server builds
Actual result: Data from mesh colliders are stripped in dedicated server builds
Reproduces on: 2021.2.17f1, 2022.1.0b15, 2022.2.0a10
Does not reproduce on: 2019.4.38f1, 2020.3.32f1
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note (fix version 2022.2):
Data from mesh colliders are no longer stripped in dedicated server builds
Resolution Note (fix version 2022.1):
Fixed in 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.2f1