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

Archived

This topic is now archived and is closed to further replies.

Aeetes

Display mode changing problem

2 posts in this topic

When you create the primary surface in full screen mode, the back surface is a member of primary. So, when you release primary surface, the back is release automatically. You release the back surface manually when you run in window mode.
Goodluck!

------------------

0

Share this post


Link to post
Share on other sites
Thank you. I got it working a little later by just releasing the back buffer before the primary surface. Thanks, since I didn't really know that the reference was held by the primary surface (I'm new to COM programming, switching from good old DPMI under DJGPP). At least now I know why it worked when I switched the release order, thanks.

------------------
Where's my Golden Fleece?

0

Share this post


Link to post
Share on other sites
I have written a GUI class library using DD and DI. So far it only runs in 640x480x8 mode. However, when I attempted to add support for mode changing (different resolutions, still 8-bit though) my programs crashes on exit (page fault). After this, any DDraw program that I run (including the samples) always crashes on loading with a page fault. I can only run a DDraw program again after rebooting.

My library has surfaces for primary and back buffer. When I change the mode I first release both the primary and back buffers, switch the mode, then finally create new primary and back buffer surfaces.

If I ignore the surfaces, and just switch the mode, not releasing and recreating the primary and back buffer, the program runs fine. I stripped the program down to the point where it does nothing but change the mode, so I am certain that the problem has to do with it... Namely the surfaces I believe.

Here is the code for changing the mode:

code:
ARESULT AccessDisplay::SetDisplayMode(int nWidth, int nHeight, int nBPP) {
if (m_pDDSPrimary != NULL) {
m_pDDSPrimary->Release();
m_pDDSPrimary = NULL;
}
if (m_pDDSBuffer != NULL) {
m_pDDSBuffer->Release();
m_pDDSBuffer = NULL;
}

if (m_pDD->SetDisplayMode(nWidth, nHeight, nBPP, 0, 0) != DD_OK)
return AERROR;

DDSURFACEDESC2 ddsd;
ZeroMemory(&ddsd, sizeof(ddsd));
ddsd.dwSize = sizeof(ddsd);
ddsd.dwFlags = DDSD_CAPS | DDSD_BACKBUFFERCOUNT;
ddsd.ddsCaps.dwCaps = DDSCAPS_PRIMARYSURFACE | DDSCAPS_FLIP | DDSCAPS_COMPLEX;
ddsd.dwBackBufferCount = 1;
if (m_pDD->CreateSurface(&ddsd, &m_pDDSPrimary, NULL) != DD_OK)
return AERROR;

DDSCAPS2 ddscaps;
ZeroMemory(&ddscaps, sizeof(ddscaps));
ddscaps.dwCaps = DDSCAPS_BACKBUFFER;
if (m_pDDSPrimary->GetAttachedSurface(&ddscaps, &m_pDDSBuffer) != DD_OK)
return AERROR;

DDBLTFX ddbltfx;
ZeroMemory(&ddbltfx, sizeof(ddbltfx));
ddbltfx.dwSize = sizeof(ddbltfx);
ddbltfx.dwFillColor = 0;
if (m_pDDSPrimary->Blt(NULL, NULL, NULL, DDBLT_COLORFILL | DDBLT_WAIT, &ddbltfx) != DD_OK)
return AERROR;
if (m_pDDSBuffer->Blt(NULL, NULL, NULL, DDBLT_COLORFILL | DDBLT_WAIT, &ddbltfx) != DD_OK)
return AERROR;

return AOK;
}


Does anyone have any ideas as to what could be causing this?

[This message has been edited by Aeetes (edited December 06, 1999).]

0

Share this post


Link to post
Share on other sites