Search Issue Tracker
Won't Fix
Votes
3
Found in [Package]
1.20.0
Issue ID
ADDR-3248
Regression
No
Addressables Collision Meshes won't be Prebaked and won't work when running build if Read/Write setting is set to False
How to reproduce:
1. Open the user attached "MeshColliderAddressableTest.zip" project
2. Open the "Boot" Scene
3. Enter Play Mode and notice the Collisions working
4. Build and Run the project (File -> Build and Run)
Expected result: Collisions are working
Actual result: Collisions are not working
Reproducible with: 1.1.5 (2019.4.39f1), 1.18.19 (2020.3.35f1), 1.19.19 (2021.3.4f1), 1.20.0 (2022.1.2f1, 2022.2.0a15)
Reproduced on: macOS Monterey 12.0.1 (Intel)
Comments (1)
-
dizi451
Nov 20, 2022 22:12
me too
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
There's not an existing flag to force a mesh to be read/write in that existing code. Due to the complexity and risk of the feature request, we're unable to address this right now