Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2.15f1
2019.3
2020.2
Issue ID
1238781
Regression
No
Texture on Particle is not displayed when the particle and mesh are put into different asset bundles
How to reproduce:
1. Open the attache demo ParticleBundle.zip project
2. Open Scenes/Sample Scene and Enter the Play Mode
3. Inspect the Scene view
Actual: Texture is not displayed on the "errorObject" (see the repro.png attached)
Expected: Textures are displayed on both GameObjects
Reproducible with: 2019.3, 2020.2
Notes:
- if they are put into the same asset bundle, the texture is displayed
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Particles using Mesh Rendering require the Mesh to be marked as Readable so the system can get access to the raw vertex data. If the mesh is in the same bundle as the particle system, the native build pipeline can mark the mesh as readable appropriately. Otherwise the mesh has to be manually marked as readable if it is stored in another bundle. This is a limitation that is unfixable in the native build pipeline and was solved in it's replacement, the scriptable build pipeline and this case has been verified to be fixed by using this. The upgrade guide for SBP can be found here: https://docs.unity3d.com/Packages/com.unity.scriptablebuildpipeline@1.7/manual/UpgradeGuide.html