You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the filterArea is not set, the bounds of the container are calculated every frame if a filter is applied, which can have a noticeable performance impact at least in the case of the weather container. It might even be a good idea to override bounds calculation for the reason that a filter might be attached to one of the parents of the weather container: this would cause bounds calculation of the weather container, if no filterArea is set on the parent.
classParticleContainerextendsPIXI.Container{filterArea=canvas.app.screen;accessibleChildren=false;interactiveChildren=false;calculateBounds(){constbounds=this._bounds;const{ x, y, width, height }=canvas.dimensions.rect;bounds.clear();bounds.addFrame(this.transform,x,y,x+width,y+height);bounds.updateID=this._boundsID;}}
The InterfaceCanvasGroup also doesn't have filterArea set.
The text was updated successfully, but these errors were encountered:
aaclayton
added
bug
Functionality which is not working as intended
canvas
Issues related to the PIXI canvas, rendering, and other WebGL functions.
sfx
Issues related to visual effects like weather
labels
Jun 12, 2022
Environment Details
Issue Description
If the
filterArea
is not set, the bounds of the container are calculated every frame if a filter is applied, which can have a noticeable performance impact at least in the case of the weather container. It might even be a good idea to override bounds calculation for the reason that a filter might be attached to one of the parents of the weather container: this would cause bounds calculation of the weather container, if nofilterArea
is set on the parent.The InterfaceCanvasGroup also doesn't have
filterArea
set.The text was updated successfully, but these errors were encountered: