This Issue is about an error on the web site.
Phaser Sandbox is Phaser 2.6.2 only, I cannot find the Phaser-CE version.

Feature Request

Firstly, thanks so much for this great and well-documented library!

Currently there is the beautiful option of loading PVRTC (or other compressed texture formats) with Phaser.Loader#image [1] and Phaser.Loader#texture [2].

However my preferred way of loading spritesheets with frames for animation is via Phaser.Loader#atlasJSONHash [3], but this method only accepts a normal image file along with the atlas data file (in JSON format).

I suppose my question is: how can we support an object with compressed texture formats (and a fallback truecolor image file as an argument passed to the Phaser.Loader#atlasJSONHash method? Is this desirable behavior for anyone else?

• [1] https://github.com/photonstorm/phaser-ce/blob/master/src/loader/Loader.js#L736
• [2] https://github.com/photonstorm/phaser-ce/blob/master/src/loader/Loader.js#L793
• [3] https://github.com/photonstorm/phaser-ce/blob/master/src/loader/Loader.js#L1584

This issue is about how BitmapFonts that are created from a texture atlas ( via cache.addBitmapFontFromAtlas() ) look very ugly compared to normal BitmapFonts ( this.load.bitmapFont() ) that use a separate non-atlas-merged PNG file.

The font PNG and XML are created using Littera. The font PNG is merged with other images into a texture atlas using TexturePacker. I am also using Phaser.CANVAS renderer.

The BitmapFont from the texture atlas is noticeably jagged / cropped on some parts / not smooth.

cache.addBitmapFontFromAtlas() is a very nice and handy feature as I am able to merge all my fonts into one texture atlas, however I currently can't use it in my game because it doesn't render so well. I would appreciate a fix for this. :)

In Phaser 2.6.2 it's lf.

In Phaser 3 it's lf.

Phaser CE's .editorconfig itself contains only lf.

There will be mixed line endings. 😿

• A -potential- bug in the API - Phaser-CE 2.7.3
• A problem with my own code

Hello! I had a question about this line - https://github.com/photonstorm/phaser-ce/blob/master/src/plugins/weapon/WeaponPlugin.js#L636 - why is the weapon calling updateTransform? Won't this incur an additional drawCall/WebGL update? I don't really know how that function works, but it looks out of place in the Weapon Plugin's update function.

When switching to v2.7.3, I have noticed strange behavior on Android where each touch event would trigger twice. Doing some debugging, I discovered that both the mspointer and touch device pointer types were being registered, and both would fire their own event when a touch event occurred.

I'm not sure why I did not encounter this in previous versions, but I suspect it has something to do with the move towards using the W3C version of PointerEvents rather than the old msPointer API:

6caec0d

Both the MSPointer class docs, as well as the code, suggest this is intended for use on Windows devices only, but window.PointerEvent is supported cross-platform, at least in Chrome. I'm not too familiar with the API, but I suspect the old window.navigator.(ms)PointerEnabled variables were returning true only on Windows devices, even on Chrome, which would explain why this problem didn't occur until the commit linked above. I also don't understand why I don't see double events on desktop Chrome, as it should be registering the pointer there as well...

As such, I'm not sure of the proper fix. One way would be to ensure that Phaser only ever registers one touch device handler, but if so, which should it prioritize? Another option would be to do a Windows OS check before setting mspointer, with a note that a better fix will come at a later date. This would adhere to the documented behavior of MSPointer and avoid any confusion caused by MSPointer being used on platforms other than Windows. (I would guess Phaser 3 would be the place to do any serious refactoring to make PointerEvent truly a cross-platform input option.)

Description
After loading an MP3 sound and waiting for decodedCallback than getting the sound duration returns zero (0) value.

Affected source
https://github.com/photonstorm/phaser-ce/blob/v2.7.3/src/sound/Sound.js
(I think the issue covers the same case as handled with CocoonJS, take a look at line 704)

Environment:
Phaser: 2.7.3-CE
OS: Windows 7
Browser: Firefox 51 (64-bit)

Code example

preload

