Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 316 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
In this Discussion
Best format for map data
antix
Member
I am at the point in development in my 2d game engine where I would like to ask everyone how they handle map data as I am wondering what the best format to use woul be going forward.
To begin with, I'm not using Tiled, instead I have created my own map editor in Visual Basic. I chose this path because Tiled isn't really a game editor since it doesn't have any functions to create/edit animations, moving platforms, enemies, etc. It doesn't export LUA maps either, whereas myeditor does.
Method A: (currently using this) Store each map tile in one number and use bitwise operators to extract any required information when required.
TILE:
BITS DESCRIPTION
31 1 if solid
30 1 if animated
25-29 reserved
18-24 animation (0-127)
10-17 tile property (0-255)
0-9 tile number (0-1023)
Method B: Use multiple arrays, one for each case; tile, property, animation, animated, solid.
Now it seems that Method B would be quite quick because you aren't having to do loads if fiddley bitwise operators to extract map data all the time. It does however take up exponentially large amounts of RAM.
How else does everybody else store mapdata? And do people think method A or B (or something else) is better in the long run? any why?
To begin with, I'm not using Tiled, instead I have created my own map editor in Visual Basic. I chose this path because Tiled isn't really a game editor since it doesn't have any functions to create/edit animations, moving platforms, enemies, etc. It doesn't export LUA maps either, whereas myeditor does.
Method A: (currently using this) Store each map tile in one number and use bitwise operators to extract any required information when required.
TILE:
BITS DESCRIPTION
31 1 if solid
30 1 if animated
25-29 reserved
18-24 animation (0-127)
10-17 tile property (0-255)
0-9 tile number (0-1023)
Method B: Use multiple arrays, one for each case; tile, property, animation, animated, solid.
Now it seems that Method B would be quite quick because you aren't having to do loads if fiddley bitwise operators to extract map data all the time. It does however take up exponentially large amounts of RAM.
How else does everybody else store mapdata? And do people think method A or B (or something else) is better in the long run? any why?
Comments
Likes: antix
https://deluxepixel.com
Likes: antix
Likes: antix