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

Handling shaders without D3DX

3 posts in this topic

Hi, I have a graphic rendering engine in DirectX9. Since D3DX has been deprecated, I'm working on removing it from the engine.

 

I was previously using ID3DXEffects to handle shaders. Without effect, it looks like I have to handle vertex and pixel shaders separately. This is not a big deal since I'm not using vertex shaders much anyway (2D game).

 

My problem is that, looking at the D3D9 API, there doesn't seem to be a way to access the different variables I am using in my shader. There is the IDirect3DDevice9::SetPixelShaderConstant family of methods, but they identify the parameters by index instead of a string. I'm not sure how I'm supposed to get the table that maps a variable name with its index? Another problem is I'm not seeing a function to set a texture variable in my code. I assume it has to do with samplers, but there's still an index I'm not sure what to do with.

 

Should I just assume that D3D9 is old so it's okay to use a deprecated (old) library (D3DX) with it, and stop worrying about having D3DX? Quite frankly, it looks like D3D9 shaders were designed to be used with D3DX, and it's hard to find doc about how to not use it since DirectX9 is starting to get old.

0

Share this post


Link to post
Share on other sites

Yea, there's no reasong to leave D3DX completely, if you're working with D3D9.

But moving away from D3DXEffect (and D3DXFont, D3DXSprite) can be a good idea, even if you still use the D3DX library for other stuff (texture loading, shader compilation, mathematics...). You don't really have a  full control of what's going on with D3DXEffect and your own implementation can be more efficient.

As Hodgman said, you can use D3DXCompileShader/D3DXCompileShaderFromFile to compile a vertex or pixel shader and you'll get a constant table which will tell you which variables are assigned to particular registers. Then you can make your map from variable name to register type/index.

 

I'm personaly forcing some common parameters to specific register numbers, for example World transform is in c0-c3. This way I can easily set it from c++ and in HLSL it's simply defined as uniform extern float4x4 g_world : register(c0) (can be in an #include file).

This allows me to somehow emulate constant buffers from D3DX11, because when I have all camera parameters in adjacent registers, I can set them all using a single SetVertexShaderConstantF call. The same for material parameters etc.

 

All other parameters specific to a particular shader can be easily found using the constant table. But they must be in different (free) registers ;)

 

Btw, the D3DXEffect framework is very complex, it's not just about shaders. In fact it can be used purely with the fixed function pipeline to set render states.

I made a simple text file parser with my own syntax for technique definitions inside each effect (.fx file), so I can still use the ability to change render states per effect/technique. (These commands are in /* */ so the file can still be used by D3DXCompileShaderFromFileA without errors.)

Edited by Tom KQT
2

Share this post


Link to post
Share on other sites

Thanks a metric ton of the input, that was very enlightening. :)

 

I will most definitely take out the D3DX effects of my engine and handle the shaders manually.

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