• 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.
Sign in to follow this  
Followers 0
NetrickPL

When to check input in fixed step game loop

3 posts in this topic

Hey! I have a question about fixes step game loop. Is it better to check input (mouse, keyboard and packets) in fixed step loop or in render loop?

I mean #1:
while (true) //main loop
{
    while(fixed step loop) //ie 50/100 times a second
     {
       check input
       do logic
      }
      render
}

or rather #2:

while (true) //main loop
{
      check input
    while(fixed step loop) //ie 50/100 times a second
     {
       do logic
      }
      render
}

I think the approach #1 is better especially for lower framerates (you check input whenever you need for logic, and in case #2 @5fps you could press a key for a short moment and it could be processed 20 times by logic loop).

Could you advice me what's better? Because I'm not sure. Which one is used in games?

Thanks

0

Share this post


Link to post
Share on other sites

Yeah, it looks like version 1 is the better approach to get fast responses when pressing a key or something.

But usually, if the game runs with 5 fps, no one will like to play it anyway ^^

Don´t think to much over something that simple. If you run into problems with the time the game needs to react, you are still able to change your code...

1

Share this post


Link to post
Share on other sites
I handle my input like case #2 and I queue up the input commands. This allows the user to keep interacting, without losing any input.

Then in the logic step I apply, then render. The fixed step in my scenario is only for physics
0

Share this post


Link to post
Share on other sites
I think the approach #1 is better especially for lower framerates (you check input whenever you need for logic, and in case #2 @5fps you could press a key for a short moment and it could be processed 20 times by logic loop).

Could you advice me what's better? Because I'm not sure. Which one is used in games?

Thanks

In many cases you will actually be limited by your OS in which advanced key input handling is tied to Window management, and if you go multithreading the OS will tend you to move input handling to the Graphics rendering thread. It's not impossible to overcome, but gives a lot more work.

 

Doing it in logic should be best. But take in mind you have to split your thinking of input into logic and graphics. Depending on your game, there may be some input that must be handled deterministically, affecting logic; while there's some other input that is graphics related and non-deterministic (i.e. a GUI)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0