function preload() {
    game.stage.backgroundColor = '#85b5e1';
    game.load.baseURL = 'http://examples.phaser.io/assets/';
    game.load.crossOrigin = 'anonymous';
    game.load.audio('audio_test', 'audio/tommy_in_goa.mp3');
}

create

var audio;
function create() {
    audio = game.add.audio('audio_test');
    game.sound.setDecodedCallback(['audio_test'], function() {
        console.log(audio.duration);  // BUG: sound  duration is zero (0)!
        audio.play();
        audio.stop();
        console.log(audio.duration);  // BUG solution: sound duration is > 0
    }, this);
}

http://phaser.io/sandbox/LDjSQJNv

• An error in the TypeScript defs

in phaser.comments.d.ts 29577:
getTileX(layer: Phaser.TilemapLayer|Phaser.TilemapLayerGL, x: number): number;

in phaser.js line 98574::
Phaser.TilemapLayer.prototype.getTileX = function (x) {

// var tileWidth = this.tileWidth * this.scale.x;
return Math.floor(this._fixX(x) / this._mc.tileWidth);

};

same happens for getTileY.

The quantity argument is optional, but if you omit it nothing happens (0 particles are launched).

This issue is about

• A bug in the API

Hi,

I am using webpack with expose-loader to have Phaser etc available on the global scope. Things are working well, I decided to upgrade to phaser-ce and the only way I could get my IDE (webstorm) to recognise that Phaser was actually a type was doing the following in MY tsconfig.json file

  "include": [
    "**/Game.ts",
    "../node_modules/phaser-ce/typescript/phaser.d.ts"
  ],
  "exclude": [
    "node_modules",
    "**/*.spec.ts"
  ]

Now it does work but says there are Multiple Options i.e. phaser.d.ts and phaser.comments.d.ts and phaser_box2d.d.ts.

I was wondering if I was doing the above correctly ?

I of course decided to remove the Includes section above but then that fails probably due to the fact that I have the exclude node_modules so the types are never being picked up.

I am using typescript 2.1 and decided to try and use the typeRoots but this also failed

"typeRoots" : ["../node_modules/phaser-ce/typescript"]

I am little confused of how to proceed do I leave the "../node_modules/phaser-ce/typescript/phaser.d.ts" inside the include section of the tsconfig.json ? It just feels kind of wrong.

Also even if I use this way then 'Phaser' seems to show Multiple Implementations for Phaser

Any help or info really appreciated

Thanks

The website http://phaser.io/docs suggests:

These docs are for Phaser 2.6.2
If you're using Phaser CE then download the CE repository and open docs/index.html

And since GitHub now supports docs/ directory for zero config github pages, can we turn that on for easier documentation viewing?

The offset parameters in body.setCircle appear not to work. No matter what I set the values to, the debug hit boxes shown are the same.

sprite.body.setCircle(32, 100, 300);

Tried in version 2.7.3.

I recently switched from phaser to phaser-ce and everything worked quite nicely except this error.

I've pinpointed it to when I apply a filter to two different sprites using the same texture. That is, something like this:

const s1 = this.game.add.sprite(0, 0, 'spriteKey');
const s2 = this.game.add.sprite(20, 20, 'spriteKey');

const filter1 = new Filter(this.game, null, shaderSource);
const filter2 = new Filter(this.game, null, shaderSource);

s1.filters = [ filter1 ];
s2.filters = [ filter2 ];

The error looks like this:

It doesn't occur in phaser 2.6.2.

It also messes up some rendering. Sprites which use the same key are flashing and teleporting seemingly at random.

The main difference I have been able to find between phaser and phaser-ce is the multi texture feature described in the tutorial. It also seems logical as sprites seem to affect each other. I have no idea how though.

How can I further debug this issue?

This Issue is about (delete as applicable)

• A bug in the API - 2.7.3

Bug here - https://github.com/photonstorm/phaser-ce/blob/master/src/plugins/weapon/WeaponPlugin.js#L879

I have a gun that is a child (via addChild) of a sprite. When the sprite moves, the gun rotates with it, but the fired bullets do not. I believe it is due to that line, where the local angle is used instead of the world angle.

Switching it from

this._rotatedPoint.rotate(this.trackedSprite.world.x, this.trackedSprite.world.y, this.trackedSprite.rotation);

to

this._rotatedPoint.rotate(this.trackedSprite.world.x, this.trackedSprite.world.y, this.trackedSprite.worldRotation);

should fix it

Videos seem to only download up to the canplaythrough point (?) on iOS 10.2. Videos show the preview image fine, and download the first second or two of the video (possibly up to canplaythrough), they don't unlock, but can be clicked to play. After the first couple of seconds of video, the video freezes – though the audio continues playing. Note, this works fine with iOS 9.3, loading and playing the whole video.

Here the most basic example I could show

    var game = new Phaser.Game(1366, 768, Phaser.CANVAS, 'phaser-example', { preload: preload, create: create })

    game.stage.scaleMode = Phaser.StageScaleMode.EXACT_FIT

    function preload() {
      game.add.text(100, 100, "Loading videos ...", { font: "65px Arial", fill: "red" })
      game.load.video('test', 'test.mp4')
    }

    function create() {
      var video = game.add.video('test');
      video.play(true);
      video.addToWorld();
    }

This has been tested using CE 2.7.3.

I have tried this with iPads and the xcode simulator using both iOS 9.2 and iOS 10.3. Both show the same behaviour for the respective OS.

This Issue is about (delete as applicable)

• A bug in the API (CE 2.7.3)

I've put a demo up here.

Source for the above demo can be download here.

The behaviour can also be seen on the Phaser demo site

This Issue is about a bug in the API (Sound).
I think the last modification to the Sound class (5735dbf) resulted in some kind of regression.
I'm trying to play the same audio file sequentially using the forceRestart parameter but I'm noticing silent gaps in the sequence, so the sound is not always playing.
No problems using 2.7.3.
I will try to create some kind of minimal example.

This Issue is about: A bug in the API (CE 2.7.3 - also seen in Phaser 2.6.2)

https://jsfiddle.net/uua222wh/1/

I'm creating a game that relies on multiple different layers running running synchronised tweens to animate composite sprites. It seems that a tween made up of multiple TweenData (i.e. one created using lots of calls to Tween.to()) will run significantly slower than a tween made up of less TweenData. I've created an example above. The two animations should each take 1000ms to complete, but they rapidly skew out of synch.

Basically it seems that the larger the value of a tweens's timeline.length, the longer the tween takes to animate.

Running Phaser in chrome works great, but I am seeing some errors thrown in Edge (syntax errors, inputs not being processed, etc.). Are there any goals to bring Edge support in line?

This Issue is about (delete as applicable)

• Compatibility with older browsers

Without any polyfill, this will fail on some older browsers (e.g. Android 4.4 default browser/webview).

We should change the use of Object.assign to Phaser.Util.extend instead.

• An error in the documentation

Looks like none of the PRs have updated the ReadMe for a couple of months now. I'm at fault here too. Can we update the summary so everyone can understand what 2.7.4 is changing/fixing? What should go there - author/commit/PR link?

If a Sprite's scale is 0.5 and its parent is the Phaser.World, its worldScale is 0.25. It should be 0.5 as well.

Richard Davey pointed me to this commit to Phaser V3. It should help resolve the issue.

If you're using Phaser Spine (Oct-ish build, with Fabrique class) and Phaser Spine 2.6.2, use the latest Phaser-Spine and Phaser CE 2.7.3. There's a loading bug of sorts when using the old combination that doesn't appear with the latest builds:

azerion/phaser-spine#40

After realise phaser-ce v2.7.3 i try to use fullScreenAPI on Android Chrome and it doesn't work for me,

if(game.scale.isFullScreen == false){
this.fullScreenButton.alpha = 0;
game.scale.startFullScreen(false);
} else {
game.scale.stopFullScreen();
this.fullScreenButton.alpha = 1;
}

By the way, the same codes works for phaser 2.6.2. I change and test it.
Can you guys check for it :)

http://codepen.io/samme/pen/EZpmMe

This Issue is about

• A bug in the API

Via phaserjs/phaser#2980

Was wondering if bower.json needs updating, should it be "name": "phaser-ce" - so as to not conflict with Phaser 2.7?

