• Content Count

  • Joined

  • Last visited

  1. That's what I am doing at the moment. We will look to upgrading to whatever Phaser version is applicable for our next projects and also see if the problem persists by then. Thanks.
  2. I see! What was weird was it was happening randomly on Chrome Version 63.0.3239.84. It might be related to Phaser 2.6.2 then (haven't had the time to try out any later versions yet, and we are too far into production to change). I will have to try some different browsers and see if just forcing to array to be specified from us and if it still works then, or if we have to check what browser is being used. Thanks!
  3. Hello! I am working on a Phaser project (however, the issue is PIXI related). I was having issues with blend modes not always being set correctly when reloading my page. After a couple of days me and my colleague found that the PIXI.blendModesCanvas was being set to something like ["source-over", "lighter", "source-over", "source-over", "source-over", "source-over"] etc. I don't know if other people have ran in to this bug, but I thought I would document this here at least, and if it still exists in newer versions of Phaser/PIXI, that is what is causing it. To fix it we just set the PIXI.blendModesCanvas to a correct list when we start loading the game. We are using Phaser 2.6.2 at the moment, and the correct list is: ["source-over", "lighter", "multiply", "screen", "overlay", "darken", "lighten", "color-dodge", "color-burn", "hard-light", "soft-light", "difference", "exclusion", "hue", "saturation", "color", "luminosity"]