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

[SlimDX] Handling Lost Devices [Solved]

8 posts in this topic

I'm having various problems handling lost devices in SlimDX (I only started with it yesterday, moving from XNA). My problems occur when I hit Ctrl-Alt-Delete in Vista, which causes the debug runtimes to spit out the following:
Direct3D9: (ERROR) :Lost due to display uniqueness change
D3D9 Helper: IDirect3DDevice9::Present failed: D3DERR_DEVICELOST
A first chance exception of type 'SlimDX.Direct3D9.Direct3D9Exception' occurred in SlimDX.dll
An unhandled exception of type 'SlimDX.Direct3D9.Direct3D9Exception' occurred in SlimDX.dll

Additional information: D3DERR_DEVICELOST: Device lost (-2005530520)
Which breaks on Present() in my drawScene() call. Relevant code snippets below, the observant among you may notice it's DirectX 9.0c: A Shader Apporach, translated into C#.
public virtual void run() 
        {
            long prevTimeStamp = timer.ElapsedMilliseconds;

            while (window.Created)
            {
                if (!isDeviceLost())
                {
                    long currentTimeStamp = 0;
                    currentTimeStamp = timer.ElapsedMilliseconds;
                    float dt = (currentTimeStamp - prevTimeStamp) / 1000.0f;

                    updateScene(dt);
                    drawScene();

                    prevTimeStamp = currentTimeStamp;                    
                }
                Application.DoEvents();
            }
        }






public bool isDeviceLost()
        {
            Result result = d3dDevice.TestCooperativeLevel();

            if (result == ResultCode.DeviceLost)
            {
                onLostDevice();
                return true;
            }
            else if (result == ResultCode.DriverInternalError)
            {
                MessageBox.Show("Internal Driver Error... Exiting");
                Application.Exit();
                return true;
            }
            else if (result == ResultCode.DeviceNotReset)
            {
                d3dDevice.Reset(presentParameters);
                onResetDevice();
                return false;
            }
            else
            {
                return false;
            }
        }






[Edited by - adt7 on August 9, 2009 5:12:15 PM]
0

Share this post


Link to post
Share on other sites
It seems like you've posted the answer to your own problem without realizing it:
Quote:
Direct3D9: (ERROR) :All user created stateblocks must be freed before ResetEx can succeed. ResetEx Fails.

If you have created any stateblocks and have not freed them before calling Reset, the call will fail.
0

Share this post


Link to post
Share on other sites
Yeah, I just noticed that, and fixed it.

However, I'm still having issues when Ctrl-Alt-Del'ing, and then the code breaking on Present() due to a lost device.

I've edited the above to reflect the problems I'm having now.
0

Share this post


Link to post
Share on other sites
Are you getting the same error? (Window doesn't have focus)

First, I'm not familiar with SlimDX in particular.

But:

How do you process WM_KILLFOCUS and WM_SETFOCUS?

Within your application itself, can you successfully switch between windowed and non-windowed mode?

When your app loses focus, you may have to switch to windowed mode and pause the process. When the app regains focus, switch back to full-screen and unpause.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Buckeye
Are you getting the same error? (Window doesn't have focus)

First, I'm not familiar with SlimDX in particular.

But:

How do you process WM_KILLFOCUS and WM_SETFOCUS?

Within your application itself, can you successfully switch between windowed and non-windowed mode?

When your app loses focus, you may have to switch to windowed mode and pause the process. When the app regains focus, switch back to full-screen and unpause.


I've fixed that one since my last post.

The problem was that Application.DoEvents(); wasn't being called when the device is lost due to it being within my if-block.

Still having problems with losing the device between checking if it's lost and present is called though.
0

Share this post


Link to post
Share on other sites
Generally speaking, the most effective approach is to use the Configuration class to disable exceptions from device lost and not-reset entirely, and check the return value of TestCooperativeLevel (see Direct3D9.ResultCode) instead of waiting for an exception.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Promit
Generally speaking, the most effective approach is to use the Configuration class to disable exceptions from device lost and not-reset entirely, and check the return value of TestCooperativeLevel (see Direct3D9.ResultCode) instead of waiting for an exception.


... well, I wasn't waiting for the exception, I was checking the result and then the exception was being throw afterwards.

Adding the following seems to have fixed it (as per your advice), although it seems... hackish.
Configuration.AddResultWatch(ResultCode.DeviceLost, ResultWatchFlags.AlwaysIgnore);

0

Share this post


Link to post
Share on other sites
Well, it'll cause the rest of your frame to silently fail, until you notice at the next TestCooperativeLevel call. This is generally not a problem and it's the approach most people take in C++, I think.
0

Share this post


Link to post
Share on other sites
Additional to these you must check does device.Present() throw any error.

.
.
.
device.EndScene();
try
{
device.Present();
}
catch (SlimDXException err)
{
devicelost = true;
}
.
.
.


At First in your isDeviceLost function check if devicelost is true. If it is then you must call Thread.Sleep for some time.

Hope this will help.
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