Thanks for the feedback!
I just took a look at how the tilesets are laid out. I managed to include a tileset in double size (32x32 instead of 16x16), but it’s not very practical at the moment.
Do you want to work on that? //more info
If you want to experience the same thing you will have to edit
\FEXNA_Config\Source Code\Static Classes\Config Data\Constants\MapConfig.cs
starting in Line 6
make sure you edit your tilesets accordingly - animated tiles will look awful.
Maybe the default resolution of the tilesets was originally 32x32. This was originally the case with FEXP I think (because there are 32x32 tilesets in the working files). I’ve also seen people claiming that FEXNA uses the higher res natively.
I’m not sure myself if it’s worth the effort. I hope that not all assets would have to be rearranged.
Maybe someone who knows Yeti and can ask him if this is an easy endavour?
I’d be happy to get help here!
Anyway: Even if 32 px tilesets are not necessary, they could bring the following advantages:
- 16x16 tiles would still be usable on double size
- “Fake” 16x16 tileset art: you can change e. g. 1/4th of the pixel
- leaves room for improvement
- nice 32 px art would be possible
- and we could use the tileset from CMagister (however, it will still require a lot of work from us to create files for an entire game)
Disadvantage:
- Current zoom x1 would have to disappear (is this a disadvantage for you?)
- Larger files (it’s not game braking though)
- breaking with FE6-8 GBA limitation tradition
- real 32px art is hard
What do you think? Not that I have anything to say here, but: In which direction should Tactile develop?