D3DXVECTOR3

Recommended Posts

I would like the code I'm writing--the interfaces at least--to be API independent. I can't do this if I'm throwing D3DXVECTOR3 all over the place. I've looked at the D3DXVECTOR3 interface, and I feel like it wouldn't be that hard to implement my own vector class. Is this a terrible idea? One concern a friend of mine brought up when I bounced this idea of of him is that there may be hardware optimization for vector processing that a class like D3DXVECTOR3 exploits? If this is true, then my software implementation would crawl comparatively. What are people's thoughts on this?

Share on other sites
I haven't tried it, but I believe that you can use the D3DX math library without using DirectX.

Share on other sites
Latest versions of D3DX have math removed from the headers. Even the simpliest matrix multiplication forces you to use libraries/dlls, as operations are not implemented in dx headers (at least I don't see them as I look through just now).

So you would have to incorporate "d3dx9(d).lib" into your project, and that immediately forces the end user to have "d3dx9_2(5/6/7).dll", which is a pain in the butt.

As for implementing your own math classes, I think it's a good idea, as not understanding the math ideas is usually the main cause of errors/problems in people's graphic code. Another thing, is that I personally don't like D3DX way of doing everything with functions, and prefer the operator overloading, which leads to code that is easier to read.

Share on other sites
So, there shouldn't be any inherent problems if I implementing my own vector classes? I think that's what I'll do then.

Share on other sites
Quote:
 Original post by john_tSo, there shouldn't be any inherent problems if I implementing my own vector classes? I think that's what I'll do then.

Nope. At most, your performance won't be as good, since D3DX is optimized by each CPU vendor. You can always look at the D3DX stuff as a reference, and fix some of its annoyances, like deffer pointed out.

Also, the same goes for matrices and if you need them, quaternions.

Share on other sites
Quote:
 I would like the code I'm writing--the interfaces at least--to be API independent. I can't do this if I'm throwing D3DXVECTOR3 all over the place.

You can always wrap it:
#ifdef USE_D3DX_MATHtypedef D3DXVECTOR3 vector3_t;typedef D3DXQUATERNAION quaternion_t;// Rest of types// ...inline float vector3_length(const vector3_t& vec){    return D3DXVec3Length(&vec);}// Rest of functions// ...#elseclass vector3_t{// Define your vector with the same interface};#endif

Also, I'd use a vendor-supplied math library if I didn't use D3DX - i.e. Intel's or AMD's math library.

Create an account

Register a new account

• Forum Statistics

• Total Topics
628320
• Total Posts
2982057

• 12
• 9
• 9
• 13
• 11