• 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

Multipe views

0 posts in this topic


I have been setting up a multi monitor framework, that is, I am rendering to multiple outputs on multiple adapters, with one device per adapter and one swapchain per output.
Each output additionally has its own backbuffer and zBuffer.

I do not want clones of the scene, which is working fine so far.
Instead, I want the scene to span the entire area spanned by all monitors ( easy to get as DXGI_OUTPUT_DESC).

So naturally, my thought was to use and set a different viewport before each Draw call.
But what it does instead, is clipping my scene to the size of, what it seems, is my back buffer (On a screen of 1280x1024, if I set [CODE]viewport.TopLeftX = -640;[/CODE]
my scene gets clipped vertically in the middle, showing only the left half)

It seems to me now, I could be creating a larger back buffer, but for n outputs I would at least let a (n-1)th of the buffer go to waste, while I seriously doubt most devices could create buffers that large.

Am I right?

Second, I might have to vary the camera matrix or the projection matrix (or even both?) for each render call, but I am a bit clueless as to how this should be done.
Currently my cam matrix is generated using [i]D3DXMatrixLookAtLH [/i].
To vary for a different viewport, I would have to multiply a Translation onto it for sure. I think, the translation in screen coordinates would be the vector from the center of the first monitor to the center of a second.
But then? How do I get this 2d translation into my 3d view space?

Or should it be entirely different?
Thanks for your help.

Just a small edit:
I reconsidered the part with different views, and came to the conclusion, that my program could only benefit from this, if the user actually ordered the displays in a circle around them.

So after a bit more experimenting, I think my desired result could be achieved using different projectionMatrices for each output.
I maybe could use [i]D3DXMatrixPerspectiveOffCenterLH [/i]to render for different monitors.
Then I would have to specify different view volumes. Here's where I'm lost at now:

I should once calculate the entire bounding box of all view volumes, maybe determine the barycentre of the view volumes, make this barycentre origin of an additional coordinate system, so that it can be the vanishing point for all windows, and then express all view volumes relative to this origin?? Edited by osiris11

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