Search Issue Tracker
Won't Fix
Fixed in 2018.4.X
Votes
1
Found in
2017.3.1p1
Issue ID
1024363
Regression
No
[Particles] non R/W mesh from asset bundle is not rendered in particle system but not detected as unusable
To reproduce:
1. Open the project, attached by the user (psr_bug.zip)
2. Open the "main" scene
3. Use the bundleMesh asset as the mesh in the Particle System on the psr_bundleMesh object
4. Observe that particles are not rendered
5. Use the editorMesh asset instead of the bundleMesh
6. Observe that particles are now rendered
Expected: mesh, loaded from a bundle, is properly used in Particle System
Reproduced in 2017.1.3p3, 2017.2.2p3, 2017.3.1p1, 2017.3.2f1, 2018.1.0a3
Did not reproduce 2018.1.0a4, 2018.1.0f1, 2018.2.0a8
Fixed in 2018.1.0a4
-
Fndz
Sep 09, 2019 07:43
Just happened on my own project.
Particle system show with no issues on Android / iOS / Editor if they are build in.
Using asset bundle we get this error;No mesh data available for mesh wave_01 on particle system start_aura. Make sure Read/Write Enabled is set in the importer to work on the particle system renderer
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
This bug isn't likely to get fixed, as it's simply not high enough priority.
The workaround is simple - mark the relevant meshes as Read/Write.
Unity would like to be able to auto-detect this for you, but it is not trivial in this case.
Sorry for the inconvenience.
Resolution Note (fix version 2018.4):
This bug isn't likely to get fixed, as it's simply not high enough priority.
The workaround is simple - mark the relevant meshes as Read/Write.
Unity would like to be able to auto-detect this for you, but it is not trivial in this case.
Sorry for the inconvenience.