http://codepen.io/samme/pen/yMapZL

Phaser.Image has a lifespan but it's never decremented and so can't kill the image.

This issue is about

• A bug in the API (2.7.3)

This Issue is about a bug in the Phaser.Cache API 2.7.3 and below.

In method Phaser.Cache#destroy

/**
 * Clears the cache. Removes every local cache object reference.
 * If an object in the cache has a `destroy` method it will also be called.
 *
 * @method Phaser.Cache#destroy
 */
 destroy: function () {
   // ...
}

The unexpected behaviour is that most objects that are put in the cache are wrapped in another object, without a destroy method.

For example, looking at BitmapData, which has a `destroy' method:

• addBitmapData stores the actual data in a new object with keys data and frameData
• getBitmapData relies on getItem to get the correct data from the cache
• destroy does not take the property into account as getItem does and therefore does not invoke destroy on the data and frameData objects.

As a result, in this case, canvasses are never returned to the CanvasPool, causing a memory leak when loading external image data and relying on the cache to clean up old images.

Suggested solution:

• Update the destroy method to also iterate over the properties in the stored cache object. If a property contains a destroy method, invoke it on the property as well.

This Issue is about (delete as applicable)

• A bug in the API (phaser-ce 2.7.3)
• A problem with my own code

I tried to reproduce here but it seems to be working fine. Not sure what is causing this issue in my code - if it's me or Phaser.

In my code I set up multiple weapons for each sprite and set them all to autoFire. I was noticing really bad performance and eventually found that my custom Bullet classes are not having their kill() function called when going out of bounds (but it is called the in the collision handler just fine).

workaround

Include the following in my custom bullet classes' constructor

    this.checkWorldBounds = true;
    this.outOfBoundsKill = true;

Here is my weapon setup code

  _setupWeapons() {
    //add all the weapons from the json file
    this.weapons = [];
    const leveledWeapon = this.info.weapons['low_level'];
    for (var i in leveledWeapon) {
      const weaponInfo = leveledWeapon[i];
      const ammo = weaponInfo.preallocation || 20; 
      var weapon = this.game.plugins.add(Phaser.Weapon);
      weapon.bulletKillType = Phaser.Weapon.KILL_WORLD_BOUNDS;
      weapon.bulletSpeed = weaponInfo.bulletSpeed || 500;
      weapon.fireAngle = this._getWeaponAngle(weaponInfo.angle);

      weapon.bulletClass = Ship._getBulletClass();
      weapon.createBullets(ammo);
      weapon.autoExpandBulletsGroup = true; 
      console.log(weapon.bullets.children)

      weapon.fireRate = weaponInfo.fireRate || 500;
      //weapon.dmg = this.getDamage();
      weapon.dmg = 25; //this does nothing right now
      weapon.bullets.myWeapon = weapon;

      const percentOffset = (weaponInfo.xPercentOffset || 0) / 100;
      const xPixelOffset = Math.abs(this.width) * percentOffset;
      const yPixelOffset = -this.anchor.y * this.height + this.height / 2; //regardless of anchor, bullets start in middle Y of sprite
      weapon.trackSprite(this, xPixelOffset, yPixelOffset);

      this.weapons.push(weapon);
    }
    console.log(this.weapons)

  }

game.renderType HEADLESS becomes CANVAS so it runs through game.render() as usual.

http://codepen.io/samme/pen/oZdwmJ

This issue is about

• A bug in the API (2.6, 2.7)

Via phaserjs/phaser#3001

Running grunt tsdocs (which is part of the release task as well) fails currently with

Warning: Cannot read property 'text' of undefined Use --force to continue.

My guess is a previous commit did not fully conform to the requirements put forth by tsdocs and is now causing it to fail, though I've yet to locate which file is the source of this problem. I'm still actively looking, but additional eyes are appreciated!

Using multiple spritesheets in the game causes too many drawCalls, even having >5 drawCalls means on devices it runs below 30fps. In phaser 2.7.0 -> 2.7.2, using MultiTexture support fixed this issue on Desktops/Android devices but on iOS, a lot of textures were replaced with solid Magenta. When 2.7.3 was released, this "fixed" this issue, but now it just doesn't seem to be working on most devices at all.

I've looked through and put console logs into phaser-ce/src/pixi/renderers/WebGLRenderer.js to look, and it seems that on my desktop, the maxTextureSpaceAvailable is more than enough to fit all spritesheets with lots of space leftover, but even on my Samsung S7, the maxTextureSpaceAvailable is at 0 before even getting to adding any spritesheets into the texture cache.

My first test i attempted was to just remove the limit making sure maxTextureSpaceAvailable was above 0, and to my surprise, on my S7, the game ran at 60fps with a single draw call, even with this value dropping below zero...

if (maxTextureAvailableSpace <= 0) { base.textureIndex = 0; } else { base.textureIndex = (1 + (index % (maxTextures - 1))); }

Seems a bit weird that it could drop below zero, i'm not very knowledgeable about working directly with WebGL, but initial thoughts were that maybe the reported value of var maxTextureSize = gl.getParameter(gl.MAX_TEXTURE_SIZE); might be incorrect... though i'm honestly not 100% on that.. however my happiness of 'fixing' this was short-lived as the game just doesn't work on iOS now, obviously things are very different between the two.

Even if its something i'm personally doing wrong in my code, it seems wrong that on Android i can add things to the textureCache which exeeds the Max_Texture_Size and it works fine, 60fps.. but not on iOS. I'll keep looking personally as having a high FPS on devices are very important to my project, and the multiple spritesheets are essential for supporting multiple languages, but potentially something not working right here that someone could take a look at?

I was trying to use phaser in a Ionic2 application.
When I try to import phaser I get the following error:

File '.../node_modules/phaser-ce/typescript/phaser.comments.d.ts' is not a module.

Even vscode warns me there's something wrong with the import statement.

Here's the code:

import { Component } from '@angular/core';

import { NavController } from 'ionic-angular';

import {Phaser} from 'phaser-ce';

@Component({
  selector: 'page-home',
  templateUrl: 'home.html'
})
export class HomePage {

  constructor(public navCtrl: NavController) {
    
  }

Can anyone help me resolve this issue?

This Issue is about (delete as applicable)

• A bug in the API @ HEAD

Hey folks,

My team working with phaser had just found what we believe to be an issue - and we wanted to make sure that this isn't "as designed". If it is as designed, we would be interested to hear the justifications for the order in which these calls are made.

Assuming we load in preload, and also (as per our game design) perform a load in the create method: the load performed in the create function doesn't work.

See the following code from src/loader/Loader.js

finishedLoading: function (abnormal) {

        if (this.hasLoaded)
        {
            return;
        }

        this.hasLoaded = true;
        this.isLoading = false;

        // If there were no files make sure to trigger the event anyway, for consistency
        if (!abnormal && !this._fileLoadStarted)
        {
            this._fileLoadStarted = true;
            this.onLoadStart.dispatch();
        }

        this.onLoadComplete.dispatch();

        this.game.state.loadComplete();

        this.reset();

    },

It's our understanding that this.reset() should be called before any of the complete callbacks are dispatched, not after. Otherwise we're clearing the loading state after we've claimed to already be done with the loading state.

With the code as it is: the preload performs some loading calls. Once complete it dispatches these complete callbacks which trigger the create method. Our create method requests some assets to be loaded. Then the finishedLoading callback from the preload state calls this.reset() which will falsely clear the isLoading flag, even though the create method has requested that some assets be loaded.

Our proposed fix would be:

finishedLoading: function (abnormal) {

        if (this.hasLoaded)
        {
            return;
        }

        this.hasLoaded = true;
        this.isLoading = false;

        // If there were no files make sure to trigger the event anyway, for consistency
        if (!abnormal && !this._fileLoadStarted)
        {
            this._fileLoadStarted = true;
            this.onLoadStart.dispatch();
        }

        // clear loading state before we claim loading is complete
        this.reset();

        this.onLoadComplete.dispatch();
        this.game.state.loadComplete();

    },

As @photonstorm and others have mentioned many times in forms: there are many workarounds to loading failing in the create method. Our team is simply proposing what we think would be a more obvious flow that would avoid the issue all together.

Let us know what you think. :-)

Thanks,
Jared

This Issue is about : an error in the TypeScript defs

( Phaser v. 2.6.2)

Just converted my project into typescript and I hit couple of TS errors while trying to update some values for all my Phaser.Group elements using .addAll() method.

Below example should throw an error

this.asteroidsWave.addAll('angle', this.game.rnd.integerInRange(1,4));

Error:
error TS2346: Supplied parameters do not match any signature of call target.

working example:

this.asteroidsWave.addAll('angle', this.game.rnd.integerInRange(1,4), false, false);

After reading the TS definitions in phaser.d.ts , it turned out that the last two parameters aren't optional , which I think they should be , cause when they're not defined they're implicitly changed to false.

phaser.js

33358: Phaser.Group.prototype.setAll = function (key, value, checkAlive, checkVisible, operation, force) {
    if (checkAlive === undefined) { checkAlive = false; }
    if (checkVisible === undefined) { checkVisible = false; }
    if (force === undefined) { force = false; }

phaser.d.ts
1768: addAll(property: string, amount: number, checkAlive: boolean, checkVisible: boolean): void;

Either setting the default values for last two parameters or making them optional should fix the error.

addAll(property: string, amount: number, checkAlive?: boolean, checkVisible?: boolean): void;
or

addAll(property: string, amount: number, checkAlive: boolean = false, checkVisible: boolean=false): void;

This Issue is about (delete as applicable)

• A bug in the API (always say which version you're using!)

this code does not work correctly.
particles can not move anywhere. (works in phaser 2.6.2)

        this.waterParticle = game.make.bitmapData(2, 2);
        this.waterParticle.rect(0, 0, 2, 2, '#ff0000');
        this.waterParticle.update();

        this.emitter = game.add.emitter(200, 200, 500);
        this.emitter.makeParticles(this.waterParticle);
        this.emitter.setXSpeed(-100, -250);
        this.emitter.setYSpeed(-100, 100);
        this.emitter.setAlpha(0.2, 1);
        this.emitter.flow(500, 20, 2, -1, true);

Hi Phaser Team,

I have updated from v2.7.2 to the latest v2.7.3 and detected that the typescript/phaser.comments.d.ts has no longer any comments. I find them realy helpfull. I have taken a look into the master branch and it is still without comments.

unfortunately the v2.7.2 tag does not exists here.
I have used npm for installing it.

best regards
Alex

Box2d debug render doesn't follow world scale and rotation.

Current version:

/**
    * Renders 'debug draw' data for the Box2D world if it exists.
    * This uses the standard debug drawing feature of Box2D, so colors will be decided by
    * the Box2D engine.
    *
    * @method Phaser.Utils.Debug#box2dWorld
    */
    box2dWorld: function () {
    
        this.start();
        
        this.context.translate(-this.game.camera.view.x, -this.game.camera.view.y, 0);
        this.game.physics.box2d.renderDebugDraw(this.context);
        
        this.stop();

    }

Improved version:

/**
    * Renders 'debug draw' data for the Box2D world if it exists.
    * This uses the standard debug drawing feature of Box2D, so colors will be decided by
    * the Box2D engine.
    *
    * @method Phaser.Utils.Debug#box2dWorld
    */
    box2dWorld: function () {

        this.start();

        this.context.translate(-this.game.camera.view.x, -this.game.camera.view.y, 0);
        this.context.scale(this.game.camera.scale.x, this.game.camera.scale.y);
        this.context.rotate(this.game.world.rotation);
        this.game.physics.box2d.renderDebugDraw(this.context);

        this.stop();

    },

If world scale is not 1 or rotation is not 0 pointer world position will be invalid.

Sample code:

var sprite;

function preload() {
    game.load.baseURL = 'http://examples.phaser.io/assets/';
    game.load.crossOrigin = 'anonymous';
    game.load.image('phaser', 'sprites/phaser-dude.png');
}

function create() {
    game.world.position.set(100,100);
    if (1)
    {
        game.world.scale.set(0.5,0.5);
    }
    if (1)
    {
        game.world.rotation = Math.PI * 45 / 180;
    }
    sprite = game.add.sprite(0, 0, 'phaser');
    sprite.anchor.set(0.5, 0.5);
}

function update() {
    var pointer = game.input.mousePointer;
    sprite.x = pointer.worldX;
    sprite.y = pointer.worldY;
}

Temporary workaround:

var sprite;

function preload() {
    game.load.baseURL = 'http://examples.phaser.io/assets/';
    game.load.crossOrigin = 'anonymous';
    game.load.image('phaser', 'sprites/phaser-dude.png');
}

function create() {
    game.world.position.set(1000,1000);
    if (1)
    {
        game.world.scale.set(0.5,0.5);
    }
    if (1)
    {
        game.world.rotation = Math.PI * 15 / 180;
    }
    sprite = game.add.sprite(0, 0, 'phaser');
    sprite.anchor.set(0.5, 0.5);
}

function update() {
    var pointer = game.input.mousePointer;
    var camera = game.camera;
    var world = game.world;
    var rotation = -world.rotation;
    var sin = Math.sin(rotation);
    var cos = Math.cos(rotation);
    var tmpX = (pointer.x + camera.position.x) / camera.scale.x;
    var tmpY = (pointer.y + camera.position.y) / camera.scale.y;
    var worldX = tmpX * cos - tmpY * sin;
    var worldY = tmpX * sin + tmpY * cos;
    sprite.x = worldX;
    sprite.y = worldY;
}

This Issue is about (delete as applicable)

• A bug in the API - 2.7.3

I'm trying to get some guns to appear behind their parent sprite, and this thread leads me to believe it's not possible without a hacky work around. Is this true? If it is, how can we enable support for rendering parent sprite on top of children?

This Issue is about an error in the documentation

For example navigate to page http://phaser.io/examples/v2/loader/load-audio
Try to select Phaser Version 2.7.5 - Phaser CE in dropdown
404 error loading http://examples.phaser.io/_site/phaser/phaser.2.7.5.min.js

Hello @photonstorm , I am the member of cdnjs project. We want to host this library. I think the main file are under build/. Could help me mention the files we need? Thanks for your help.

cdnjs/cdnjs#10227

In src/loader/Loader.js on line 2297 you have :

 case 'texture':

                if (file.key.split('_').pop() === 'truecolor')
                {
                    this.loadImageTag(file);
                }
                break;

i think there should be something like this :

 case 'texture':

                if (file.key.split('_').pop() === 'truecolor')
                {
                    this.loadImageTag(file);
                } else {
			  // load pvr files.	
                           this.xhrLoad(file, this.transformUrl(file.url, file), 'arraybuffer', this.fileComplete);
			 }
                break;

or simply remove break; before case 'binary':

This Issue is about

• A bug in the API (checked from 2.6.1 on)

When using multiple tinted BitmapTexts some characters may be rendered incorrectly. It can even lead to IndexSizeError in some browsers.

On image below is test scenario:

Two BitmapTexts are used to show number 5. Then, when both texts are changed to 10, only first (bottom one) text is rendered correctly, while the second has distorted "50" instead of 10. Problem is related only to Canvas renderer.
Problem is that both texts use the same character and parameter requiresReTint is not on glyph, but on texture. Then tinted texture for first character occurence is updated, but not for other characters sharing the same texture (as requiresReTint is flagged to false after first retint). So, second text uses old tinted texture, but tries to display correct rectangle from it. If rectangle to display is bigger than tinted texture, you may get IndexSizeError in some browsers (IE).

Solution working for me was to change (https://github.com/photonstorm/phaser-ce/blob/master/src/gameobjects/BitmapText.js#L455):

            g.scale.set(scale);
            g.tint = this.tint;
            g.texture.requiresReTint = true;

to:

            g.scale.set(scale);
            g.tint = this.tint;
            g.texture.requiresReTint = true;
            g.cachedTint = 0xFFFFFF;

This issue was added to the Phaser repo but I didn't see it here. It also occurs with apk files created with cocoonjs. The workaround in the Phaser issue below worked for me. Details and workaround are in the link below.

phaserjs/phaser#2913

When webaudio is active and loading and removing large audio files these are not deleted from memory, this bug is from phaser 2.3.0
The discussion is in this thread http://www.html5gamedevs.com/topic/19339-audio-memory-usage-headache/

http://codepen.io/samme/pen/apJBWP?editors=0010

• A sprite with a physics body and exists = false
• Modify its scale
• Call sprite.reset(…) or sprite.body.reset(…)
• The body dimensions don't match the sprite dimensions

This can happen if you try scaling weapon bullets (which don't exist until they are reset when fired).

It happens because

• sprite.reset() → body.reset() updates the cached scale but doesn't resize the body
• body.preUpdate() → body.updateBounds() resizes the body only if the cached scale is wrong

This issue is about (delete as applicable)

• A bug in the API (2.6, 2.7)

This Issue is about: A bug in the API
Reproduced with: 2.6.2 and CE 2.7.3
Description: Changing game volume when sound is muted will unmute the sound but game.sound.mute stays true
Sandbox example: http://phaser.io/sandbox/edit/pwRPKVcR

I could understand that changing volume unmutes the game but it then should also revert mute to false.

My workaround currently:

({
  vc_updateVolume: function() {
    var nv, was_muted;
    nv = this.vc_getVolume();
    if (nv !== this.game.sound.volume) {
      was_muted = this.game.sound.mute;
      if (was_muted) { this.game.sound.mute = false }
      this.game.sound.volume = nv;
      if (was_muted) { this.game.sound.mute = true }
    }
  }
});

// ---
// generated by coffee-script 1.9.2

This Issue is about (delete as applicable)

• A bug in the API (always say which version you're using!)

Uncaught TypeError: this.preUpdateLifeSpan is not a function
    at Phaser.Image.preUpdate (phaser.js:34431)
    at Phaser.Stage.preUpdate (phaser.js:16669)
    at Phaser.Game.updateLogic (phaser.js:21276)
    at Phaser.Game.update (phaser.js:21167)
    at Phaser.RequestAnimationFrame.updateRAF (phaser.js:48928)
    at _onLoop (phaser.js:48911)

/**
* Automatically called by World.preUpdate.
*
* @method Phaser.Image#preUpdate
* @memberof Phaser.Image
*/
Phaser.Image.prototype.preUpdate = function() {

    if (!this.preUpdateInWorld() || !this.preUpdateLifeSpan())
    {
        return false;
    }

    return this.preUpdateCore();

};

Looks like it's probably related to #63

Hello, I am trying to create a phaser application using Ionic 2. All that is do is initialize an ionic 2 project using ionic start then once that is created I do a npm install phaser-ce --save Once that finished I import phaser into one of the auto generated pages like so.

import { Component } from '@angular/core';
import { NavController } from 'ionic-angular';
import Phaser from 'phaser-ce'
@Component({
  selector: 'page-page1',
  templateUrl: 'page1.html'
})
export class Page1 {
  constructor(public navCtrl: NavController) {  }
     ionViewDidLoad(){
        console.log(Phaser)
     }
}

Then I simply just try to run the application. When i do i get this error

By going into the developer console on chrome this is where the error is coming from

I have tried editing the files to make this work but no matter what i do nothing seems to work. If anyone knows if this is a bug or if I am just doing something wrong that would be great.
Thank you.

For reference, I posted this in the forums

I am using the latest phaser ce build, phaser 2.7.3. My target browser is desktop Chrome
(I don't care much for any other browser, mobile platform, etc)

Explanation of my issue: I have a text, at position (0,0) [Therefore, no possibility of it no being a whole number, etc]. It is not scaling properly.

=> Minimal fiddle testcase showing my problem: http://jsfiddle.net/1g3cj8md/

=> Expected outcome if game is not scaled: http://jsfiddle.net/encznmqq/1/

Is this a bug? Am I missing anything? Basically, the rendering of a google fonts when the game is scaled seems off. This happens whether you use a pixel-friendly font like VT323 or a more 'normal' font.
I pressume that if this is a bug, it has to do with how scaling manages text. Perhaps a workaround is using other types of fonts?