2014-02-04, 04:25 PM
(This post was last modified: 2014-02-04, 07:18 PM by StolenBattenberg.)
Alright, so a few new ideas to question and think about are bought into the 'SoM 2.0' plan, here's a few things I've been thinking about relating to it recently.
1) I completely underestimated the amount of map pieces which would actually be possible to have in each map, since I didn't CUBE it... I only thought about it as in one dimension, which would be 2047, but it's actually 2047x2047x511 (X, Y and z) you could have stacked, collision-able levels, and there won't be that weird bug where light is everywhere on the Y/Z.
2) Networking abilities... Now this I'm still thinking about, it would be easy enough to do but I'm not finding much of a use for it in a game like SoM, maybe for online updates etc.
3) A 'compiled' map is another idea added to my work table, I get the feeling having thousands of map tiles in a room, all using separate 'objects' would cause a lot of lag, so I'm going to try and put together a way that will take the data of a map, and turn it into one big map model when the game is compiled, sorta like how part files get written into binary when you're ready to release.
4) A new file to allow something I was putting off, you all having custom map pieces an available feature... This'll be done with a .SET file, which holds the map piece data... I'm not exactly sure how yet because I just thought of the idea an hour ago, and I think about this stuff while I'm programming etc... So far you can think of it as a massive registry for map tiles, which will be unique to each game.
If you wanted a more technical description, it's a massive list, which is loaded into the engine... The list contains link to each tile.prt file, the engine then loads each tile.prt file into an object which can be placed into the world. phew!
EDIT: preview of indev launcher, just trying some styles, i'll also be posting a IDE 'template' of what the SoM 2.0 IDE might look like, since it's gonna allow you to have ALL the tools open at once, rather than just one at a time...
1) I completely underestimated the amount of map pieces which would actually be possible to have in each map, since I didn't CUBE it... I only thought about it as in one dimension, which would be 2047, but it's actually 2047x2047x511 (X, Y and z) you could have stacked, collision-able levels, and there won't be that weird bug where light is everywhere on the Y/Z.
2) Networking abilities... Now this I'm still thinking about, it would be easy enough to do but I'm not finding much of a use for it in a game like SoM, maybe for online updates etc.
3) A 'compiled' map is another idea added to my work table, I get the feeling having thousands of map tiles in a room, all using separate 'objects' would cause a lot of lag, so I'm going to try and put together a way that will take the data of a map, and turn it into one big map model when the game is compiled, sorta like how part files get written into binary when you're ready to release.
4) A new file to allow something I was putting off, you all having custom map pieces an available feature... This'll be done with a .SET file, which holds the map piece data... I'm not exactly sure how yet because I just thought of the idea an hour ago, and I think about this stuff while I'm programming etc... So far you can think of it as a massive registry for map tiles, which will be unique to each game.
If you wanted a more technical description, it's a massive list, which is loaded into the engine... The list contains link to each tile.prt file, the engine then loads each tile.prt file into an object which can be placed into the world. phew!
EDIT: preview of indev launcher, just trying some styles, i'll also be posting a IDE 'template' of what the SoM 2.0 IDE might look like, since it's gonna allow you to have ALL the tools open at once, rather than just one at a time...