Search Issue Tracker
Fixed in 5.3.3
Votes
2
Found in
5.1.2f1
Issue ID
723993
Regression
No
[culling] Wrong culling of some particle objects
1. Open attached "CANDLE3" project
2. Open "repro" scene in assets folder
3. In hierarchy tab, click on "FX" and then double click on "e_Luciernagas Reverse" object
4. Move or zoom camera around this object
5. Notice, that this object sometimes blinks or disappears (As shown in the attached GIF)
Comments (5)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Teku-Studios
Dec 11, 2015 15:13
Ok, I see how this goes. The thing with some particle effects (like fire) is that their size is variable since the emitting is somewhat random, and that makes that, sometimes, the particle is on a corner of the screen and its bounding box can for a few frames be small enough to get out of the camera frustum, and then get in again. In the frames in which the bounding box is smaller and it's not inside the screen space, the particles are culled and, as soon as the particle grows bigger and the bounding box expands, the particle appears again.
Teku-Studios
Dec 11, 2015 12:16
Happenning in v5.3.0 too...
Teku-Studios
Nov 09, 2015 13:31
Still happenning in v5.2.2...
Teku-Studios
Oct 01, 2015 14:49
It's apparently related to the subemmitters. The Yscale value in their transform must be exactly 1, don't really know why.
Teku-Studios
Sep 25, 2015 11:51
This also happens with sprites too (although in that case setting their Zscale to a very very small value such as 0.001f kind of solves the issue).
Hoping this will be fixed soon since it clearly affects the visuals of any game.