Collectible Card Game Headquarters

Ok I updated one of my tablets to .005 and I'm now giving it a try. As of right now, I can't even make it go ingame past the menus (as in the "show me the match screen") - it loads up, then I click "Constructed" and "Start" (with all options on default), it shows me the "Loading new game..." overlay and then just hangs on it forever, it seems. I tried waiting for about 10 minutes but it was to no avail.

P.S. I recompiled all the modules with "Clean and Build", including the desktop and mobile-specific ones, before making the .apk and publishing.

- Agetian

That's odd. I just installed .005 and I was able to start a match without issue. Could it be an issue with the decks you're using?

That said, it's still as laggy as before, so obviously the Android API version had nothing to do with it.

drdev wrote:That's odd. I just installed .005 and I was able to start a match without issue. Could it be an issue with the decks you're using?

That said, it's still as laggy as before, so obviously the Android API version had nothing to do with it.

Hmm not sure, but I just tried the random color match (two colors: Random 1 / Random 2) for both Human and AI several times. This is the usual configuration I go for, so it's nothing out of ordinary. If it was just lagging then the lag was terrible for my old tablet because 10 min wasn't enough to go into the match UI...

- Agetian

My match started with almost no delay on my S4 phone. When I said lag, I meant during combat.

drdev wrote:My match started with almost no delay on my S4 phone. When I said lag, I meant during combat.

I'll try a different tablet soon (a newer one) and will report how that goes
By the way, is there any way to profile an Android app to see where it's lagging so much (e.g. during combat)?

- Agetian

Ok, still doesn't start the match for me (even on a different tablet, this time Samsung Galaxy Tab Pro 10.1 2014 - a really new one with a 8 core CPU and Android 4.4). I tried preconstructed decks and I tried random color decks, still no go. The music is playing, I can hit "back" to go back to the main menu screen, but every time I hit Start it just sits there forever with "Loading new game..." shown on my screen.

- Agetian

Agetian wrote:Ok, still doesn't start the match for me (even on a different tablet, this time Samsung Galaxy Tab Pro 10.1 2014 - a really new one with a 8 core CPU and Android 4.4). I tried preconstructed decks and I tried random color decks, still no go. The music is playing, I can hit "back" to go back to the main menu screen, but every time I hit Start it just sits there forever with "Loading new game..." shown on my screen.

- Agetian

I'd recommend using LogCat in Eclipse to investigate what's going on. I assume this doesn't happen if you just run forge-gui-mobile-dev as a Java app, right?

drdev wrote:I'd recommend using LogCat in Eclipse to investigate what's going on. I assume this doesn't happen if you just run forge-gui-mobile-dev as a Java app, right?

I'll try forge-gui-mobile-dev when I'm back home and I'll report back. Also, I'll try recompiling and reinstalling the .apk on my tablets (probably after wiping the old Forge) to see if that helps. I don't have an active Eclipse installation though, and even provided that I did (I can install it if necessary), I have no idea how to use LogCat... is there a tutorial of any sort that would explain how to go about it?

- Agetian

Agetian wrote:

drdev wrote:I'd recommend using LogCat in Eclipse to investigate what's going on. I assume this doesn't happen if you just run forge-gui-mobile-dev as a Java app, right?

I'll try forge-gui-mobile-dev when I'm back home and I'll report back. Also, I'll try recompiling and reinstalling the .apk on my tablets (probably after wiping the old Forge) to see if that helps. I don't have an active Eclipse installation though, and even provided that I did (I can install it if necessary), I have no idea how to use LogCat... is there a tutorial of any sort that would explain how to go about it?

- Agetian

You could try Googling it. It basically just monitors what's going on in an attached Android device.

Ok I'll see if I can figure it out and get a development environment like that going on my PC. I'll keep you posted in case I manage to set it up.

- Agetian

Bug in version 1.5.28.002

I know the version is not the latest, but I doubt that it has seen attention since this version.

I play duress and the opponent has multiple possible cards in hand. I choose one, then un-choose it. When I want to select a new one, all the options are selected and I can't choose only one. It wants to discard them all. Both the Auto and OK buttons are grayed out.

Re-tested .005 (both "stock" and the one updated to the latest trunk) on both my tablets after a full recompile. Still no go, doesn't go past the "Loading new game..." screen within any reasonable time frame. The "forge-gui-mobile-dev" thing works fine on my desktop. Can anybody else please test .005 to see if it works for you or not? (in particular, whether you can go inside the match or not).

