Phaser: Bitmaptext display capped on Canvas

[monteiz]

Version

• Phaser Version: 3.50.0
  
• Operating system: MacOS
  
• Browser:

Description

With version 3.50.0, Bitmaptext objects are displayed cropped, like only a small portion of every letter. This happens only with canvas. Using WEBGL, the same code/asset works as expected.

Example Test Code

Additional Information

[vforsh]

You need to provide an example. I use bitmap texts extensively in my game and they look fine.

[monteiz]

@vforsh You're right, all of the Phaser 3 examples also works. It must be a matter of assets. I am trying to prepare an example, but since the issue appears to be asset specific, I cannot find a quick way to share my own .png and .fnt file in the sandbox.

These are the two files: https://ufile.io/f/48e4c

I use the old Shoebox to create my bitmapfonts, which worked well until version 3.24.x. With version 3.50.0, they appear wrongly cropped.

I tried Littera to make a test, and bitmapfonts created with it work well.

What do you use to create your bitmapfonts?

[vforsh]

@monteiz I always use Littera too. Such a shame that it is a Flash-based tool and it will fade away soon.

[monteiz]

@vforsh I agree with you, Littera is great, but a bit limited. With Shoebox you can use Photoshop or Illustrator to make really amazing bitmapfonts, but for some reason Phaser 3.50.0 does not like it anymore. I hope someone can fix that.

Littera in Flash, and Shoebox in Adobe Air. We will say bye to them soon I guess, and that's a shame.

I have just seen your game, it looks awesome! Congratulations, it is beautiful.

[SBCGames]

@vforsh @monteiz Another Littera user here. On Adobe site, you can download Flash projector (https://www.adobe.com/support/flashplayer/debug_downloads.html). It is standalone app on PC that can open .swf files. Then download web page with Littera with browser and keep .swf file. Finally, open .swf with projector...

[monteiz]

Thank you @SBCGames, that's a good tip.

[photonstorm]

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.