Skip to main content

Level design basics, part 9

 Memory

A level can take 100 mega bytes of random access memory which is taken
on each load. Play a match 20 times, you will have 2 giga bytes of memory
taken. So it is important to separate level files into 10 data base segments.

A navy level would be hard to make as it involves loading ships on the start
base. Saving memory is an important method when it comes to designing a
level. Design is important. That's what after all level design is all about. And

memory plays an important key role.

Database 1 "arena.lvl"
generic memory
RAM stack
geo

Memory design:

seal animal

This script code prevents the client user from reading confidential united
states army information used in the game. Made them a lot of troubles while
designing Doom 3. Memory is an important part of human brain; and also

of a personal computer. 90% of the human brain's memory has to be used
all the time. And under standing computer memory enchances human memory
and under standing level game design. Zero is a complicated number. It's hard

to understand, but is used for numero logy in designing computer memory.
And computer memory applications. Data base is a very large set of files that
take tons of memory. Seals are in the united states army, that's why the source

code can be applied when making navy goal levels. Generic memory uses c++
made memory templates from the standard template library. Random access
memory stack applies geo graphy methods that can be used to generate memory

nodes.

Comments

Popular posts from this blog

Level design basics, part 2

An arch level design is hard, as it doesn't involve only polygon boxes, but also also three dimensional curve lines. If you ever played. Americas army 1, you'll know how hard it is to make a curve building, like the famous over played bridge crossing map. The point is to start. With one curve. Curve is not a straight line, but it's still a line. Means it is possible to apply lines into a three dimensional level. arch 0 0 1 0

Level design basics, part 7

Meta files Meta means in between. Wild hard ware and soft ware connection. A game design level document is just documentation; it is normal text. Actual level files however are en coded. Not normal text, in other words; which is why they are a lot harder to make. Forests for example are hard to put into a text file. Trees are real world eco systems that are the source of nature and life. It is one thing to put a real world object into a game, what is even a LOT harder is putting one, for example a tree into a text file. Source code is just sofware, it is nothing but encoded writing, which is why to put it into soft ware is not exactly easy, but has been done many times before. However, putting source code directly into hard ware is a completely different thing. That's where meta files come in handy. Meta files are clay ware. They work very similiar to a human brain. Like a connection between software and hardware. A meta file contains level game design documentation and level code....

Coding

I find it extremely hard to code a game. It gets worse than that. I also have to do the game design, UI design, level design and the story. Basically lots of bugs, lots to learn, lots to design. The good news is I have a teammate and she works on level design and story. Helps a lot regardless there is tons of work to be done before even first of the three Trix games gets published. I sometimes work even 12 hours a day. Yikes!