• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
molehill mountaineer

Separating API specific code from the rest of the framework

6 posts in this topic

Hi guys,

 

So for the past few months I've been developing a little "pong meets arkanoid" game, learning directx and building a little framework as I go along. (I hesitate to call it an engine) 

 

Though frustrating at times, I do find it immensely satisfying and educational to work with something I built, so I hope to keep exanding (and correcting) this code for future projects, which brings me to my question: I would like to make  the code less dependent on API specific stuff (directx  in particular) so that I could, for example, render the game in openGL should I wish to do so.

 

The trouble is that I'm not quite sure how to seperate the rendering code from the game objects.

I gather I would have a class called "render manager" or something like that, with a pointer to a "renderer" base class - similar to the 'strategy' design pattern. How does one isolate the actual drawing of the object from the game code? Right now my game objects all contain a pointer to a sprite object, which is rife with directX stuff.

 

I'm also now quite sure how to phrase this in a google query so I thought I would ask you guys.

 

Thanks for reading

0

Share this post


Link to post
Share on other sites

I think I get it - instead of having the sprite class contain a bunch of DX references it would contain pointers to interface classes? The actual implementation would then depend on the API I choose to render with. That's actually pretty simple. Thanks!

1

Share this post


Link to post
Share on other sites

The key thing is to wrap it all around in a nice interface, going back to the vertex buffer you could have an interface that defines how to access it (create, map data, etc.) then for example you could have a GLVertexBuffer and an DXVertexBuffer class that derives from the interface. This way you hide the implementation and let your render system decide which one it wants to use.

2

Share this post


Link to post
Share on other sites

You should separate implementation from interface. DirectX and OpenGL are implementation so should be in a file named like GLVertexBuffer, DXVertexBuffer or simple as GLMesh, DXMesh, etc. That allows you to create an attachable library, you could add dx or opengl shared library at runtime. The only downside is that interfaces will produce vtables, but thats not a big deal.

A can give you an example of how i do it:

(Interface)
https://github.com/Ghrum/Ghrum/blob/master/include/Event/IEventManager.hpp

(Implementation)
https://github.com/Ghrum/Ghrum/blob/master/include/Event/EventManager.hpp
 

2

Share this post


Link to post
Share on other sites
As others have stated the way to do it is simply to abstract, think of the rendering like a big wall with a bunch of mail slots in it with labels over them. You know if you shove an object in a certain slot it will get handled appropriately, your code doesn't care who is behind the wall.

Then all you have to do is create the back room yourself, it can be as simple as going to where your engine creates a renderer object and change the type to one of multiple different ones. Thus you seperate the concrete implementation from the interface you use to work with it.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0