game input
July 03, 2002 10:22 PM
For a keyboard only input, what''s better?
Using GetAsyncKeyState or using DirectInput?
122
July 03, 2002 10:31 PM
This is the simplest and first question i have answered! 
DirectInput is like all other DX components have alot of initialization crap. However, it is much better to use and has MUCH MUCH more options than GetAsyncKeyState. Plus GetAsyncKeyState often loses input data.
DirectInput is like all other DX components have alot of initialization crap. However, it is much better to use and has MUCH MUCH more options than GetAsyncKeyState. Plus GetAsyncKeyState often loses input data.
I need money...Will you give me money?Please!I need money...Will you give me money?......
122
July 08, 2002 08:23 AM
But it''s much easier to set up GetAsyncKeyState() if you''re a newbie......
DirectInput is much more powerful and much faster though. I often use GetAsyncKeyState() while starting a game to save time and then fill in with DI later.
DirectInput is much more powerful and much faster though. I often use GetAsyncKeyState() while starting a game to save time and then fill in with DI later.
1,826
July 08, 2002 08:46 AM
Yeah, GetAsyncKeyState is fine for testing, but don''t use it in your finished game.
Richard "Superpig" Fine - saving pigs from untimely fates - Microsoft DirectX MVP 2006/2007/2008/2009
"Shaders are not meant to do everything. Of course you can try to use it for everything, but it's like playing football using cabbage." - MickeyMouse
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
