Hey guys, I might be asking something stupid but the similarities between OpenGL and Direct3D9 are being swamped by the differences. In my project I have a bunch of image resources (specifically 565 16-bit images) that are not square or power of 2 most of the time and I know that not all machines support using a non-square or not power of 2 texture, In OpenGL it's as simple as calling glDrawPixels()... but from my understanding of Direct3D9 thus far, it may not be as simple as that for me. I did find a few pages regarding D3DX and Sprites but I'm not that far into fully understanding DirectX, and I'm just trying to learn plain D3D9 on it's own for the time being, also I have little to no choice in either changing the resources to work better as textures nor am I able to link D3DX to my project (I'm using GNU GCC MinGW, it produces much smaller executables and they seem to run marginally faster than the MSVC++ 2008 executables, as well as the fact they don't seem so prone to crashing with the bad programming done back in the late 90s on the game engine I'm trying to ramp up) I'll give a few details as to why I'm in such a sticky situation with these restrictions, I've got the source-code (legit) to an old game, I've begun rewriting the D3D7 code into D3D9 and thus far there have been no Direct3D related crashes on any system this game has been tested on since the upgrade, I'm still a ways off completing this, but before I move onto managing the textures for the game geometry, I want to have the User Interface working (the default game code already prints out quite a bit of useful information to the screen and I need some of these image resources to work) Basically all I want to do is take the Image data (whether it be RGB's RGBA's or 565) and print it onto the screen directly in a fashion that does not temporarily stall the game as writing to the backbuffer does (Locking the back buffer causes a stall that is considerably noticeable even at 640x480 resolution, which is absolutely unacceptable.) Also note I'm on a 5 year old machine, and I want this game to work on new computers, but also old ones, so fixes that only work on new system are unacceptable. Also, this fits into the same subject, I want to be able to print a single pixel out on the screen, don't worry, I don't intend to draw any more than 100 or sow pixels manually, but if D3D7 could do it easily... why shouldn't D3D9 be able to? OpenGL has allowed me to do it as well. Thank you all in advance if you answer, your help is appreciated when given :)

How fast does that work? glDrawPixels() is fast enough that the framerate is visibly unaffected (it drops but the human eye will never notice unless the hardware you run the game on is really old)

The original D3D7 code Locked the backbuffer surface, dropped the image onto it, then Unlocked the surface, of course D3D is much different now than it was then... but I am trying as hard as I can to avoid putting in any unessecary libraries and if the method you've supplied with UpdateSurface won't visible affect an already good frame rate, then I'll use it.

So what do I do about users who have Graphics Hardware that do not allow non-square/power-of-2 textures? waste texture space by generating a power of 2 (and square if I must) texture and Blt the data to that? That's a waste tbh and I'm trying my best to support new and old machines (said so above)

glDrawPixels() does not visibly stall my hardware which is quite old, so I'm happy with saying it's not too slow (yes, in truth it is slow, but in the application it isn't really slow enough to matter since I'm not doing anything advanced)

It'll be too much of a hassle to use UpdateSurface, I'd have to completely rebuild how t he entire game works (and I will try out every option to me before I begin rewriting around 6000 lines of code out of 20,000+)

Looks like LPD3DXSPRITE might be something I'll have to use... now if only I could get the damn D3DX headers to work with MinGW in Code::Blocks >_>
Has this problem been solved before? MinGW dislikes the "SUB" at the end of the header IIRC, and MinGW only comes with outdated standard d3d7,8,9 headers, no D3DX...