pls help me with few directx doubts... Am a beginner

please bear me with spellings ... I am lazy in typing

please bear me with spellings ... I am lazy in typing

Don't take my word from it, but i've heard that Directx 10 is kinda, well... not used much. Directx 9 or 11 are the most used ones. Why you choose Directx 10?

Don't take my word from it, but i've heard that Directx 10 is kinda, well... not used much. Directx 9 or 11 are the most used ones. Why you choose Directx 10?
[/quote]

I believe that DX9 is supported still simply because older cards still cling to it but aren't up to DX10, DX10 is for newer cards on XP, DX11 ships with Win7 only.

DX10's advantage over DX9 is more shader flexibility. And a little performance. But that's about it. I really cannot claim to know more on the subject difference between the two.

I believe that DX9 is supported still simply because older cards still cling to it but aren't up to DX10, DX10 is for newer cards on XP, DX11 ships with Win7 only.

Morley, DirectX 10 doesn't work with XP. It was one of the big reasons PC gamers jumped on Vista: the first Windows OS to actually support DX10 code. Anything on XP has to resort to DX9.0c features.

DirectX 11 is able to down-level to DX10 feature levels, and runs on Vista, which is why 11 is more prevalent than 10: if you're targeting DX10, you can use DX11, because you've already excluded XP users.

Rockvignesh25: have you defined your viewport? That helps the rendering pipeline determine where matrix-transformed pixels actually appear relative to the display buffer's borders.

[quote name='Morley' timestamp='1355936141' post='5012488']
I believe that DX9 is supported still simply because older cards still cling to it but aren't up to DX10, DX10 is for newer cards on XP, DX11 ships with Win7 only.

Morley, DirectX 10 doesn't work with XP. It was one of the big reasons PC gamers jumped on Vista: the first Windows OS to actually support DX10 code. Anything on XP has to resort to DX9.0c features.

DirectX 11 is able to down-level to DX10 feature levels, and runs on Vista, which is why 11 is more prevalent than 10: if you're targeting DX10, you can use DX11, because you've already excluded XP users.

Rockvignesh25: have you defined your viewport? That helps the rendering pipeline determine where matrix-transformed pixels actually appear relative to the display buffer's borders.
[/quote]

vp.topleftx = 0
vp.toplefty = 0
vp.width = 1600 // my screen resolution
vp.height = 900
vp.mindepth = O.O
vp.maxdepth = 1.0

pls anybody teach me abt placing this so called 'virtual camera' and also about its projection matrix in detail

i choose direct x 10 because i have bought the book for it .... I have also found that 11 and 10 are almost same (from program code point of view) and i thought it would be easy for me to get used with it.

the "virtual camera" is just the easiest way to think about, and group, properties related to calculating your view and projection matrices.
At its core, the common "camera" class has a world-space position, relative to a world-space origin. This position is used to create the "lookat" matrix, or your view matrix, which has the effect of rotating and translating vertex data (defined in world space) so that it is rendered relative to where you've placed the virtual camera, giving the effect of viewing the scene from the camera's location.

The perspective projection matrix creates the depth effect of 3d by making further objects appear smaller and creating the parallax scrolling effect of distant objects moving across your view slower than near objects. It is also responsible for translating data in view-space to screen-space. It uses field-of-view (FOV) angle, aspect ratio of the screen (or render window), and near- and far-plane distance values to calculate a 3d frustum volume representing everything the camera can see in view-space.

The key to their interaction is multiplication order. The standard path is to multiply scene objects (specifically their vertices) by their world matrix (not necessary in your case, you've explicitly placed the triangle, but something you could use to move said triangle around if you wanted), then by the view matrix (orients the scene to where your camera is looking) and finally by the perspective matrix (to convert to screen-space). My first guess is you've got the multiplication order backwards. (This is much easier to detect when you have controls in place to move the camera around.)

Don't take my word from it, but i've heard that Directx 10 is kinda, well... not used much. Directx 9 or 11 are the most used ones. Why you choose Directx 10?

I believe that DX9 is supported still simply because older cards still cling to it but aren't up to DX10, DX10 is for newer cards on XP, DX11 ships with Win7 only.

DX10's advantage over DX9 is more shader flexibility. And a little performance. But that's about it. I really cannot claim to know more on the subject difference between the two.
[/quote]
DX9 is still supported because the PS3 and X360 only support DX9+ level features(PS3 doesn't support D3D at all btw), it has nothing to do with older cards. DX 10 and 11 ship from Vista not what you said and since DX11 support feature levels there is no reason other then the consoles to support a DX9 path. We dropped PC DX9 support with DiRT: Showdown, but where thinking of doing this on DiRT 3 already.

pls anybody teach me abt placing this so called 'virtual camera' and also about its projection matrix in detail

i choose direct x 10 because i have bought the book for it .... I have also found that 11 and 10 are almost same (from program code point of view) and i thought it would be easy for me to get used with it.

Then start coding for 11, nowadays learning DX10 has no uses what so ever, jobs ask for DX11 or OpenGL 4 now. Also DX 11 fixed a few things that DX 10 got wrong.