Skip to main content

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 walls can be seen on the

outside, which is something you have to take into account while
rendering. The truth is, that loading 1 mega byte of data can take
insane ammounts of time, which is a huge problem in pentagon.

A very complex objects to render are corridors and tunnels. Which is
why ceilings are hard to render, as they carry immense weight. To
render a character, before the game starts, it has to be rendered

standing with arms diagonally from the shoulders. Then moved into
the right position, also use this technique for rendering spawned new
characters. Preload them, in other words.

void pre_load(int character_list_element)
{
    static std::vector<Character> character_list{};
    
    in_advance_draw(character_list.get(character_list_element);
}





Comments

Popular posts from this blog

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.

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

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!