Good day to you all.
I have been using rpgmaker to make android deployed apps for about a year now.
I decided to update to 1.5 and I started a new project, however on deploy it failed and I was busy searching for an answer. I am unable to force a log on my pc for some reason, but I digress. Another user posted this( https://forums.rpgmakerweb.com/inde...r-for-android-deployment-in-rmmv-1-5-0.80359/ ) and I was able to see a crash log.
Guess what plugin seems to be the issue. the new Pixi.js
SO I did some testing.
Upgraded a project I have at 1.3.4 that did export and work to 1.5 = failure, crashed on start.
Made a new blank project in 1.5 = failure, crashed on start.
Took the project I made in 1.5 and 'downgraded' it with the js and index files of my old game = exported and works!!!!! (tho with some bugs due to misconfigs).
After these tests, I am fairly confident in stating that rpgmaker 1.5's new pixi cannot deploy to android at the moment, causing an undefined error immindately upon starting the app.
RPG Maker 1.5 will not delpoy to android.
● ARCHIVED · READ-ONLY
-
-
When I did update to 1.5 I got undefined error on startup too. I thought it was a plugin incompatibility.
-
When I did update to 1.5 I got undefined error on startup too. I thought it was a plugin incompatibility.
at first I also assumed so, however you can try to deploy even the base new project and even that fails. -
I had the same issue.
https://forums.rpgmakerweb.com/inde...r-for-android-deployment-in-rmmv-1-5-0.80359/
I wish there will be a official solution soon. -
We took a look into this.
Unfortunately, Intel XDK has no "document.fonts" on android and our issue in Graphics.js from the RMMV source code. In short, it's not exactly Pixi that's causing the problem but it seems like the community core script.
EDIT: Here's a temporary fix
line 1720 of rpg_core.js , add this line:
Graphics._cssFontLoading = false -
thanks, it seems to be working fine now. Is this font loading part of the performance improvement or it does not matter?We took a look into this.
Unfortunately, Intel XDK has no "document.fonts" on android and our issue in Graphics.js from the RMMV source code. In short, it's not exactly Pixi that's causing the problem but it seems like the community core script.
EDIT: Here's a temporary fix
line 1720 of rpg_core.js , add this line:
Graphics._cssFontLoading = false -
We took a look into this.
Unfortunately, Intel XDK has no "document.fonts" on android and our issue in Graphics.js from the RMMV source code. In short, it's not exactly Pixi that's causing the problem but it seems like the community core script.
EDIT: Here's a temporary fix
line 1720 of rpg_core.js , add this line:
Graphics._cssFontLoading = false
What about for people not using the intel XDK?
When I export my projects to android I use python, crosswalk and the apache ant.
Also in the project I exported I had deleted and disabled all plugins, including the community core.
Not at home atm, but when I get there i'll try the fix and see if the crash is resolved reply again.
(not trying to be picky, just hoping to solve all the issues).
EDIT:
Okay so I got home and made a project WITHOUT the community core script which still crashes.
Did the temp fix and the base project does indeed export and work now, however my method isn't intel xdk, but the method used in the help file tutorial. -
Community Core Script is just an append script. The OSS community edited the CORE scripts themselves. Did you follow the line instruction I told you to do so?
-
Community Core Script is just an append script. The OSS community edited the CORE scripts themselves. Did you follow the line instruction I told you to do so?
Yes. I mentioned it in the second part of my edit. I am getting projects to export by adding that line. -
Yes. I mentioned it in the second part of my edit. I am getting projects to export by adding that line.
I highly recommend posting in this github (or following the issue here). As the changes made by the JP Community is the one that caused it. -
I highly recommend posting in this github (or following the issue here). As the changes made by the JP Community is the one that caused it.
Alright. Thanks a lot for looking into it and doing what you could. your temp fix is working and you mentioned it there so hopefully if people are having issues they find this post and know the line to add.