[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 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.