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
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
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