directx

I'm trying to simulate mouse events in a game. The games uses DirectInput so you can't use SendMessage to send mouse events/keyboard events to it, that's basically why I have to hook in to the game. Also I don't want to use SendInput/mouse_events, the game must run on the background and make mouse events. I already managed to make a DLL hook in the game but now the next problem is that I have to make the mouse events and keyboards (probably the main problem). Thanks in advance. Instead of hooking into the game you could use GlovePIE , which is a kernel-level input emulator. You can write down

I'm starting a hobby game project on Windows that will make heavy use of 3D graphics effects. It will most likely be written in C++. Should I use OpenGL or Direct3D for my graphics backend? Why? Or should I use a ready-made graphics engine such as OGRE 3D ? Which one? Some "how to get started" links would be useful. (On either technology, or both.) Edit - Yes I really meant Direct3D, not DirectX, thanks to graham.reeds for clarification Edit - Mihai Lazar pointed out that I could also use a graphics engine such OGRE 3D. Edited the question to reflect this alternative. Start with OpenGL because

During my OpenGL experience, I often forgot to set some states. So I think state machine may not be a good design today. But now it has to be compatible. And I also know that DirectX was also a state machine in the early days. I'd like to know why OpenGL as well as DirectX was originally designed as a state machine? It's not clear what people mean when they refer to "state machine", as they never explain what the opposite is. So I'll talk about it both generally and specifically in terms of OpenGL "state machine" vs. current D3D "not a state machine". Both OpenGL and Direct3D use global state.