Skip to main content


Topic: Feasibility of custom map engine in Sphere 1.5 (Read 6374 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • Fat Cerberus
  • [*][*][*][*][*]
  • Global Moderator
  • Sphere Developer
Re: Feasibility of custom map engine in Sphere 1.5
Reply #15
@Jester: I just ran the math on your huge maps:

4096x4096 with 16x16 tiles at 32 bits per pixel = 4096*4096*16*16*4 = 17,179,869,184 bytes, or 16GB(!) per image!  And that's just for one layer!  You said you were doing 8, which brings it to a whopping 128GB :o  No idea how that ever worked...
  • Last Edit: January 23, 2015, 11:37:04 pm by Lord English
Sphere 5.6.2 - neoSphere engine - Cell compiler - SSj debugger
forum thread | on GitHub

Re: Feasibility of custom map engine in Sphere 1.5
Reply #16
Hmm, maybe I remember wrong. Most of my maps were for randomly generated environments, so I usually didn't have to actually fill them out by hand.

Not all maps had so many layers though (usually less, the Majestic made most normal uses of layering kind of silly), and not all maps were so large.

I usually only did stuff like that for demos of terrain generation, or for SimCity style, modifiable maps. Which tended to have fewer layers.
  • Last Edit: January 24, 2015, 03:19:37 am by Flying Jester