Container.cacheAsBitmap behaving funny on retina

[nuthinking]

almost as if the snap shot wasn't retina. I am developing for an Android TV, sorry if the pictures below are not ideal (without and with cacheAsBitmap).

FYI Android TV is considered Retina (small window size in pixels but double density). I used the rendererOptions.resolution = window.devicePixelRatio and canvas style size = window size option to support it.

[nuthinking]

On the laptop, with technically the same resolution (full hd) looks way more readable (ok, this is a screenshot, not a photo).

So I guess I am doing also something wrong managing the retina use case in the first place.

[nuthinking]

Here Canvas 2D (left) VS Pixi (right).

I guess this is the price of using 3d rendering. On the TV the difference is much more noticeable.

[GoodBoyDigital]

hey there! if you use the pixi canvas renderer, does the text show up sharp?

[nuthinking]

Hi @GoodBoyDigital, I tried new PIXI.CanvasRenderer and as a matter of fact the difference in rendering quality is still there!

Here the pen: http://codepen.io/anon/pen/NNbdJY

It should be enough to check it on an iphone.

Thanks!

[nuthinking]

@GoodBoyDigital thanks to @ivanpopelyshev I discovered the "resolution" parameter in PIXI.Text. The documentation doesn't seem updated: https://pixijs.github.io/docs/PIXI.Text.html

This solved the quality of text in general. Still cacheAsBitmap makes the text worse. I updated the pen (had some problem with embedded font)

[GoodBoyDigital]

oh, one more to try:

PIXI.RESOLUTION = 2

as pix may be using a lower resolution texture to cache the text. - side note here but there should not be a situation where you would need to use cacheAsBitmap on text as it essentially a bitmap anyway.

hope that does the trick!

[nuthinking]

@GoodBoyDigital updated the pen, seems to work. Thanks! ;) Anyway, I was thinking of using cacheAsBitmap for a composition of more elements.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.