Skip to main content
↑
↓
Spherical forums
Community for the
Sphere game engine
New?
Contact Us
to register an account!
1 Hour
1 Day
1 Week
1 Month
Forever
Community
Help
Search
Recent Posts
Log in
Contact Us
News
Spherical
Facebook
-
Twitter
-
Discord chat
New?
Contact us
to register an account!
Sphere Development
Sphere Support
Feasibility of custom map engine in Sphere 1.5
previous
1
2
Print
Topic: Feasibility of custom map engine in Sphere 1.5
(Read 9632 times)
previous topic
-
next topic
0 Members and 2 Guests are viewing this topic.
Fat Cerberus
Big Chungus
Posts: 2,774
*MUNCH*
Logged
Global Moderator
Sphere Developer
Re: Feasibility of custom map engine in Sphere 1.5
Reply #15
–
January 23, 2015, 11:32:51 pm
@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
No idea how that ever worked...
Last Edit
: January 23, 2015, 11:37:04 pm by Lord English
neoSphere 5.9.2
-
neoSphere
engine -
Cell
compiler -
SSj
debugger
forum thread
|
on GitHub
Flying Jester
Legendary Poster
Posts: 1,161
Logged
TurboSphere Developer
Re: Feasibility of custom map engine in Sphere 1.5
Reply #16
–
January 23, 2015, 11:56:12 pm
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
Learn some history?
The Flying Jester's Blog of Sorts
previous
1
2
Print
Sphere Development
Sphere Support
Feasibility of custom map engine in Sphere 1.5