directx

For the past month or so, I have been busting my behind trying to learn DirectX. So I've been mixing back back and forth between DirectX 9 and 10. One of the major changes I've seen in the two is how to process vectors in the graphics card. One of the drastic changes I notice is how you get the GPU to recognize your structs. In DirectX 9, you define the Flexible Vertex Formats. Your typical set up would be like this: #define CUSTOMFVF (D3DFVF_XYZRHW | D3DFVF_DIFFUSE) In DirectX 10, I believe the equivalent is the input vertex description: D3D10_INPUT_ELEMENT_DESC layout[] = { {"POSITION",0

I'm following tutorials and I've converted the usual initialisation to using ComPtrs up to this line: ID3D11Device* g_pd3dDevice = nullptr; ID3D11Device1* g_pd3dDevice1 = nullptr; // Obtain the Direct3D 11.1 versions if available hr = g_pd3dDevice->QueryInterface( __uuidof( ID3D11Device1 ), reinterpret_cast<void**>( &g_pd3dDevice1 ) ); Here's what I expected to be the straight analog: Microsoft::WRL::ComPtr<ID3D11Device> device = nullptr; Microsoft::WRL::ComPtr<ID3D11Device1> device1 = nullptr; // Obtain the Direct3D 11.1 versions if available hr = device->QueryInterface(__uuidof(ID3D11Device1

I want to use Vectors in a C# application I'm writing, sepcifically a Vector3. What's the best way for me to get a Vector type without writing my own? I used one in a POC that I found on CodeProject . It's not ideal, but it worked for our situation. At the time, however, it did not have a method to reflect a Vector3 about a given normal, but that may have changed since then. If you don't mind using DirectX (some stay away from it for whatever reason), then there is a Vector3 type in that library as well. Well, there's a struct called Microsoft.DirectX.Vector3 if that's what you're looking for.

In graphics software, sometimes we saw "field of view" for camera. Can someone explain what does it mean? The field of view (in the gluPerspective call) is the angle in degrees between a plane which passes through the camera position and the top of your screen and another plane which passes through the camera position and the bottom of your screen. Edit: Since you need not have a full-screen viewport: Any line which is projected to (x1, 0)-(x2, 0) lies in the first plane, any line that is projected to (x3, height)-(x4, height) lies in the second, where height is the height of your viewport in

I have a mesh model in X, Y, Z format. Lets say. Points *P; In first step, I want to normalize this mesh into (-1, -1, -1) to (1, 1, 1). Here normalize means to fit this mesh into a box of (-1, -1, -1) to (1, 1, 1). then after that I do some processing to normalized mesh, finally i want to revert the dimensions to similar with the original mesh. step-1: P = Original Mesh dimensions; step-2: nP = Normalize(P); // from (-1, -1, -1) to (1, 1, 1) step-3: cnP = do something with (nP), number of vertices has increased or decreased. step-4: Original Mesh dimensions = Revert(cnP); // dimension should

I'm using this gem from somewhere on this site. import ctypes import pynput SendInput = ctypes.windll.user32.SendInput W = 0x11 A = 0x1E S = 0x1F D = 0x20 # C struct redefinitions PUL = ctypes.POINTER(ctypes.c_ulong) class KeyBdInput(ctypes.Structure): _fields_ = [("wVk", ctypes.c_ushort), ("wScan", ctypes.c_ushort), ("dwFlags", ctypes.c_ulong), ("time", ctypes.c_ulong), ("dwExtraInfo", PUL)] class HardwareInput(ctypes.Structure): _fields_ = [("uMsg", ctypes.c_ulong), ("wParamL", ctypes.c_short), ("wParamH", ctypes.c_ushort)] class MouseInput(ctypes.Structure): _fields_ = [("dx", ctypes.c_long