Android Version


#61

[quote=“hatcher, post:58, topic:13348”]You should check options in-game. There’s a bug, when spawn modificators droping to the default value after game starts. I’ve played with 1 in item and zombie spawn modificators very long, until i noticed that crap.
Fixing is pretty easy: go to the save folder, change the values and put a only-reading flag after.[/quote]

Actually I think what happened with me was I was just being dumb :slight_smile: I had started a new game several times but I forgot to generate a new world so the settings were still the same as before.


#62

Elirector: Flick up on a shortcut to remove it. If you remove all shortcuts, it will reset the entire shortcut row to defaults for that screen.

StopSignal: Thanks! No donations necessary but appreciate the thought - I shall have a beer in my honour, haha. I make games for a living, so this is just a fun side project while I have the spare time.


#63

FOUND FIX TO PLAY WITH TILES IF YOU GET GARBLED TEXT!

It’s pretty simple actually, you only need a file exploring app.
What you’re going to do is go to the app’s folder (root/sdcard/Android/data/com.MichaelDavies.CataclysmDDA/files/) and move the GTX folder somewhere easy to find later (IE “sdcard” folder). Now, launch the game and go to the options. Enable software rendering and close the game. Move the GTX folder back into the “files” folder and you’re ready to go!
The game should properly open now, and you should be able to play with tiles on.


#64

Nice one, well done :smiley: You can probably just rename the gfx folder to something else to stop the game from picking it up.

There is a known issue with the software renderer though: if you rotate the screen it will break. I’ve been looking into this problem along with the garbled text hardware acceleration bug for the last week. It turns out SDL (the graphics library Cata uses) on Android is riddled with weird bugs like these that only show up for certain devices. I’ve been able to reproduce the issues in their samples, so I don’t think it’s anything that the Cataclysm code is doing wrong. I’ve emailed their mailing list and posted on their forums about both issues, but haven’t heard anything back yet.

Turns out native Android development is a real pain in the ass! Trying to make something that works on ~20,000 totally unique devices with wildly varying hardware and capabilities is rather challenging. :slight_smile:


#65

Love the port and havent had any issues with it until today! Seems the game crashes when I attempt to manually control vehicle turrets ): Using a Moto G4 if that helps! No way im goibg to be able to kill this tank drone without using the turrets on my vehicle…


#66

In theory, can i update the game by replacing data files? Found couple of shitty bugs, incompatibilities and unbalanced code which has been fixed in later experimentals.
Eg crash after hitting “f” inside of a vehicle with empty hands, turrets manual control crash, broken minireactor , PK rebalance debug errors etc.
Or tell how you compiled it, pls.


#67

Thanks for letting me know RE: instability issues in experimental.

I plan on periodically updating the build to latest experimental and putting the source code up on GitHub once the beta test is complete.

That said, yes you can update the data files yourself. Obviously this will only work for fixing data-only bugs, and if you’re using the Google Play version of the game and the app updates, on next launch it will refresh the game data (excluding custom soundpacks/tiles/mods and save games), so you’ll need to reapply the patches.


#68

I just rolled out a new version - download links + changelog in the first post of this thread.


#69

This update seems to have fixed that weird red screen bug!


#70

But my personal (i guess) bug appears again. After updating game doesn’t launching. Game even don’t see the new configs from first beta release. So i deleted everything, reinstalled and replaced configs with my old config folder. Now gotta change settings again, god damnit.
At least i have some brains and did save my character folder in other directory.


#71

RE: red screen bug, great news :smiley: Now If I can fix the other weird SDL bugs we’re seeing, we’ll be ready to release!

hatcher: Could you explain the steps you took in a a bit more detail to get it running on your device?
When you say you replaced configs, do you mean you copied over the ‘config’ folder with your old config folder?
I’m puzzled why you needed to uninstall/clear data to get it working again. When the app upgraded from the previous version (before you uninstalled it), did it say “Upgrading game data”, or “Installing game data”? (it should have said upgrading, just checking.)
When it upgrades the game data, it shouldn’t touch the ‘config’ or ‘save’ folders. It will only refresh data under ‘data’, ‘gfx’, ‘lua’, and ‘lang’, but will ensure any custom-added stuff like mods/soundpacks/tilesets will be preserved… I followed the logic that the desktop CDDA Launcher uses for this. So I’m confused why it wouldn’t launch after the app updated, since your old config should have still been working. Did you delete the gfx folder by any chance?