EDIT: Here's what the game log says, Forge actually goes into an exceptional state:

Code: Select all

(ThreadUtil first call): Running on a machine with 2 cpu core(s)
Language 'java.util.PropertyResourceBundle@420a07b0' loaded successfully.
Read cards: 14302 archived files in 68408 ms (25 parts) using thread pool
Read decks (973 ms): 0 constructed, 0 sealed, 0 draft, 3 cubes, 0 scheme, 0 planar, 0 commander.
AI profile Reckless was chosen for the lobby player Alana.
java.lang.IllegalStateException: forge.FThreads.assertExecutedByEdt may not be accessed from the event dispatch thread.
   at forge.FThreads.assertExecutedByEdt(FThreads.java:23)
   at forge.util.WaitCallback.invokeAndWait(WaitCallback.java:23)
   at forge.GuiMobile.showInputDialog(GuiMobile.java:157)
   at forge.util.gui.SOptionPane.showInputDialog(SOptionPane.java:80)
   at forge.util.gui.SOptionPane.showInputDialog(SOptionPane.java:72)
   at forge.player.GamePlayerUtil.getPlayerNameUsingFirstTimePrompt(GamePlayerUtil.java:100)
   at forge.player.GamePlayerUtil.setPlayerName(GamePlayerUtil.java:79)
   at forge.match.MatchUtil.startGame(MatchUtil.java:131)
   at forge.screens.match.MatchController.startNewMatch(MatchController.java:116)
   at forge.match.MatchUtil.startMatch(MatchUtil.java:106)
   at forge.screens.LaunchScreen$1.run(LaunchScreen.java:74)
   at forge.screens.LoadingOverlay$1$1.run(LoadingOverlay.java:33)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:408)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1524)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1248)


- Agetian

Agetian,

I'm able to run .005 without issue on my stock Nexus 5. Combat is still a little laggy, but I haven't run into any of the match issues you're having.

Agetian wrote:Re-tested .005 (both "stock" and the one updated to the latest trunk) on both my tablets after a full recompile. Still no go, doesn't go past the "Loading new game..." screen within any reasonable time frame. The "forge-gui-mobile-dev" thing works fine on my desktop. Can anybody else please test .005 to see if it works for you or not? (in particular, whether you can go inside the match or not).

EDIT: Here's what the game log says, Forge actually goes into an exceptional state:

Code: Select all

(ThreadUtil first call): Running on a machine with 2 cpu core(s)
Language 'java.util.PropertyResourceBundle@420a07b0' loaded successfully.
Read cards: 14302 archived files in 68408 ms (25 parts) using thread pool
Read decks (973 ms): 0 constructed, 0 sealed, 0 draft, 3 cubes, 0 scheme, 0 planar, 0 commander.
AI profile Reckless was chosen for the lobby player Alana.
java.lang.IllegalStateException: forge.FThreads.assertExecutedByEdt may not be accessed from the event dispatch thread.
   at forge.FThreads.assertExecutedByEdt(FThreads.java:23)
   at forge.util.WaitCallback.invokeAndWait(WaitCallback.java:23)
   at forge.GuiMobile.showInputDialog(GuiMobile.java:157)
   at forge.util.gui.SOptionPane.showInputDialog(SOptionPane.java:80)
   at forge.util.gui.SOptionPane.showInputDialog(SOptionPane.java:72)
   at forge.player.GamePlayerUtil.getPlayerNameUsingFirstTimePrompt(GamePlayerUtil.java:100)
   at forge.player.GamePlayerUtil.setPlayerName(GamePlayerUtil.java:79)
   at forge.match.MatchUtil.startGame(MatchUtil.java:131)
   at forge.screens.match.MatchController.startNewMatch(MatchController.java:116)
   at forge.match.MatchUtil.startMatch(MatchUtil.java:106)
   at forge.screens.LaunchScreen$1.run(LaunchScreen.java:74)
   at forge.screens.LoadingOverlay$1$1.run(LoadingOverlay.java:33)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:408)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1524)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1248)


- Agetian

Ah, it looks like your issue is you don't have a name saved, so it's trying to prompt you for a user name when it shouldn't be able to. That explains it. That also explains why you couldn't reproduce on your desktop, and why I'm not seeing the same problem.

I should have a fix for that ready shortly, at which point you can release 1.5.28.006.

Ahhh, OK, gotcha! Thanks! Yes, will be happy to release an updated version.

- Agetian