• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.

Archived

This topic is now archived and is closed to further replies.

Zenroth

Game Input Timing

3 posts in this topic

I haven't used GetDeviceState- but I'm guessing it gets the current up/down status of all the keys right?
Also, I'm confused about why adding a delay makes a difference. Maybe it has something to do with key repeat? The second key pressed will repeatedly be set as pressed while the first is only pressed once?

Anyway here's an alternative way, a bit uglier, but it works for me-

bool GetKeyEvent(unsigned char &Scancode, bool &Pressed)
{
DIDEVICEOBJECTDATA TheEvent;
unsigned long ArrayLen= 1;
HRESULT Result;

Result= Keyboard->GetDeviceData(sizeof(DIDEVICEOBJECTDATA), &TheEvent, &ArrayLen, 0);
if (!SUCCEEDED(Result))
{
return false; // no keys pressed
}

if (ArrayLen == 1)
{
Scancode= (unsigned char) TheEvent.dwOfs;
if (TheEvent.dwData & 0x80)
Pressed= true;
else
Pressed= false;
return true;
}
else
return false;
}


Call this in your main loop:

while (GetKeyEvent(Scancode, Pressed))
register this key as pressed/released

You'll need an array of the keys you want to use in your program, and mark them as down/up in the above loop.

Then after the loop you can check your keyarray for the pressed keys.

This also fixes a problem you might run into later, if you have a shoot key for instance- it's possible to press and release the key inbetween calls to GetDeviceState, in which case the keypress would not be caught.

hope this is somewhat useful

0

Share this post


Link to post
Share on other sites
Well how im doing keyboard input is im using immediate data and not buffered input. I dont check the entire keyboard. I just check to see if that one key is down.

I guess i might need to look into buffered directinput,but dont i have to worry about overflows and things then?

0

Share this post


Link to post
Share on other sites
Ok i have recently run into a bit of a problem ive tried a few things to fix the problem,and they didnt work well. So here i am.

Ok i am using directinput for checking keys in my logic loop. Basicly

Keyboard->GetDeviceState( sizeof(diks), &diks );

int KEY(int key){
return diks[key] & 0x80;}

if (KEY(DIK_ESCAPE)) PostMessage(hwnd, WM_DESTROY,0,0);

Ok this works great so far. Now i come to my problem

if (KEY(DIK_UP) && KEY(DIK_LEFT))player1.y-=1, player1.x-=1, player1.dir = DIR_NORTH_WEST;

Ill tell you a bit more bout what im trying to do so that the above might make a little bit more sence. Im using 8-way graphics and i have bitmaps for each direction. The problem is i can never get the diagonal to work. I mean they work if i hold them down but i can't ever get the direction to stay as a diagonal. I guess it sees that one of the direction keys was down for a millisecond longer than the other so it goes up or left ect. So what i need i think is some type of a delay. Sleep(1) works perfectly but kills my framerate very badly.

Any Thoughts on how to get this working?

0

Share this post


Link to post
Share on other sites
Yes you'll have to deal with overflow, but it's not hard. Use the SetProperty function when you're setting up the keyboard:

DIPROPDWORD Props;
Props.diph.dwSize= sizeof(Props);
Props.diph.dwHeaderSize= sizeof(DIPROPHEADER);
Props.diph.dwObj= 0;
Props.diph.dwHow= DIPH_DEVICE;
Props.dwData= 1024;
Keyboard->SetProperty(DIPROP_BUFFERSIZE, &Props.diph);

The dwData member is the buffersize, as long as you're checking the buffer every so often it should never overflow with a big enough buffer.
If it does overflow, directinput handles it- new data is lost, but it won't crash.

0

Share this post


Link to post
Share on other sites