• 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
3DModelerMan

Event system for updates vs callbacks

7 posts in this topic

What would be better? Would it be better to have onUpdate() callbacks that need to be registered to get? Or would it be better to have an event system that just sends out an update message each frame. I can see a few benefits of both. The onUpdate callback method would have better performance because the event system wouldn't be taking care of the update scheduling. But with the event system sending out update messages, it would end up resulting in less code and an easier to maintain system, and by parralelizing the event system you might be able to get better performance. What are some other tradeoffs? Edited by 3DModelerMan
0

Share this post


Link to post
Share on other sites
I would go for a combination. If you are making a game then your system will have many other things to do each frame, so messages like "update color of an angry monster" won't need to be sent so often. Although some messages probably need to be sent each frame (like "update position" message). Edited by Freya
1

Share this post


Link to post
Share on other sites
I'm just trying to decide if the update messages should be sent through the event system, or be called from the main loop.
0

Share this post


Link to post
Share on other sites
I use events for menus when its items are clicked, highlighted, etc. They make more sense for interface elements such as these.
1

Share this post


Link to post
Share on other sites
[quote name='3DModelerMan' timestamp='1346772012' post='4976446']
I'm just trying to decide if the update messages should be sent through the event system, or be called from the main loop.[/quote]
I don't see any real reason why it couldn't be both. A callback is conceptually the response to an event.

Make your event dispatch system flexible enough to support both regular pulses (i.e. onFrameRenderer), and rare events (i.e. onButtonClicked).
2

Share this post


Link to post
Share on other sites
Game entities and subsystems. I usually just have a system where the game logic has a list of all the entities and subsystems and just loops through and calls onUpdate. But I thought it might be better to have the event system just send out an update event, and then the game logic would only need to worry about updating the event manager. Am I over engineering this and should just have it call the root entity's update method as well?
0

Share this post


Link to post
Share on other sites
[quote name='3DModelerMan' timestamp='1346861445' post='4976871']
Game entities and subsystems. I usually just have a system where the game logic has a list of all the entities and subsystems and just loops through and calls onUpdate.[/quote]
Do all game entities need an onUpdate() method? Do all subsystems?

If the answer to either of those is ever 'no', then you are under-engineering this problem. Something (probably your EventManager) should have a list of objects that are registered for updates, and loop over those calling onUpdate().
1

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