Richard Davey

icon indicating a website link www.photonstorm.com icon indicating an email [email protected]

icon company @phaserjs icon location UK icon location Full time HTML5 Game Developer and creator of Phaser, Atari otaku, Retro Gaming Geek, child of the 80s, demoscener, anime and pixel art fan.

Results 275 comments of Richard Davey

Immovable object is stopped by a non immovable object

Closing this off as it was more a discussion than an issue. Feel free to re-open in the forum / Discord if still relevant.

SceneManager.getScene function to generic

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...

Fix: `convertTilemapLayer` creating composite bodies unintentionally

Thanks for this. I have implemented your fix and credited you in the Change Log.

Tiles disappear on camera move in isometric mode

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...

Timing, frame-rate consistency improvements and features

@liabru I don't suppose there's any chance of you merging this into master, is there? :) I really think it could be beneficial!

DisplayList causes infinite loop that is hard to track down.

Calling destroy is vital and *must* be done. Replacing it with an empty function will completely break the internals of Phaser.

DisplayList causes infinite loop that is hard to track down.

@frankakn7 find out where in your code you are destroying the Game Objects, or incorrectly overriding the `destroy` method (as in the original issue), or if you've got any Game...

DisplayList causes infinite loop that is hard to track down.

Going to close this, as `destroy` should never be replaced in this way and is documented as such.

Cursor not refreshing after disableInteractive()

While this could be done, disabling _any_ interactive object that sets the cursor would reset the cursor again, no matter how that disable was triggered. This is actually currently an...

requestVideoFrame polyfill is causing a error in Next.js hot-reload

Even with this change in place, Next.js SSR still complains about the use of `navigator` for us. How did you get around that?