#72

[quote=“a1studmuffin, post:71, topic:13348”][/quote]
Ok, i’ll try to explain. For some reasons, game doesn’t creating any configs while first launch, except for fonts.json. I copied options.json and keybindings.json into the folder and it helped. After updating (it was “update”, not “install”) game didn’t deleted old saves, configs nor mods, but that weird bug appeared again. I guess, game didn’t see old configs, although those configs was accepted and successfully changed before. I checked all possibilities of invalid values in them, but found nothing. Didn’t touch those configs before update at all, but i copied em, just in case. File and folder permissions are OK.

Did you delete the gfx folder by any chance?
I dont get it. Gfx is just a tilesets, no? Anyway, i didn’t delete folder, but i deleted all tilesets, except for modded mrshock by xotto which im using.

Btw, without json configs logs are just empty. With json’s there’s alot of “couldn’t parse color” messages and thats it.
Im pretty sure something wrong on my side, but do not know how to find out whats going wrong without detailed logs.


#73

Thanks hatcher, much appreciated! Glad to hear it didn’t nuke any of your configs/saves/mods after the upgrade, I was pretty sure that would be the case but good to have it verified.

I believe the config json files (options.json + keybindings.json) are only created after you modify a setting or keybinding and save the changes. They aren’t created on the first run, which is the same behaviour as the desktop build. So I think that’s why you weren’t seeing them.

It sounds like the data upgrade caused your strange crash bug to appear again. It would have copied all the tilesets back again, so perhaps this was causing the crash somehow. Maybe it was crashing on startup because you deleted the other tilesets, or perhaps it was trying to load one of the default tilesets instead, causing your device to run out of memory. If the current tileset is missing, I think it will try and load “gfx/tinytile.png” as the fallback after that. It’s difficult to diagnose without having your specific device handy, but glad it’s working now for you anyway. Thanks for checking the logs too.


#74

[quote=“a1studmuffin, post:73, topic:13348”]Thanks hatcher, much appreciated! Glad to hear it didn’t nuke any of your configs/saves/mods after the upgrade, I was pretty sure that would be the case but good to have it verified.

I believe the config json files (options.json + keybindings.json) are only created after you modify a setting or keybinding and save the changes. They aren’t created on the first run, which is the same behaviour as the desktop build. So I think that’s why you weren’t seeing them.

It sounds like the data upgrade caused your strange crash bug to appear again. It would have copied all the tilesets back again, so perhaps this was causing the crash somehow. Maybe it was crashing on startup because you deleted the other tilesets, or perhaps it was trying to load one of the default tilesets instead, causing your device to run out of memory. If the current tileset is missing, I think it will try and load “gfx/tinytile.png” as the fallback after that. It’s difficult to diagnose without having your specific device handy, but glad it’s working now for you anyway. Thanks for checking the logs too.[/quote]

I’ll try mess around with this after next update :wink: But not now, i do not want to set everything on place again. It’s working – well, don’t touch it – that what i think.
Btw, game don’t need those configs for launch?? That will explain everything. Maybe one of the default options causing the crash, but after i loading modified config it dissapears. Yeah, that something with i can work next time.
Also, even the modded mrshock by xotto (32x32) do not causing out-of-memory crash on my device with crappy ≈480mb RAM. So, im not sure its truly the reason because first run crashing.

Protip: changing the font height from 16 to 14 in the fonts.json is giving lot of space for logs/minimap/enemy in sight list. Without drawbacks. Very helpful on devices with ≤5 inches. I expanded logs from 14 to 18 lines, and now i can freackin drive and see latest logs and the minimap at the same time.


#75

A1,

Thanks for doing this for all of us!

I’ve been having trouble starting the app after the process where the files are downloaded.
Here’s what has happened so far:

I first tried to run the app on my phone (5.?). Installation went smoothly but it wouldn’t go past the big Z splash-screen.
Then I tried installing on my tablet (6.1), same results.
After the tablet run failed I went back to the phone and dug around a bit until I found the options file.
I think I may have also moved the app to the SD card (via the app manager, not manually.)
I didn’t change anything on the phone’s files but the next time I tried to run the app it ended up launching and has successfully launched since then.

