Skip to main content

direct x coding, part 5

To draw a monster arhetype, you have to first uproot your own system
direct x data, initialize a direct x monster attributes server table,
then sort all of the data into a separate close database and then

print all you want to the fence and then to the screen. Direct x 12
fence works like a render memory for the computer. To update the
fence, you can use the server command line.

--fence

This will send all the data you need to the windows operating system,
so that it will be available to the direct x (12) at all times. 
Another tool you can use to apply direct x 12 coding is git, so you

can push the fence data to your repository. That is in the case you
actually have any in the datafiles, as you will not be pushing the
hardware data directly.

--push(fence)

This will push the entire current fence data to the repository. You
can then filter that data to see if there's something useful you need.
To do this, you will most likely have to use the command line

terminal. Once you have the data in the repository, see if there's
something that you actually need. The graph I made in second part
was printed by the fence. I wouldn't want to bother coding a program,

that makes a window, because there is already a tutorial made that
does that. And there is another tutorial made you can find on the
web on Google that explain how the fence works, regarding making

windows. Instead I'm making one that helps you understand how the
fence and the video pipeline work. To understand how to use direct x
12 code works is an opportunity and a important tool asset to have.

Labels:

Comments

Post a Comment

Popular posts from this blog

object oriented programming

Object oriented programming is a sound and bold approach to c++ and internet wiring application and video games. It reduces a lot of code messes, made by global and half global functions. One of the more advanced object programming techniques are private access, poly morph and object message inheritance. It is set by c++ bjarne stroustrup and iso isometric standard convention comitee to use classes instead of structs and structures for making objects. Which means you most definitely should , but not must or have to. class Monster {     std::string memory_attributes{}; public:     void treck();     void track();     void trace(); }; The treck() function makes the monster roam and do human like jogging and trimming. track() means the monster goes ai path tracking and trace() means it tries to find other monsters in the area. class Weapon {     std::string memory_attributes{}; public:    void use(); }; void Weapon::use() {   ...
Post a Comment
Read more

object render, part 3

 Making a object requires a class call, but also has to be rendered. Monster monster{}; monster = new Monster[10]; void render_monster(Monster* monster_array); The iso c++ standard says you should use classes for making objects, not structs(structures). Considering it is a standard.  With emphasis on  should , not  must . It is a standard, not a coding rule. It was set forth by iso commitee and bjarne stroustrup. Polymorphism allows us to make multiple monster arch map types. virtual void render_monster(std::string map_name, int type=0); Atch map is a data map about what all is happening in the game, like for example campaign map. It allows making archetypes. monsters, for more efficient run time memory and pointers managing bugs and random access memory. Random access memory can hold quite many objects. class BackPack {     std::string inventory_node{}; };
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