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
I noticed that cacheAsBitmap property from Container class has disappeared.
Is there a workaround for that ? Or maybe a come back of the property ?
This feature was really powerful in the previous versions and many projects cannot be migrated without that.
Expected Behavior
When we have a container and many sprites side by side, with V7 and cacheAsBitmap enabled, we can scale the container as much as we want, the container behave like an image and displays no spaces between the sprites.
Steps to Reproduce
in V8 without cacheAsBitmap, when the container is rescaled, some spaces appear between the sprites and do not behave like an image which results in some weird behaviour (see attached images)
Environment
pixi.js version: e.g. 8.1.0
Browser & Version: e.g. Chrome
Possible Solution
I can export the container as a texture and make a simple workaround like that:
let options = { target:myContainer }
let texture = app.renderer.extract.texture(options);
but when the container exceed the texture size limit, this workaround cannot work and besides, it adds a new texture to the memory etc, which was well handled in V7 and all previous versions of Pixi...
Additional Information
Thanks a lot !
The text was updated successfully, but these errors were encountered:
In v8 I didnt got this problem with adding 1px padding on my sprite in my spritesheet.
Also in my experience this kind of problem can be also be linked with the generation of the mipmap if the sprite is used to a smaller version of himself, then it will use the generatemipmaps and this typically result in bad behaviors with line appearing on the border like the one you screenshot.
This workaround works in some cases yeah, but it does not come with the cacheAsBitmap functionalities, such as blocking all animations or updates within any cached container.
the cacheAsBitmap property was very useful in previous versions, does the team schedule to implement that again in V8 or it is just erased like that with no migration options ?
Current Behavior
I noticed that cacheAsBitmap property from Container class has disappeared.
Is there a workaround for that ? Or maybe a come back of the property ?
This feature was really powerful in the previous versions and many projects cannot be migrated without that.
Expected Behavior
When we have a container and many sprites side by side, with V7 and cacheAsBitmap enabled, we can scale the container as much as we want, the container behave like an image and displays no spaces between the sprites.
Steps to Reproduce
in V8 without cacheAsBitmap, when the container is rescaled, some spaces appear between the sprites and do not behave like an image which results in some weird behaviour (see attached images)
Environment
pixi.js
version: e.g. 8.1.0Possible Solution
I can export the container as a texture and make a simple workaround like that:
let options = { target:myContainer }
let texture = app.renderer.extract.texture(options);
but when the container exceed the texture size limit, this workaround cannot work and besides, it adds a new texture to the memory etc, which was well handled in V7 and all previous versions of Pixi...
Additional Information
Thanks a lot !
The text was updated successfully, but these errors were encountered: