Search Issue Tracker
Fixed in 2018.2.X
Votes
1
Found in
2018.1.0f2
Issue ID
1033103
Regression
No
Phantom mesh is rendered at (0, 0, 0) with mesh particle GPU instancing
To reproduce:
1. Import the package into the project (bugreport 20180503 particle GPU instancing glitch.unitypackage)
2. Open the "demo scene" scene
3. Enter Play mode
4. Observe the ghost cube at the center of the world
5. Select Particle System game object and in Renderer module disable Enable GPU Instancing
6. Observe that ghost cube is gone
Expected: the ghost cube is not there
Reproduced in 2018.1.0a6, 2018.1.0f2, 2018.2.0b3, 2018.3.0a1
Did not reproduce in 2018.1.0a5
Could not test in earlier versions, the GPU Instancing for particles doesn't exist there
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment