I almost always ignore rpgmaker titles as they tend to be lazily made and not fun to grind throughIn my rather varied experience, few things are actually better in RPGMaker. I would almost go as far as to say that nothing is "better" in RPGMaker, just generally simpler to make.
FIXED.Android copy crashes for me
How large is the APK, APKs larger than 2gb rarely run, so maybe that's the issue? Also depending on how you've handled the file system in android, sometimes you have to grant the APK write permissions (usually I've only seen this if the save location isn't in the default Android>Data>appname system folder) manually, rather than receiving a popup requesting them.FIXED.
I tested it on Android and it was crashing for me as well, even though the package was successfully compiled.
Anyway, I have recompiled it and tested it and it is working now, so re-download an Android version from the opening post.
However, I can't get the Android version of v0.5.5 of the game to run, even though there is no problems in compiling it. The apk installs and then simply closes before after the "Ren'Py" loading screen appears.
I've spent hours trying to figure this out but nothing is obviously wrong. This is on v8.3.7 of Ren'Py. If the tools aren't working, I won't be able to offer a developer-original Android version after v0.4.0.
Any error messages on crash?FIXED.
I tested it on Android and it was crashing for me as well, even though the package was successfully compiled.
Anyway, I have recompiled it and tested it and it is working now, so re-download an Android version from the opening post.
However, I can't get the Android version of v0.5.5 of the game to run, even though there is no problems in compiling it. The apk installs and then simply closes before after the "Ren'Py" loading screen appears.
I've spent hours trying to figure this out but nothing is obviously wrong. This is on v8.3.7 of Ren'Py. If the tools aren't working, I won't be able to offer a developer-original Android version after v0.4.0.
May I suggest asking on theI've spent hours trying to figure this out but nothing is obviously wrong. This is on v8.3.7 of Ren'Py. If the tools aren't working, I won't be able to offer a developer-original Android version after v0.4.0.
Btw. I just wanted to say that I really like your games. The art style (stellar incognita) is unique and the different paths make it really enjoyable. I kinda had to get used to the art, but I really liked it eventually. Thx for your efforts.I did a reinstall of renpy and associated modules and Android porting seems to work for now. No idea what was wrong, though. There werenever any error messages.
I spoke too soon.I did a reinstall of renpy and associated modules and Android porting seems to work for now. No idea what was wrong, though. There were never any error messages.
There has to be some kind of log, debug mode or otherwise error output. Tough to help without access to any of it.I spoke too soon.
I tried a new Android version of the latest update for the game and it failed.
1) Build is successful - no error messages.
2) APK installs with no issue.
3) Click on the icon on an Android device and the RenPy loading screen starts.
4) Program abruptly closes at the RenPy loading screen.
There were no error messages at all, but then I found something when I went to "Clean" up the Android packaging project. It seems RenPy couldn't find some images to clean up, but they were clearly included in the package. The issue may have been that for images, I use a lot of nested folders and the directory tree can get quite deep. I note that with some programs, once a directory address gets long enough, programs can no longer understand and find them.There has to be some kind of log, debug mode or otherwise error output. Tough to help without access to any of it.
Again... it's quite tough for me to help without having any access to it, but...There were no error messages at all, but then I found something when I went to "Clean" up the Android packaging project. It seems RenPy couldn't find some images to clean up, but they were clearly included in the package. The issue may have been that for images, I use a lot of nested folders and the directory tree can get quite deep. I note that with some programs, once a directory address gets long enough, programs can no longer understand and find them.
So I cut the image directory tree in half and made it more shallow, having a Pt 1 and Pt 2 of the images. That seems to have worked.
We'll see when I try and make the next build if that was the issue.