Forge Android App: 11-13-2016 Alpha 1.5.58.002

[jtrowell]

I found a bug : the start button is always active.

Exemples of situations where it shouldn't be active/visible :
- when finishing a challenge in quest mode, even if you don't have any more challenge you can click again on the start button and this will relaunch the last challenge again.
- when loading a quest, you can click on the start button before the programm has finished scanning for existing quests (so no quest is selected yet), resulting in an error message.

[johnny5ive]

I'm not sure if this is the right location to post this, but, whenever I start a Commander game(I only have the android version of this program), the life totals are starting at 30. Aren't they supposed to start at 40?

Thanks

Kwaiden

For 1v1 commander, it's actually supposed to be 30. 40 is for 3+ player commander.

Not exactly. French EDH is an alternate form of EDH tailored to competitive 1v1. In French life totals do start at 30 but French is not the default for 1v1 EDH. French is a separate format with a separate ban list. For example, Sol Ring is banned in French. By default a 1v1 EDH game follows the regular rules of EDH as laid out by the RC. Life totals should start at 40.

French should be a separate option.

[drdev]

I'm not sure if this is the right location to post this, but, whenever I start a Commander game(I only have the android version of this program), the life totals are starting at 30. Aren't they supposed to start at 40?

Thanks

Kwaiden

For 1v1 commander, it's actually supposed to be 30. 40 is for 3+ player commander.

Not exactly. French EDH is an alternate form of EDH tailored to competitive 1v1. In French life totals do start at 30 but French is not the default for 1v1 EDH. French is a separate format with a separate ban list. For example, Sol Ring is banned in French. By default a 1v1 EDH game follows the regular rules of EDH as laid out by the RC. Life totals should start at 40.

French should be a separate option.

Is French EDH another name for Duel Commander?

[johnny5ive]

Yes. I guess French is an unofficial name. I don't play it myself.

[Scion of Darkness]

Description: [describe what you were doing when the crash occurred]

NullPointerException | Open

Code: Select all

Forge Version:    1.5.40.003
Operating System: Linux 3.4.0-cyanogenmod-gb4db2ef armv7l
Java Version:     0 The Android Project

java.lang.NullPointerException: Attempt to invoke interface method 'void forge.card.CardZoom$ActivateHandler.activate(int)' on a null object reference
   at forge.card.CardZoom.fling(CardZoom.java:157)
   at forge.Forge$MainInputProcessor.fling(Forge.java:565)
   at forge.toolbox.FGestureAdapter.touchUp(FGestureAdapter.java:221)
   at forge.toolbox.FGestureAdapter.touchUp(FGestureAdapter.java:158)
   at com.badlogic.gdx.backends.android.AndroidInput.processEvents(AndroidInput.java:360)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:420)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1522)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1239)


Ransom deck custom game

[gbraad]

The app is built using libgdx 1.5.5, which uses OpenGL. Not sure about OpenGL ES. Can your e-book run other OpenGL-based applications/games?
What happens when you try to run it? Do you get an error, maybe logged in Forge/data/forge.log?

Hi, sorry for the belated response. OpenGL ES 2.0 seems to be used... but I believe it should be possible to have a software fallback mode? Correct me if I am wrong...

At least, the error I see is the following:

Code: Select all

FATAL EXCEPTION: main
java.lang.ExceptionInInitializerError
Caused by: com.badlogic.gdx.utils.GdxRuntimeException: Couldn't load shared library 'gdx' for target: Linux, 32-bit
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load gdx: findLibrary returned null


The device does not do OpenGL, but it is running Android on an i.MX6 (boox T68). A full stack exception can be found as a Github gist by id: 0235597a6a778266f49f. I can't paste the link yet...

I'll try to reinstall the application and see if this would fix the issue.

[sharkus]

Hello All,

I am running the alpha 1.5.40.003 on a galaxy S4 ver: lollipop and when I tap on any of the content downloaders the app freezes and then crashes after navigating away from the app.

I took a look at the forge/data/forge.log and this line was in repetition taking up most of the .txt

at forge.screens.settings.GuiDownloader.show(GuiDownloader.java:101)

Is this a bug or maybe I did something incorrectly?

New to this app and new to programming.

Thanks!

I'm also having this problem on my Nexus 9.

[gbraad]

Code: Select all

FATAL EXCEPTION: main
java.lang.ExceptionInInitializerError
Caused by: com.badlogic.gdx.utils.GdxRuntimeException: Couldn't load shared library 'gdx' for target: Linux, 32-bit
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load gdx: findLibrary returned null


I'll try to reinstall the application and see if this would fix the issue.

I guess the issue may have been caused by the following:

Code: Select all

shell@android:/sdcard $ pm install -r forge-android-1.5.40.003-signed-aligned.>
        pkg: forge-android-1.5.40.003-signed-aligned.apk
Failure [INSTALL_FAILED_DEXOPT]


