• 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
BackFlipp

PeekMessage(PM_NOREMOVE) + Fullscreen = fail?

3 posts in this topic

Heya all

I'm following the DirectX tutorial here: [[url="http://www.directxtutorial.com/Tutorial11/B-A/BA4.aspx#still"]1[/url]]

I've found some strange behavior with the main loop... The tutorial uses the following

[code]while(TRUE)
{
if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
{
TranslateMessage(&msg);
DispatchMessage(&msg);
if(msg.message == WM_QUIT)
break;
}
RenderFrame();
}
[/code]

When you hit alt-enter to switch to fullscreen mode, it works flawlessly. However, if you change the main loop to this:

[code]while(TRUE)
{
if(PeekMessage(&msg, NULL, 0, 0, PM_NOREMOVE))
{
GetMessage(&msg, NULL, 0, 0);
DispatchMessage(&msg);
if(msg.message == WM_QUIT)
break;
}
RenderFrame();
}
[/code]


When you hit alt-enter, it starts to go fullscreen, then "dings" an error and returns. It seems like it has to do with the PM_NOREMOVE flag, as the following shows the same broken behavior as the latter:


[code]while(TRUE)
{

if(PeekMessage(&msg, NULL, 0, 0, PM_NOREMOVE))
{

}
if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
{
DispatchMessage(&msg);
if(msg.message == WM_QUIT)
break;
}
RenderFrame();
}
[/code]

The DirectX debugging output doesn't give any errors or warnings. Interestingly, it has to do with the context switching itself, not the fullscreen... if you change the line:

[code]swapChainDesc.Windowed = false;[/code]

It starts fine in fullscreen, but fails to switch out of fullscreen on alt-enter. Any reason why PM_NOREMOVE would break fullscreen switching?


[1] [url="http://www.directxtutorial.com/Tutorial11/B-A/BA4.aspx#still"]http://www.directxtu.../BA4.aspx#still[/url]
0

Share this post


Link to post
Share on other sites
If you use NOREMOVE then you'll never remove messages from the queue, and more and more messages will just continue to pile up. This is going to cause bad things to happen.

Either way that message loop is jacked up. You want to loop on PeekMessage until no messages are left, THEN render a frame. Otherwise you will only remove one message per frame, and messages could end up piling up and then getting dealt with slowly.
0

Share this post


Link to post
Share on other sites
Sure, NOREMOVEchecks if there's a message on the queue and returns true if there is. Then, you use GetMessage to pull it off the queue and process it. You're right that looping on it until all messages have been processed is the better way to do it (even better: render in a separate thread, so you don't slow your render loop if processing tons of input/messages).

That said, it doesn't give any insight as to why the behavior is different. In both the first and second cases, the message queue is processed successfully; messages are caught, translated, and passed. Starting fullscreen or windowed works in both, but switching contexts via alt-enter doesn't work in the latter.
0

Share this post


Link to post
Share on other sites
Are you handling your device reset when switching modes from WM_ACTIVATE? This is not a good idea for a number of reasons, not least because you're going to fail to catch all of the circumstances in which a lost device may occur. Better to check the HRESULT from your Present call and use TestCooperativeLevel.
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