• 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
Ripiz

Trouble resolving dependency properly

4 posts in this topic

Hello,

firstly little background. I've seen a lot posts "Write games on engines" and I don't need this type of stuff here. I'm just trying to separate engine and game early on instead of having a lot of hardcoded things later on. This is where I encountered a problem. I'm trying to wrap DirectX into a bit more friendly classes, but they need DirectX Device and I can't think of a decent way of passing device to these objects. Roughly my code looks like this:

[CODE]
class VertexShader {
ID3D11VertexShader *shdr;

void Create(void *bytecode, uint32 size); // requires ID3D11Device or DXWrapper;
};

class DXWrapper {
ID3D11Device *dvc;
ID3D11DeviceContext *dvcc;
};

class Engine {
DXWrapper DXW;
};

// this is how I use VertexShader class:
class SkinnedRenderer {
VertexShader vrtShader;

SkinnedRenderer() {
auto bytecode = ResourceManager.Get("skinned_vs.cso");
vrtShader.Create(bytecode.data(), bytecode.size());
}
};
[/CODE]

I managed to think of 2 possible solutions (workarounds?) but I'm not satisfied with either of them.[list=1]
[*]Pass D3D Device as argument in VertexShader::Create() call, but I feel it's a bit messy doing it all the time.
[*]Make Engine or DXWrapper class's instance static/global, allowing global access, but I'm trying to avoid such dependency, as code re-useability decreases.
[/list]

Anyone have any ideas how can I resolve this issue, or solution #1 is the right way?

Thank you in advance. Edited by Ripiz
0

Share this post


Link to post
Share on other sites
I'm not a graphics programmer (yet), but aren't vertex buffers dependent on the device you create them from? If this is the case, then #1 makes sense assuming you mean DXWrapper& and not ID3D11Device*. However, if this isn't an option, why not pass an intermediate class, which hides the device being used to create the vertex buffers from the interface? Something like the following:

[code]
class VertexBufferContext {
public:
VertexBuffer create( ... );

private:
DXWrapper& context;
};
[/code]
1

Share this post


Link to post
Share on other sites
It's VertexShader, not VertexBuffer, but doesn't matter, wrappers look almost identical.
Yes, it does depend on device.

I would still have to initialize VertexBufferContext somewhere, most likely on the DXWrapper, such class method probably would be better on DXWrapper itself, rather than dummy class with single method. However, assignment operator displeases me:

[CODE]
class DXWrapper {
public:
VertexShader CreateVertexShader(...);
};

class SkinnedRenderer {
VertexShader vrtShader;

SkinnedRenderer(DXWrapper &DXW) {
auto bytecode = ResourceManager.Get("skinned_vs.cso");

// this assigment feels little bit fishy and a bit wrong
vrtShader = DXW.CreateVertexShader(bytecode.data(), bytecode.size());
}
};
[/CODE]

And before someone suggests using pointer: this class also has purpose of destroying resources on it's own destruction, solves issue of missing Release() calls and some redundant typing.
0

Share this post


Link to post
Share on other sites
I recently came across this design problem myself and found that creating a factory responsible for the creation of game assets (shaders, textures, etc.) was a good way to go. The factory ends up maintaining the ID3D11Device creation/destruction, and you can add methods for whatever resources you need with whatever arguments you need. It's no different than the original interface for ID3D11Device really, but it ends up doing away with some creation options you don't think you'll need.

[CODE]
class ResourceManager {
public:
Mesh* createMesh(const char* file);
Texture* createTexture(const char* file);
VShader* createVertexShader(const char* file);
PShader* createPixelShader(const char* file);
private:
ID3D11Device* m_device;
ID3D11DeviceContext* m_context;
};
[/CODE]
2

Share this post


Link to post
Share on other sites
Thank you both for reply. It seems some kind of factory might be the a good choice in this case.
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