I uninstalled the application and reinstalled, and now it says:

Code: Select all

I/ActivityManager(10705): Start proc forge.app for activity forge.app/.Main: pid=17240 uid=10112 gids={1015, 3003}
I/imx6.gralloc(10225): Display Request: 204 (0, 0) - (1440, 1080)  mode = 0x5 flags = 0x0
I/imx6.gralloc(10225): Display Request: 205 (0, 0) - (1440, 1080)  mode = 0x5 flags = 0x0
D/dalvikvm(17240): Trying to load lib /mnt/asec/forge.app-1/lib/libgdx.so 0x414e7300
W/ProcessStats(10705): Skipping unknown process pid 17318
D/dalvikvm(17240): Added shared lib /mnt/asec/forge.app-1/lib/libgdx.so 0x414e7300
D/dalvikvm(17240): No JNI_OnLoad found in /mnt/asec/forge.app-1/lib/libgdx.so 0x414e7300, skipping init
D/libEGL  (17240): loaded /system/lib/egl/libGLES_android.so
D/libEGL  (17240): 3D hardware acceleration is disabled
D/AndroidRuntime(17240): Shutting down VM
W/dalvikvm(17240): threadid=1: thread exiting with uncaught exception (group=0x40a191f8)
E/AndroidRuntime(17240): FATAL EXCEPTION: main
E/AndroidRuntime(17240): java.lang.RuntimeException: Unable to start activity ComponentInfo{forge.app/forge.app.Main}: com.badlogic.gdx.utils.GdxRuntimeException: Libgdx requires OpenGL ES 2.0


The whole stacktrace is available at https://gist.github.com/gbraad/2afc31ff9733a08e9ad0. So it seems "Libgdx requires OpenGL ES 2.0" is explanatory enough... however, is a software rendering mode available?

Edit: submitted this question also on the LibGDX forum at http://www.badlogicgames.com/forum/view ... 11&t=19407

[Agetian]

In r29444:29445, I fixed an issue which allowed the player to cheat: the game used to spoil practically all the card information about face-down cards (P/T, name, text, mana cost) if the card back image (hidden.jpg) was not available in the game cache and the game was set to "card image view" mode. Currently the implementation is very simple and the result looks a bit ugly - basically it draws the Forge art (from the theme) on top of the card to emulate a card back. It ends up being stretched so it looks somewhat weird. The method CardImageRenderer::drawFaceDownCard can be improved to make it look better, I would welcome any help in making it look better than it currently is.

- Agetian

[tasteful]

Not sure if this bug is actually specific to android but if you use Channel and then play a card, if you click the channel effect in order to pay the cost and then say "no" when the Pay Life? prompt comes up, the spell will be cast anyway, with no life payment.

[drdev]

So I'm excited to finally share a first look of the new Landscape mode match screen. Let me know what you think.

Hopefully I should have Landscape mode ready to release for Android tablets soon.

Thanks.
-Dan

[philocritus]

So I'm excited to finally share a first look of the new Landscape mode match screen. Let me know what you think.

LandscapeMatchScreen.png

Hopefully I should have Landscape mode ready to release for Android tablets soon.

Thanks.
-Dan

Looks awesome! Good work!

[johnny5ive]

So I'm excited to finally share a first look of the new Landscape mode match screen. Let me know what you think.

LandscapeMatchScreen.png

Hopefully I should have Landscape mode ready to release for Android tablets soon.

Thanks.
-Dan

It looks really nice. Although, personally, I'd like it flipped. Hand on the left and the other information/zone switcher on the right. Would making it user selectable be an option? Again, it looks really nice, though.

[drdev]

So I'm excited to finally share a first look of the new Landscape mode match screen. Let me know what you think.

LandscapeMatchScreen.png

Hopefully I should have Landscape mode ready to release for Android tablets soon.

Thanks.
-Dan

It looks really nice. Although, personally, I'd like it flipped. Hand on the left and the other information/zone switcher on the right. Would making it user selectable be an option? Again, it looks really nice, though.

The main reason it's on the right is because the two fields wouldn't line up with one hand open and the other not (which is the default state). Plus it would shift the entire field anytime you toggled the zone visibility. The only way it would work on the left is if it both players had this area always shown. If you think a setting to do so would be desirable, let me know and I'll consider it.

Thanks for the feedback.
-Dan

[Agetian]

Great job on the landscape mode thus far, Dan! Looks great to me!
By the way, not sure if you have taken care of it already, but I noticed that some of the latest SVN builds for Android (post-1.5.40.003) had an issue with the user being unable to scroll certain pull-up windows (most notably "Add Basic Lands") in standard portrait mode. Also, in that same window the "basic land set" list appeared in the wrong place and it was impossible to scroll it. Just wanted to put it here as a reminder so that it can be taken care of before the next build goes live (provided, of course, that it wasn't remedied already - I haven't checked ).

- Agetian