Jump to content


  • Content Count

  • Joined

  • Last visited

About st0n3vn

  • Rank

Recent Profile Visitors

1078 profile views
  1. Three years later, I have stumbled upon the same question. Any idea yet ? :D
  2. Yes, thanks for that, I followed your advice and quickly reworked the draw logic so that I don't call the loadTexture method at all. Although a minor improvement can be seen, sluggish performance on iOS continues (tested on iPad mini and iPhone 6s) and is still way slower compared to Android. I've been searching for rendering issues with iOS, but haven't found anything related. One other possible issue could be the large number of texts I am creating, drawing on bitmapdatas and after that destroying. I am currently exploring bitmaptexts, although I do need the fill for different colours,
  3. Hello, no I am not using TileSprite. In fact, I am preloading very few assets into the game, almost everything is drawn within the game onto bitmapdatas and then displayed into sprites via sprite.loadTexture()
  4. Hello, I have encountered a problem with iOS, which I haven't been able to address so far and I was wondering, if someone maybe has an idea of what could be going on. I have a cordova-crosswalk Sudoku puzzle game which runs great on a large variety of Android devices, including Samsung Galaxy S2 and Note 1. Apart from bringing groups to top, there is nothing else in the update as the entire game logic revolves around input signals. To my knowledge, the game is decently optimized, given how well it performs on the aforementioned 6-year old devices. The problem comes with iOS. I have t
  5. Update: A colleague of mine accidentally found while testing on a dual-monitor system that the issue was actually experienced only on a 144hz monitor. As he moved the browser to his second 60hz monitor, tweens were running ok. The PC I had the issue on was with AMD's FreeSync enabled and running at 120hz. Once I reduced those to 60hz, tweens were fine as well. I actually never gave it a thought that screen refresh rates can have an impact on tweens.
  6. I've just discovered this issue as well. Still no workaround? Edit: I just found out that the onDown event works correctly on Edge and is a viable alternative. Previously I had a check in update where I listened for pressed input such as: // if (this.cursorKeys.left.isDown && this.inputReleased) { // do something} This was bugged for me on Edge as OP described. However, manually assigning an arrow key and triggering an onDown event works okay for me. For example: this.leftKey = this.game.input.keyboard.addKey(Phaser.Keyboard.LEFT); And then the binding: this.lef
  7. Actually, autoadjustment for daylight saving time will only trigger this once per year since the issue is with rolling back a clock, not forward. However, a player can manually change their PC clock for some reason. Also, I haven't tried yet waiting for an hour because a standard full session in these games will most likely continue not more than 30 minutes before starting over. I will try out what you suggested, thanks a lot!
  8. Hello, I just encountered the following issue. In two different games I am using two ways of updating the game time shown in the UI - a timer and a timed event. I've just discovered that changing the PC's clock by -1 hour (say it's 10:00 AM, I roll it back to 9:00 AM) causes the updating to stop. This issue is not present if I roll the clock forward (from 10:00 AM to 11:00 AM). I found a way around this by using setInterval and clearInterval, but I'd like to know if a Phaser internal fix or workaround exists, or maybe if I need to do something differently. Here is the case when using a timer:
  9. Thanks for the reply. Well the thing is, this behavioral issue is the same across all 10 puzzle games, which use various tweens. I don't really know what block of code to post as a showcase since something as simple as tweening the y position of a sprite from its current position to 50 pixels below happens notably slower than intended (for example, I've set a duration of 200 ms and it visibly happens much slower, about two times slower). The PC in question has the latest drivers for its components and the latest Chrome and Firefox versions. I too guess it's something hardware related and don't
  10. Thanks for the reply. This, however happens across multiple games and on a single specific PC. Furthermore, in most of the games the core logic is triggered by event listeners, nothing is in the update really.
  11. Further testing revealed that the same issue is experienced on Firefox. I forgot to mention that the PC is running Windows 10, and if it's of any importance, it uses an i5 4570 CPU with an R9 290 gpu.
  12. Hello, I've recently encountered a very strange behavior on a specific PC. I've been testing about 10 Phaser puzzle games, which use various tweens for visualization. I've played the games on quite a few desktop PCs, including a Mac, and more than 10 different mobile devices, Android and iOS. On only 1 of the PCs all games exhibit an aberrant behavior where tweens seem to be running slower than their duration states. I couldn't find anything in the Internet about what could cause this issue. Even a simple alpha tween with a certain duration, no delay and autostart is acting weird. Phaser 2.4.6
  13. Bump, I am experiencing this as well. Works fine on android but having this issue on an iPhone 6S and Mac mini.
  14. Hello all, I was wondering, is there a way to change the used renderer at some point after the game has been created.
  15. Thanks for the cool method, lewster32, it is awesome. It works perfect on Chrome, Firefox and Edge on Phaser 2.4.4. For those of you using TypeScript, here is the code: private tweenTint(spriteToTween:Phaser.Sprite, startColor:number, endColor:number, duration:number):void { var colorBlend = {step: 0}; this.game.add.tween(colorBlend).to({step: 100}, duration, Phaser.Easing.Default, false) .onUpdateCallback(() => { spriteToTween.tint = Phaser.Color.interpolateColor(startColor, endColor, 100, colorBlend.step, 1); }) .start() }; You can also
  • Create New...