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

D3DX8 and D3DX9 in one project

9 posts in this topic

Hi,

 

I want to use D3DX8 and D3DX9 (Sprite and Font class) in one project. Using D3D8 and D3D9 together is not a problem but the X variants have the same function and class name for DX8 and DX9. This causes problems while executing the (test) program.

//D3D8 part
LPDIRECT3DDEVICE8 device;
....
ID3DXSprite *sprite;
D3DXCreateSprite(device, &sprite);
sprite->Release();

//and D3D9 part in an other file
LPDIRECT3DDEVICE9 device;
....
ID3DXSprite *sprite;
D3DXCreateSprite(device, &sprite);
sprite->Release();

The D3D8 part will run fine but the D3D9 part crashes in the D3DXCreateSprite method. I checked the generated assemblercode and it turns out that both D3DXCreateSprite methods are the same so the code tries to initialize the D3DX9 Sprite with the D3DX8 Sprite code what can't work.

I hoped something like this could work but for sure it does not:

namespace D3D8
{
#include <d3dx8.h>
#pragma comment(lib, "d3d8.lib")
#pragma comment(lib, "d3dx8.lib")
}

D3D8::ID3DXSprite *sprite;
D3D8::D3DXCreateSprite(device, &sprite);
sprite->Release();

The compiler doesn't create seperate methods.

 

Anyone has an idea how I can include both DX versions in one project? One solution could be to dynamicly load the d3dx_....dll and use GetProcAddress for D3DXCreateSprite but I hope there is an "build in" solution.

 

Thanks for your help!

0

Share this post


Link to post
Share on other sites

Why do you need D3DX8? What are the functions in D3DX8 which aren't available in the D3DX9?

 

Cheers!

0

Share this post


Link to post
Share on other sites
it is an overlay for dx apps and should work with DX8 (yeah some older programs use it ;)) and DX9.
Internaly it checks which version the game uses and then uses my DX8 or DX9 renderer.
0

Share this post


Link to post
Share on other sites

Sorry to say this, but in VC++ you have no way to tell the compiler "that's the right dll". There are 2 solutions to your problem:

 

1. GetProcAddress all of D3DX8 needed functions dynamically.

2. Wrap those functions in separate library and static-link.

 

It's additional work, but probably the only solution.

0

Share this post


Link to post
Share on other sites

I tested your second idea 5 minutes before because I thought it would work but now the DX8 part is ignored and the DX9 D3DXCreateSprite gets called for both. Maybe I have done something wrong with it. GetProcAddress with D3DX8 will not work (found it out yesterday) because there isn't a d3dx8_....dll. The provided file in the DX8 SDK is a static library.

 

I will attach the project and it would be very cool if you could check if I did something wrong.

0

Share this post


Link to post
Share on other sites

Create two DLLs that contain the DX functionality you need, one compiled against DX8, the other compiled against DX9. Then have your application dynamically load the appropriate DLL at runtime. Note that your are not dynamically loading DX, only the version of your DLL compiled against the desired DX version.

0

Share this post


Link to post
Share on other sites

yes, this would work but I don't want to split this part in different DLLs.

0

Share this post


Link to post
Share on other sites

Sorry, but that is the correct way to do it.

 

Why do you care that they are in different DLLs?

0

Share this post


Link to post
Share on other sites

I'm confused as to how an outright hack is preferable to a clean and simple solution, but if you're happy, then carry on.

1

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