It may be because of that, I’ve tried it on 6.0 and below. @javasabr, are you using Android 7 too?.
I’ll try to test it in an emulator (the google apis are a bit painful with them), and try to find out if it is an engine issue or I messed it up with viewports.
I’m running it on Android 8.0 (Nexus 5X) and it’s fine.
I installed it immediately after work yesterday, but wanted to play it a bit before giving feedback. I like the concept - never seen other games like that, so it feels original. Great job on the artwork. Gameplay is challenging, but not too hard. The only thing I don’t like is the ads - I know that’s your revenue stream from the game so you can’t cut them entirely, but it would be nice if they were only in the menus and not visible during the levels. That said, they are unintrusive and not all up-in-your-face like some mobile ads, so kudos for that.
Difficulty seems about right - I get frustrated and bored when games make you play 500000x repeat battles to get enough gold/points/whatever to upgrade units enough to pass the level you’re stuck on. I got stuck a few times so far, but not so badly as to be too frustrating (10 or fewer tries usually enough to progress).
About the issue with Android 7, I’ve tried to run the app in an emulator but the game doesn’t even start (however, it does on Android 8).
Anyway, whenever I try to enter a match, the app crashes in the emulator with this already filled bug so I can’t really fix it by now :S.
Just tried it.
It’s pretty nice. Graphics sound and music works really well.
The game is fun, though I had a hard time figuring out what to do. I ended up tapping around to finally find something I could interact with.
Once you get how it works it’s simple, but I guess the tutorial should be more explicit.`
In the UIs I also got lost a bit.
In the inter fight UI, where you can buy stuff, I went into all the options and leveled up some units, then I couldn’t figure out how to go back to the battle.
I finally figure out you have to click on the map and choose the destinations.
I think the confusion comes from this big “FIGHT” panel on the left side that I couldn’t click on…
Not sure why it’s there.
Anyway…I’ll continue playing a bit it’s quite fun, I’ll give you more feedback.
Well, thanks to everybody for the feedback. I’m not changing this game anymore but it will be useful for future ones.
@nehon, I don’t know if you are trying to track the problem with Android 7 or how is the progress abut this, but I got a crash report from a SM-T550 (7.1.1 - Nougat) containing the trace:
java.lang.IndexOutOfBoundsException: index=2304 out of bounds (limit=1653)
at java.nio.Buffer.checkIndex(Buffer.java:528)
at java.nio.ByteBufferAsFloatBuffer.get(ByteBufferAsFloatBuffer.java:95)
at com.jme3.collision.bih.BIHTree.initTriList(BIHTree.java:87)
at com.jme3.collision.bih.BIHTree.<init>(BIHTree.java:135)
at com.jme3.collision.bih.BIHTree.<init>(BIHTree.java:139)
at com.jme3.scene.Mesh.createCollisionData(Mesh.java:992)
at com.jme3.scene.Mesh.collideWith(Mesh.java:1033)
at com.jme3.scene.Geometry.collideWith(Geometry.java:460)
at com.jme3.scene.Node.collideWith(Node.java:611)
at com.jme3.scene.Node.collideWith(Node.java:611)
at com.jme3.scene.Node.collideWith(Node.java:611)
at com.simsilica.lemur.event.PickEventSession.cursorMoved(PickEventSession.java:534)
at com.simsilica.lemur.event.PickEventSession.cursorMoved(PickEventSession.java:433)
at com.simsilica.lemur.event.PickEventSession.buttonEvent(PickEventSession.java:610)
at com.simsilica.lemur.event.TouchAppState.dispatchButton(TouchAppState.java:132)
at com.simsilica.lemur.event.TouchAppState$TouchObserver.onTouchEvent(TouchAppState.java:185)
at com.jme3.input.InputManager.processQueue(InputManager.java:837)
at com.jme3.input.InputManager.update(InputManager.java:907)
at com.jme3.app.LegacyApplication.update(LegacyApplication.java:725)
at com.jme3.app.SimpleApplication.update(SimpleApplication.java:227)
at com.jme3.app.AndroidHarnessFragment.update(AndroidHarnessFragment.java:577)
at com.jme3.system.android.OGLESContext.onDrawFrame(OGLESContext.java:342)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1557)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1268)
If I try it on an emulator, I get an endless:
01-27 16:39:47.027 3532-3584/? E/emuglGLESv2_enc: a vertex attribute index out of boundary is detected. Skipping corresponding vertex attribute. buf=0x77b91d290db0
01-27 16:39:47.027 3532-3584/? E/emuglGLESv2_enc: Out of bounds vertex attribute info: clientArray? 0 attribute 1 vbo 113 allocedBufferSize 1380 bufferDataSpecified? 1 wantedStart 0 wantedEnd 261124
01-27 16:39:47.027 3532-3584/? E/emuglGLESv2_enc: a vertex attribute index out of boundary is detected. Skipping corresponding vertex attribute. buf=0x77b91d290e50
01-27 16:39:47.027 3532-3584/? E/emuglGLESv2_enc: Out of bounds vertex attribute info: clientArray? 0 attribute 2 vbo 115 allocedBufferSize 4140 bufferDataSpecified? 1 wantedStart 0 wantedEnd 783372
I think that posting here the bug wasn’t the better idea. For future references, please comment android 7 bugs related in this other post (seems fitter to the subject)
