1. Introducing Channels - a new way to chat with other Android users!
    Dismiss Notice

Sky Force - developer needs feedback


Last Updated:

  1. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    Hi,

    Sky Force was recently released for Android and I'm looking for a feedback from people with HTC Hero, Motorola CLIQ and Nexus One.

    [​IMG][​IMG][​IMG]

    Here is a list of problems reported for those devices:

    Hero:
    Some people reported performance problems on HERO, could you please try Sky Force LITE and let me know if performance is really that bad? I've tried it on G1 and as long as you play using accelerometer the framerate is pretty smooth. When you start playing in touch mode it drops badly but thats a hardware limitation that we currently can't overcome. I think for now I should just disable it for Hero like devices.

    Motorola CLIQ:
    One person reported that it crashes on that device. Could you please confirm?

    Nexus One:
    Game works but something is wrong with resolution. Could you please take a screenshot when graphics is corrupted?

    The devices that we have are Android G1 and Motorola Droid.

    If you have any other device and found any issues - please let me know!

    Any feedback is appreciated. Please help us making this game better for Android users.

    Thank you in advance!
    Marek
    Infinite Dreams
    http://www.idreams.pl
     

    Advertisement
  2. turbosol16

    turbosol16 Well-Known Member

    Joined:
    Jan 2, 2010
    Messages:
    250
    Likes Received:
    9
    I think a trackball control option might be good to add. I think it would be easier to control on a Nexus with the trackball.

    I tried touch controls and I didn't see a drop in frame rate but if you can add a option so you can setup the offset of the ship to your finger that may be helpful to some.

    Can't take a screen shot but I did see the error with the resolution, it happens all the time.

    The Demo is really short, you might need to give people more to see before they shell out money.

    Nice graphics and it seems like a good game.
     
  3. Doc Savage

    Doc Savage Well-Known Member

    Joined:
    Jan 13, 2010
    Messages:
    45
    Likes Received:
    0
    Good game, it reminded me of my youth playing Raptor Call of the Shadows. :)

    I tested the lite version. It works fine on the HTC Magic (32B running Cyanogen 4.2.13)

    Playing on N1, there are graphics distortions. The forum wanted me to resize the screenshots to 620x280, so I've thrown them onto my server here (excuse the slow connection.)

    On the Nexus I got a 'Force close' when clicking the Purchase game on the scoring screen. This didn't happen on the Magic.

    Here is the appropriate lines from logcat:
    Code (Text):
    1. I/ActivityManager(   67): Starting activity: Intent { act=android.intent.action.VIEW dat=http://www.idreams.pl/redirect/id_skyforce_android_full.html cmp=com.android.browser/.BrowserActivity }
    2. E/Surface (  855): invalid token (-1, identity=0) or client (0x0)
    3. D/AndroidRuntime(  855): Shutting down VM
    4. W/dalvikvm(  855): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
    5. E/AndroidRuntime(  855): Uncaught handler: thread main exiting due to uncaught exception
    6. E/AndroidRuntime(  855): java.lang.RuntimeException: Unable to pause activity {com.idreams.skyforcelite/com.idreams.skyforcelite.game}: java.lang.NullPointerException
    7. E/AndroidRuntime(  855):     at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3162)
    8. E/AndroidRuntime(  855):     at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3119)
    9. E/AndroidRuntime(  855):     at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:3102)
    10. E/AndroidRuntime(  855):     at android.app.ActivityThread.access$2400(ActivityThread.java:119)
    11. E/AndroidRuntime(  855):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1870)
    12. E/AndroidRuntime(  855):     at android.os.Handler.dispatchMessage(Handler.java:99)
    13. E/AndroidRuntime(  855):     at android.os.Looper.loop(Looper.java:123)
    14. E/AndroidRuntime(  855):     at android.app.ActivityThread.main(ActivityThread.java:4363)
    15. E/AndroidRuntime(  855):     at java.lang.reflect.Method.invokeNative(Native Method)
    16. E/AndroidRuntime(  855):     at java.lang.reflect.Method.invoke(Method.java:521)
    17. E/AndroidRuntime(  855):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
    18. E/AndroidRuntime(  855):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
    19. E/AndroidRuntime(  855):     at dalvik.system.NativeStart.main(Native Method)
    20. E/AndroidRuntime(  855): Caused by: java.lang.NullPointerException
    21. E/AndroidRuntime(  855):     at com.idreams.skyforcelite.MyGLSurfaceView$AudioThread.kill(game.java:341)
    22. E/AndroidRuntime(  855):     at com.idreams.skyforcelite.MyGLSurfaceView.onPause(game.java:304)
    23. E/AndroidRuntime(  855):     at com.idreams.skyforcelite.game.onPause(game.java:132)
    24. E/AndroidRuntime(  855):     at android.app.Activity.performPause(Activity.java:3782)
    25. E/AndroidRuntime(  855):     at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1190)
    26. E/AndroidRuntime(  855):     at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3149)
    27. E/AndroidRuntime(  855):     ... 12 more
    28. I/Process (   67): Sending signal. PID: 855 SIG: 3
    29. I/dalvikvm(  855): threadid=7: reacting to signal 3
    30. E/Adreno200-EGL(  855): egliGetNativeWindowSize: unable to dequeue native buffer
    31. I/dalvikvm(  855): Wrote stack trace to '/data/anr/traces.txt'
    32. E/Surface (  855): invalid token (-1, identity=0) or client (0x0)
    33. E/Adreno200-EGL(  855): egliGetNativeWindowSize: unable to dequeue native buffer
    34. I/ActivityManager(   67): Starting activity: Intent { act=android.intent.action.VIEW dat=http://www.idreams.pl/redirect/id_skyforce_android_full.html cmp=com.android.browser/.BrowserActivity }
    35. W/dalvikvm(  855): threadid=13: thread exiting with uncaught exception (group=0x4001b178)
    36. E/AndroidRuntime(  855): Uncaught handler: thread GLThread 12 exiting due to uncaught exception
    37. E/AndroidRuntime(  855): java.lang.RuntimeException: eglMakeCurrent failed: 12291
    38. E/AndroidRuntime(  855):     at android.opengl.GLSurfaceView$EglHelper.throwEglException(GLSurfaceView.java:938)
    39. E/AndroidRuntime(  855):     at android.opengl.GLSurfaceView$EglHelper.createSurface(GLSurfaceView.java:878)
    40. E/AndroidRuntime(  855):     at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1097)
    41. E/AndroidRuntime(  855):     at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:975)
    42. I/Process (   67): Sending signal. PID: 855 SIG: 3
    43. I/dalvikvm(  855): threadid=7: reacting to signal 3
    44. W/ActivityManager(   67): Process com.idreams.skyforcelite has crashed too many times: killing!
    45. D/ActivityManager(   67):   Force finishing activity com.idreams.skyforcelite/.game
    46. D/ActivityManager(   67): Force removing process ProcessRecord{44c0a740 855:com.idreams.skyforcelite/10069} (com.idreams.skyforcelite/10069)
    47.  
     
  4. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    Thank you so much for such a professional feedback. :)

    For Nexus One all is clear, corrupted area should be black - it will be very easy to fix. Crash is probably related to killing audio thread.

    Anyway, have you noticed any problems with framerate on Nexus One? Does the game run smooth with no or very little graphics tearing?

    What about the HTC Magic. I understand that it works smooth using accelerometer. What if you switch to touch control (in options)? I can see very visible slowdown on G1 in touch control mode.

    Anyone with Motorola CLIQ or HTC Hero tried the game?

    Thank you so much for your help!

    Marek.
    Infinite Dreams
    http://www.idreams.pl
     
  5. Doc Savage

    Doc Savage Well-Known Member

    Joined:
    Jan 13, 2010
    Messages:
    45
    Likes Received:
    0
    Your welcome. :)

    Framerate on the N1 is fine, no tearing what so ever, it was a joy to play. Both with touch and accelerometer.

    Just tried touch on the Magic, it works smooth with both control methods and again no tearing.
     
  6. arlissfreire

    arlissfreire Member

    Joined:
    Dec 28, 2009
    Messages:
    17
    Likes Received:
    0
    I will test, this is one of my favorites.
    Don't forget to think about an alternative to sell it out of the market.
    We owners of some models of unlocked android phones are misprized by google.

    update: works! touch control very responsive in Motorola Milestone.
     
  7. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    Thank you all for your feedback. I'm really happy to hear that HTC Magic has better touch driver than G1.

    Anyone with HTC Hero or Moto CLIQ? Or any other Android device not mentioned earlier?

    best regards,
    Marek
    Infinite Dreams
    http://www.idreams.pl
     
  8. kutsushita

    kutsushita Well-Known Member

    Joined:
    Nov 19, 2009
    Messages:
    56
    Likes Received:
    2
    Sprint Hero user... game functions beautifully, no loss of graphics or anything except the touch controls (which of course is hardware.)
     
  9. mattcoz

    mattcoz Well-Known Member

    Joined:
    Nov 28, 2009
    Messages:
    60
    Likes Received:
    2
    Yeah, it's pretty choppy on the Hero. Not so bad that I couldn't play it, but still.
     
  10. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    Thank you everyone for your feedback.

    So I think I should simply disable touch control option for G1 and Hero. Unfortunately threre is nothing else I can do. For some people it's better to disable functionality that does not work perfectly so they don't have anything to complain about. :)

    Thank you again!

    best regards,
    Marek
    Infinite Dreams
     
  11. arlissfreire

    arlissfreire Member

    Joined:
    Dec 28, 2009
    Messages:
    17
    Likes Received:
    0
    Will it affect other devices that do not have the trackball?
    In the case of the Droid/Milestone it does not have the d-pad nor trackball.
     
  12. Gremlin256

    Gremlin256 Well-Known Member

    Joined:
    Nov 13, 2009
    Messages:
    319
    Likes Received:
    14
    will it work on droid?
     
  13. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    It already does work on Droid very well (I have one!).

    All I'm gonna do in next update is disable touch control for HTC HERO only.

    On all other devices it's gonna be possible to play using accelerometer and touch.

    best regards,
    Marek
    Infinite Dreams
    http://www.idreams.pl
     
  14. phillevy

    phillevy Well-Known Member

    Joined:
    Aug 27, 2009
    Messages:
    501
    Likes Received:
    15
    I gave up playing on my Hero - even using accelerometer it was very choppy - I used to have this on my Nokia N82 and Dell Axim 51v and it was always fast and smooth. Also can't the trackball be an option on the Hero?
     
  15. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    On G1 when you play with touch it's really slow. When you play with accelerometer - everything is smooth. Looks like things are much worse on Hero. I guess I'll have to try it by myself on Hero.

    I'm sorry to say but both Axim 51v and N82 have better hardware for games than first generation Android devices.

    On G1 whatever you touch (screen or trackball) framerate drops significantly. New generation (like Droid or N1) are joy to work with.

    best regards
    Marek
    http://www.idreams.pl
     
  16. phillevy

    phillevy Well-Known Member

    Joined:
    Aug 27, 2009
    Messages:
    501
    Likes Received:
    15
    Thanks for your concern - I'm really disappointed and hope that you can possible scale the game to be more playable on the Hero - I'm surprised how it highlights the gaming deficiencies of the Hero, but have to say, this is the first market game that I have encountered such performance issues.
     
  17. redandblack1287

    redandblack1287 Well-Known Member

    Joined:
    Dec 4, 2009
    Messages:
    144
    Likes Received:
    3
    Game is very choppy in touch mode, but it is absolutely unplayable in accel. mode--please do not disable the touch option.

    If the Hero can ever run at 528mhz instead of 384, I'm sure this game will run fine. Otherwise I think that even adding trackball functionality will be futile, but it never hurts to try, right? ;)
     
  18. benjers

    benjers Member This Topic's Starter

    Joined:
    Jan 18, 2010
    Messages:
    14
    Likes Received:
    5
    Ok, I understand that something is wrong with SkyForce on Hero. I need to get this device then.

    It's really strange because it's running pretty well on G1 which is more or less the same hardware as Hero.

    Anyway, thank you for letting me know!
     
  19. redandblack1287

    redandblack1287 Well-Known Member

    Joined:
    Dec 4, 2009
    Messages:
    144
    Likes Received:
    3
    The G1 probably runs at 528, not 384, but I really have no idea. Good luck fixing it, I will buy it immediately if you can get it running smoothly.
     

Share This Page

Loading...