Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ Diposit Digital de l...arrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
image/svg+xml Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Closed Access logo, derived from PLoS Open Access logo. This version with transparent background. http://commons.wikimedia.org/wiki/File:Closed_Access_logo_transparent.svg Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao
versions View all 2 versions
addClaim

Motor Gráfico para Juegos

Authors: Ruiz González, Carlos;

Motor Gráfico para Juegos

Abstract

This project is about the construction of a game engine, the game engine's editor and a game. The game engine and editor are made with an Entity Component System architecture and with the technologies WinRt, DirectX and WIC, XAML was used to do the editor's GUI. The programming language used was C++, the IDE was Visual Studio Express 2013 and the target OS is Windows 8. The Direct X Game and Direct X and XAML App templates from Visual Studio Express 2013 were used as the base for the game engine and game engine's editor, respectively. In this memory it is explained concepts like Entity Component System and how it was applied to this project. The Entity Component System is initially explained from a Object Oriented Design perspective. Then, there's a little break from ECS, and there is a section about "the ability to deal with the cache of the computer of an OOD system". At the end, during the explanation of the implementation of the ECS, these two themes are brought together. Also, there are a few components of the engine that are explained more deeply. These components are the Graphic Engine and the Physic Engine. The Graphic Engine follows a simple approach that consist on using a Camera, and drawing everything that is inside that Camera. The Physic Engine follows a "not so traditional" approach. Basically, it updates every game object in the Y axis and then the collisions are managed, then it does the same but in the X axis. Also, the design done to create the ECS is explained. Which Components where made, how the Processors handle them and the Assemblages to generate more Entities. To create a game there are two steps. Firstly create it with the game engine's editor. Secondly, save it with the editor, the result will be a .txt file. Thirdly and finally, add that file to the game engine project, change the program to use that file and play the game engine.

Treballs Finals de Grau d'Enginyeria Informàtica, Facultat de Matemàtiques, Universitat de Barcelona, Any: 2014, Director: Oriol Pujol Vila

Country
Spain
Related Organizations
Keywords

C++ (Computer program language), Programari, C++ (Llenguatge de programació), Video games design, Bachelor's theses, Disseny de videojocs, Treballs de fi de grau, Computer software

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
    OpenAIRE UsageCounts
    Usage byUsageCounts
    visibility views 99
    download downloads 345
  • 99
    views
    345
    downloads
    Powered byOpenAIRE UsageCounts
Powered by OpenAIRE graph
Found an issue? Give us feedback
visibility
download
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
views
OpenAIRE UsageCountsViews provided by UsageCounts
downloads
OpenAIRE UsageCountsDownloads provided by UsageCounts
0
Average
Average
Average
99
345
Green