I’ve got a game that uses several layers. The bottom layer is a storyboard layer that changes when the user moves from room to room. There are several layers on top of the storyboard layers for the menu buttons, the inventory slide out, the game text, and special effects layers. Each of these layers are several objects grouped together. There are essentially 5 layers above the storyboard layer.
The problem is that when an object on the story board layer is clicked on a kindle fire (or HD) device, as well as several other android devices, there is about a one second delay before the click is registered. If the user clicks on any of the objects on any of the layers above the storyboard layer the click is pretty instant, it’s just the storyboard layer that’s slow.
It’s causing me to get some negative reviews.
Why does the storyboard layer have such a delay in the clicks on these devices, when the other layers are fine. I haven’t tested an app with just storyboard and no other layers, but I’m wondering if it would have the same delay? Is there anything I can do to get it to be more responsive? [import]uid: 11193 topic_id: 34344 reply_id: 334344[/import]
Storyboard is pretty snappy in most cases. Does the performance get worse over time or is it just bad from the start?
[import]uid: 199310 topic_id: 34344 reply_id: 136522[/import]
it’s slow right off the bat. [import]uid: 11193 topic_id: 34344 reply_id: 136525[/import]
Can you start by removing the various layers, perhaps one at a time and see if the storyboard gets better?
[import]uid: 199310 topic_id: 34344 reply_id: 136610[/import]
I was hoping to avoid this (removing the various layers to test) because those extra layers are all intertwined and required and would be a lot of work to remove them enough to really give it a good test. But if no one else is experiencing slow tapping response times using the storyboard api, I guess that’s a good thing. I was hoping to use it with my next game as well, but it’s a game where timing on your taps is extremely critical, so if I wanted to make sure storyboard isn’t usually slow like in my current game.
[import]uid: 11193 topic_id: 34344 reply_id: 136722[/import]
Storyboard is pretty snappy in most cases. Does the performance get worse over time or is it just bad from the start?
[import]uid: 199310 topic_id: 34344 reply_id: 136522[/import]
it’s slow right off the bat. [import]uid: 11193 topic_id: 34344 reply_id: 136525[/import]
Can you start by removing the various layers, perhaps one at a time and see if the storyboard gets better?
[import]uid: 199310 topic_id: 34344 reply_id: 136610[/import]
I was hoping to avoid this (removing the various layers to test) because those extra layers are all intertwined and required and would be a lot of work to remove them enough to really give it a good test. But if no one else is experiencing slow tapping response times using the storyboard api, I guess that’s a good thing. I was hoping to use it with my next game as well, but it’s a game where timing on your taps is extremely critical, so if I wanted to make sure storyboard isn’t usually slow like in my current game.
[import]uid: 11193 topic_id: 34344 reply_id: 136722[/import]