Skip to main content

Level design basics, part 15

Game design and level design

They are very closely related. A good method is to make separate
document, that shows the relation points. Game design is like an arch
type to all other documentations. Which of course includes the level

design. One documentation doesn't go without the other. They are co
related, and both very important; two documents should do for the
entire documenation: of course as a document I don't mean 1 page or

any thing like that. Because an entire documentation of either can be
in one extensive document. But for better understanding and
comprehension; by then two documents are optimal. Level design

documentation is mostly and most oftenly a part game design
documentation. Level design is paramount part of game design. It
supports the whole structure together. It is very important, in other

words. A good way to start doing that is by making a separate game
design document. Or a level design section. Write all the references
to the level design documentation. What they both share in common is

the word "design". Designing a level is more than just planning it
and then designing it. They inter vine with each other. They are co
related. They don't go one with out the other. And so they both

require a giant ammount of effort. Making a campaign takes time,
effort and dedication. Game design basically covers all game aspects,
what makes it out standing from other games, game play querks,

challenges. Level design is not only writing about levels, but
covers data as well. So can game design. Data is crucial for the game
to not over flow the computer system with memory information. It has

to be stored in data bases. Game data design can quickly cover a lot
of game design and level design in over lap. Data is a very complex
infomation structure. A data unit basically contains a lot of bits

of information. So there is actually a lot of document over lap
between game design and level design. They are very deeply inter
related. As they cover all other design parts of the game, including

code design.

Comments

Post a Comment

Popular posts from this blog

static mesh render

Static mesh is a data compound of a three dimensional object in time and space. To render one, it takes a one big storage file that contains all the data about the object. That data has to be stored on a disk drive. The really tricky meshes to render are the flying ones. It's a completely different air pressure. The data gets written to a game memory log, it's a massive multiplayer online game, otherwise in the cloud, like Steam. To render one, the data from the level and monster data files to the monitor handling chip. Monitor handling chips vary based on personal computers, lap tops, operating system, processor and graphics car. Before a three dimensional object can be rendered it has to be fixed on memory, either random access memory or the disk drive recovery point. A three dimensional object data can take quite a large amount of memory, especially those used multiple times. Steam Cloud has it's own of handling data, so that it is persistent. A level is made of static m...
Post a Comment
Read more

object render

To render objects with c++, it is first required to load them on the engine's heap. After loading the object it has to be integrated into the game engine's allocated memory. void integrate() {     direct_x_node.call(); } Modern games(after doom 2) take an insane amount of heap memory. Integrating all the objects on the level, can take 400 mb or random access memory (ram). The same memory has the chip effect on the working of the central processing unit. To completely render the object, the first step is to load all the textures, shadow models, parts, particles, inner model, render the object on the level map, all the corelations with the heuristics. It is very hard to render the inner part of the objects, such as anatomy or infra structure. While it is perfectly fine to just render the inner part to not be displayed.  The anatomy of a player character or non player can be seen on the outside, and the internal strurcture of a level object such as a building, including the ...
Post a Comment
Read more

object render, part 4

Object is either two dimensional, or three dimensional. Even abstract ones. People imagine c++ game objects as a part of a class on a graph chart, to understand the game and development mechanics. But they are really two dimensional, iso metric or three dimensional. They can be seen on the level or the level map, in other words, about 90% of used classes. Even server objects can be seen on the game, if there is any blue print or underlying real world net working mechanism. So in other words, the class objects can be used in game. They have to be dimensional. //PvE class Monster {     std::vector<int>  head_memory{};     std::vector<int> body_particles{}; public:     int get_memory(int element);     int get_particles(int element);     int get_head_memory_size();;     int get_body_particles_size(); }; Monster's head memory is used for AI render, the body particles list is used for rendering. 60 frames per second...
Post a Comment
Read more