• 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.
  • entries
    316
  • comments
    485
  • views
    321029

User Notifications in Hieroglyph 3

Sign in to follow this  
Followers 0
Jason Z

512 views

The final big ToDo in my list of Hieroglyph updates that were accumulated while writing our book was to add a better error handling system. There were many occasions where a shader would not compile properly, which basically caused a crash or a null pointer exception. In most cases, data is logged to the debug log and it is easy to figure out what happened, but in general it wasn't the way that it should be done. So I decided to take a look around and decide what to update or modify to give a more graceful exit strategy.

[subheading]Communication Issues[/subheading]

In Hieroglyph 3, there is already a rudimentary event system that can be used to simplify communication between various disparate classes in the engine. For error handling, I wanted to stick with this same mechanism - partially because it was already there and partially because I'm not the most familiar with writing exception based code. In addition, all of the sample applications have already been setup to receive and handle events, so it was really a no brainer to stick with the existing system.

So I created two new event classes, EvtInfoMessage and EvtErrorMessage. The former will simply notify the user of something, while the latter will both inform and then request an end to the application. After a few quick tests, the system was up and running without much more than half an hour, and could gracefully an application without dumping all over itself.

[subheading]Notifications[/subheading]

After deciding how the system will indicate that something unexpected has happened, it was time to decide how best to communicate this to the user (i.e. the developer debugging his code). I really have three choices in this regard. Hieroglyph 3 has fairly robust support for multiple windows, so I could simply pop up a new window and give the message. This could be done with raw win32 (as I have done for my Lua console window) or with the built in text rendering system that has been discussed previously. The former is kind of clunky, although almost surely would always be functional. The later depends on the engine itself, which may or may not be functioning properly in an error situation.

This led me to choose the third option - to use the good old windows MessagBox function. It will more or less always be functional, but is significantly easier to use than a raw win32 window. This also lets me use different icons for an error or an info message, and automatically handles the addition of buttons to the window too (I'm not using the buttons for anything now, but I could in the future...). This results in the following style messages for when a shader fails to load instead of an exception:

ErrorMessage.png

With the general system now being operational, it is just a matter of going through the engine and adding the creation and launching of one of the new events in each error situation. This may seem like a small step forward, but it already has sped up the development of an application. As always, the code is available to check out at the Hieroglyph 3 codeplex repository.


0
Sign in to follow this  
Followers 0


0 Comments


There are no comments to display.

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