Search the Community

Hello, Please can someone tell me whether Phaser games will work well in IE9? As phaser uses webGL, I assumed it won't work in IE9 as webGL is not supported by IE9. But still I was able to open a few of the phaser games in IE9. I just want to get an overall analysis of browsers supporting phaser games.

Hi my phaser tweens are running slow on IE9 (about half speed), regular game loop object movement via setting x/y is fine, IE10+ is ok as is other browsers. Is there any known issue with phaser tweens and IE9? Example of tween code this.title.scale.set(0,0);this.title.alpha = 1;this.game.add.tween(this.title.scale).to({ x:1, y:1 },1500, Phaser.Easing.Elastic.Out, true, 500); Any ideas?

When trying to use pixelperfect checks IE9 throws SCRIPT5022: DOM Exception: SECURITY_ERR (18) mysprite.input.pixelPerfectOver = true;mysprite.input.pixelPerfectClick = true; I have this set if it matters: load.crossOrigin = "Anonymous" The server has header Access-Control-Allow-Origin: * Same code works on IE11, Chrome, Safari. Is there a good way to get this working? I can do other image operations on the same image such as redrawing it on bitmapdata and alpha masking without this problem.

Hi, I'm having issues with everyone's favorite browser: I'm displaying Spine animations in Pixi - which works well except for in IE9. part of the code: PIXI.loader.add('animTest', 'libs/pixiSpine/animTest.json');PIXI.loader.load(function (loader, resources) {walker = new PIXI.spine.Spine(resources.animTest.spineData);}and on on IE9 I receive the following error: SCRIPT5022: The spineData param is required.If I log 'spineData' it's undefined. I've tried one or two polyfills (typedarray.js and es5.js) with no effect.. Since I'm new to web development, I've not sure how to figure out what IE is missing. Thanks!

Hey Everyone, I am developing a game that needs to run in IE9 (unfortunately) and the Phaser framework is throwing errors as soon as the JS file is loaded. Here is a link to illustrate the issue : http://files.thesecretlocation.com/CRUS/NERD/testGame/indexNew.html All I am loading on the page is an un-minified version of the v2.1.0 framework along with the IE9 dataview-polyfill.js This is the offending code chunk ( from line 64,217 of phaser.js ) var process=require("__browserify_process"),global=typeof self !== "undefined" ? self : typeof window !== "undefined" ? window : {},Buffer=require("__browserify_Buffer"),__filename="/..\\node_modules\\poly-decomp\\src\\index.js",__dirname="/..\\node_modules\\poly-decomp\\src";module.exports = { Polygon : require("./Polygon"), Point : require("./Point"),};It looks like there are extra commas being added on the second last line. After some deeper investigation it looks like this is happening throughout the code base which is causing the browser (IE9) to throw the error. Does anyone know a way around this? I started going through and removing the offending commas but there is 80,000 lines of code : / thanks, Josh NOTE : I am using this version of IE9 in a VM on my mac http://news.softpedia.com/news/How-to-Run-Internet-Explorer-on-Mac-OS-X-391323.shtml

Hello Anybody, I just encountered a problem when preloading json, with IE9. I tracked the problem down the Phaser.Loader.jsonLoadComplete handler is using this._xhr.responseText instead of this._ajax.responseText when window.XDomainRequest is used. I checked the master/dev and parallel-loader branches there doesn't seem to be fix in place yet, is this a bug or am I missing something else here? Regards, Brad

Well I know getting things to work on older versions of IE are not the highest priority... however- I chose pixi for some client work and of course they are having problems seeing it on IE9/Windows 7 I believe the problem is due to pixi using Object.defineProperty() which IE9 should be able to handle... but doesn't always. There's a lot out there about getting the browser into IE9 standards mode (or something) - but every combination of tags and doctypes I use only seem to fix the problem, only to have it broken the next time we open the browser. Using F12 developer tools to change the browser mode can fix it, but of course the end user won't be expected to do that. The start of my html looks like this: <!DOCTYPE html> <html> <head> <title>My Project</title> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <meta charset="utf-8"> Tried removing the IE=Edge meta tag but it gives me 'random' success. I'm basically ready to give up and convert to EaselJS which won't take me too long, but I'm still curious about this. Thanks for any clues!