Unfortunately I haven’t been able to locate the same file on the tablet, yet. I did find the com.yourname.cdda, etc. files however. I’ve made no changes thus far.
The tablet remains stuck at the Z screen.

Do you have any thoughts on what may have caused the phone installation to finally work and what I might need to do to get the tablet working?

Thanks!
Taerzik


#76

A1,

I solved my own problem, sort of.

Going on a hunch from others’ issues here, I removed the graphics folder from my tablet and that allowed the app to launch fairly quicky.

That doesn’t quite explain what’s going on though.
My phone’s CDDA instillation seems to be loading with graphics now, while it was initially hanging at the Z screen.
But the tablet’s installation won’t load unless I remove or rename the graphics files.

I’ve tried launching CDDA with GFX file present and then looking at memory usage but it doesn’t appear to be going over a few MB during startup.
This makes me think that the problem isn’t the tiles themselves but some kind of problem with the loading process… unless there’s a corrupt file in there that is simply causing the launch to hang.

I would really like to be able to have graphics on my tablet, preferrably iso., but it’s only got a gig of memory total and I haven’t figured out how to get a swap file working yet to work around what might be a memory shortage.


#77

Heya, glad you’ve sort-of worked around it. I’m pretty sure this is an out-of-memory issue if you’ve only got 1GB RAM on your devices. What are the models + specs + android versions of your phone + tablet?

(Also, note to self - try and detect out of memory and display a proper message!)

On first run, after it installs the game data, the game will sit on the Z screen for a good 10-30 seconds (depending on how slow your device is) before launching. Could you have mistaken that for a freeze on your phone perhaps? That would explain why it worked on successive loads. (I should probably put a “LOADING” indicator on that screen as well as the Z.)

The game uses around 350-450MB (it might peak slightly higher than this too during load), and most Android devices use at least half a gig for the OS and other bits and pieces, so it’s definitely a squeeze and is probably failing to load tiles during startup… that’s why renaming the gfx folder fixes the issue, as it forces the game to skip loading tiles, thus reducing overall memory needed to start the game.

I was chatting with someone over email and they managed to get the Hoder’s tileset working when ChestHole wouldn’t, so perhaps that’s worth a shot. This was on a 2GB device too, so I’m wondering if some Android devices have issues loading the large tileset textures into memory… perhaps there’s a 4096/8192 limit on some of them…


#78

Awesome work! I’m interested though on whether you’re able to use tilesets on your HTC One M8, as I’ve had to rename the graphics folder to get the game to launch.

Also, how feasible would it be to be able to repoint the world and character folders to another location? I have CDDA as a folder in Google Drive, so the thought of being able to continue games both on the move and on my PC makes me giddy!


#79

Dan that’s a really sharp idea there! I love it!


#80

danabnormal: That’s interesting you’re unable to run with tiles on an HTC One M8. Perhaps you’re running some software that’s taking up more memory than I am? I’m running Cyanongenmod 14.1 (Android 7) which might also make a difference.

I’m wondering if I should default the game to not using tiles at all, since Android devices tend to have way less memory than PCs. This would mean more people would be able to launch the game on low-spec devices. They could try turning tiles on, but if it fails, they can just clear program data and relaunch again, try a different tileset etc. Might be a simpler flow for users than messing with the gfx folder?

RE: CDDA synced over Google Drive/Dropbox, I see no reason why it wouldn’t work, and I’ve been quietly waiting for someone to try it! :smiley: I think you would have good luck with something like Autosync Dropbox/Google Drive, assuming they work reliably (I haven’t tested either of them, but all the reviews seem positive):

Autosync Dropbox: https://play.google.com/store/apps/details?id=com.ttxapps.dropsync&hl=en
Autosync Drive: https://play.google.com/store/apps/details?id=com.ttxapps.drivesync&hl=en

The only thing to be aware of is that CDDA Android adds some extra json data to the save games to remember the touch shortcuts for various screens. These will be ignored (and overwritten) by the desktop version, so it means if you played on Android, then on desktop, then on Android again, the touch shortcuts would reset. It’s probably not a huge deal, but worth noting. If this becomes a heavily used flow by players, I could look at moving the shortcuts into their own separate json file to avoid this issue.