![]() Moreover there would be no need for savegames since the hole game state is saved in the database. And I don't have to take care about data of objects far away. I could easily query data of objects near the player needed for rendering. I would not need objects for representing entities. The advantages of using a relational database like MySQL would be the data orientated structure which allows fast computation. Aside from keeping everything in memory, what alternatives do I have? Advantages Would Be Is a SQL database fast enough to use it for realtime reading and writing game informations, like the position of a moving character? I also need to care about cross-platform compatibility. Except of meshes and textures which are even more performance related, so I will keep them in memory. ![]() ![]() SQLite or MySQL, to store the game data? This contains virtually all game content like items, characters, inventories. Moreover, each component can read, edit, create and remove data. Each component can trigger and listen to events. There are many components like physics, input, sound, renderer, ai. My design decision is to use a data centered architecture where there is a global event manager and a global data manager. The programming language is C++ and it uses OpenGL. There will be a 3 dimensional world with first person view and it will be single player for now. I am planning a computer game and its engine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |