api21 is for android 5.0+. If you have 4.1-4.4.x, you can only use api16. “Installation” instructions should be displayed in the launcher, but rough description is in the post with the first version [forum.vcmi.eu/t/vcmi-for-android/784/164)
Maybe it would be possible to change these forced full redraws into partial draws (redrawing only hero tiles + neighbors(?)) because nothing except hero animation changes there. I might try looking into it (at some point).
Sooo I built new packages, but they’re quite weird this time and I’m not sure if they work correctly (honestly, compiling them feels very random). It works correctly on my 7.1 device, but I was unable to start the app on any emulator (tested on three different ones and each one is broken in a different way…). I don’t know, I might need to downgrade sdk/ide or something if it doesn’t work for others.
right-clicking support (two modes, switchable in launcher; personally, after some testing I find relative cursor very weird but I’ll leave it there),
intro doesn’t appear frozen anymore (after interrupting intro, screen is cleaned + progressbar is displayed); this might also possibly fix HarryPhoon’s problem with artifacts on the sides, buuut I don’t know,
hack that might make hero movement animations slightly smoother.
I just updated from the previous version of vcmi that I had and everything went smooth. On my device, Lenovo P2 with Android 6.0.1, the game works absolutely amazing. The right click is working very well and the hero movement is so smooth now. I’ve played for a few minutes with no crashes and bugs at all. Thanks for the excellent release, Fay!
Few things I noticed:
[ul] ]Relative cursor mode doesn’t seem to work very well, literally disappears after trying to press right click and you can move it off screen as much as you want, to the point where you completely lose it, thanks for adding it so fast though, if you’re gonna fix it and don’t mind working a bit more on it add sensitivity too, would be useful./:m] ]While intro seems much nicer now it seems to take longer time to load (might be just a psychological thing) and the sound of it disappeared (Actually now that I think about it, it may have not ever been there, if so dismiss this one), not something essential to the game but I think it worked previously./:m] ]Right clicking is pretty nice, takes a few clicks initially to get used to since one of your fingers always cover the information table but just moving fingers while you don’t have them released solves the problem./:m] ]Walking seems a little bit smoother now, but further optimisation would go a long way./:m][/ul]
Will edit if I find more stuff, thanks for the update! Oh also meant to ask, are there any performance differences between 16 and 21 API versions? And if not, what’s the point of making two different ones? Also why does this update take up three times as much space compared to the last one?
Okay, you’re right. That’s because I wanted to do it without adding more java<=>c communication so I didn’t have any reliable info about an actual cursor position and had to guess sometimes. I changed it to get the cursor directly from SDL an it works substantially better. Still can go offscreen though; not sure if I can limit it to actual game bounds.
The only things I changed there is clearing screen + displaying progressbar. Definitely nothing that could affect the loading speed.
I’m not sure about the sound because I always have it turned off. If it was there previously, it should still be there.
Okay, so the short answer is “it’s complicated”. I could probably get away with building only one package. I’m not sure about some details but generally:
android device can have one of 5 architectures (arm, arm-v7a, arm64-v8a, x86, x86_64); 64-bit ones require api21 (android 5.0+) and I think x86 needs api18 (android 4.3+),
all arm-based archs should work “normally” with applications built for normal arm, but x86-based devices will probably not,
I assume when the arch doesn’t match, the performance is works becuse there needs to be some translations,
running arm application on 64-bit device is probably the similar case as running 32bit applications on 64bit pc (slower, more limited, but usually not really noticable).
Currently the api16 package contains only arm arch and api21 contains all 5.
Because, for some reason, the apk file has no compression. I assume this is some kind of bug in android build system, because I can’t see any settings to change it and previously it was compressed normally. You can test this by unpacking the apk file (it’s just a zip) – both packages have ~313MB after unpacking.
Actually… never mind. That’s definitely not possible, because the screen follows the hero during movement.
the biggest change (but not very important from the player’s perspective) is that I gave up on gradle-experimental build and returned to stable gradle (+external cmake), because it felt really unstable and required some nasty hacks to work “correctly”; additionally I changed ndk to newest version (r15 b1) and replaced libc++ with gnustl, because it’s more stable and “default” in ndk
at the moment, due to the previous point, the application doesn’t work correctly on armeabi (compiler crashes during SDL build) or api <21 (runtime crashes, probably due to some boost<>ndk conflicts); oh well, according to google, ~70% of phones are 5.0+ already; I’ll be monitoring ndk/gradle updates, hopefully it gets fixed at some point
you need to uninstall previous version before installing this one (different app signing because of release mode and stuff)
everything is compiled in release mode and should work much quicker (haven’t played enough to see big difference in-game, but app startup on my phone was ~12s previously and is ~3s in this version)
app should no longer crash/hang when it goes into background or screen is turned off (hopefully),
due to the fact that android can kill application in background at any time it wants to, vcmi now tries to make autosave when the app is about to be killed (_Android_Autosave file); not guaranteed to work, because it’s not very elegant solution for now,
better relative cursor mechanics (as discussed in previous posts) + relative pointer speed multiplier setting in launcher,
added adventure map swipe support (as an alternative to relative pointer); doesn’t feel very smooth but should be functional (launcher -> pointer mode -> “normal with map swipe”)
added sound/music settings in launcher (because it’s irritating that these can’t be changed right away after starting the game ),
launcher should correcly preserve all vcmi config settings (previously launcher would drop settings that it didn’t understand (everything except resolution and codepage))
back button should now work like alt+f4 (closes app if in menu, displays exit confirmation if in-game)
I’ll try to look into it and and ping some Android developers I know and in IRC.
No good answer for this. One important point: is all code changes merged in develop?
If no this is what you need to start with. We’ll also benefit if you join our organization on github and move build system repository here.
And for building stable version I really not sure if it’s worth to wait since this would be quite long waiting probably. Like I wish to have tons of time to test and merge everything, but I only have so much…
In same time we don’t have any working version for Android at all so I don’t think we’ll make it worse.
Is that a problem at all? I don’t think anyone care what package name is and if xyz going to get some weird credit for his previous work that not problem too.
That’s better to be solved one way or another.
Is there any way to detect when application was updated from older version? If there is then it’s would be enough to notify users who updated it that path files changed and they need to move assets. I doubt anyone seriously playing older version since it’s wasn’t really playable at time, many might have it installed.
Also once we get new version I want owner of this one to get it unlisted: play.google.com/store/apps/deta … vcmi&hl=en
Or if he agrees he can transfer ownership too. Then we could update it once and suggest to install another app instead and then unlist it so it’s not confusing anyone.
Well, technically I am an android dev.
3rd party licenses definitely should be placed somewhere in the launcher.
Don’t know about policy, because vcmi doesn’t really do anything with user data – the only thing that could qualify is probably sdcard reading/writing.
Do you mean my changes in vcmi? Currently they’re here github.com/Fayth/vcmi/tree/android-support – I can start a pull request to vcmi/develop if that’s what you mean… probably not today though. I tried to wrap all android-specific logic in VCMI_ANDROID define so hopefully the won’t be any problems, but currently I don’t have any environment installed to check if the desktop version complies correctly.
Sure. I think it’s a good idea that vcmi team has the ownership over this.
If you feel that the current vcmi/develop version is stable enough to be published then there’s no problem on my side.
No technical problems. Only the fact that google suggests that your app’s id should reflect the domain that you own. But it’s not really a problem, because it’s not a hard rule, just a guideline.
No built-in mechanism. Usually apps just save previously launched version number and check it on startup.
In our case, we should probably try to detect datafiles in the old location and move them if possible. Should be doable.
Sadly this is something I have like zero idea about so all I can do is just google it.
Just create pull request and Travis will compile it.
We’ll also be able to find if there something need to be fixed.
Welcome to team! If seriously we obviously not give everyone access to main repository since not everyone actually need them, but I think github have teams inside organizations so there no problem to invite you and then let you control repositories you want and non-develop branch.
Warmonger / AVS might need comment on this though since I don’t have full permissions on github.
I don’t think it’s stable, but it’s far better than 0.97 for sure.
I think they forgive us. Or we could ask for ownership over other package later that in fact represent our domain.
So for instance we can let Fay to keep Android-specific changes in main repository branch even without giving develop (protected branch) push access. Of course we can also just ask nicely to not push directly anything unless it’s absolutely obvious and tested fix.