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

Offset Origin in MonoGame 3.0 Control

3 posts in this topic

Hey folks, 

I've embedded a GLControl in to a WindowsFormsHost for a WPF application, as described by http://www.jfmajor.com/post/38447851593/monogame-in-wpf , but there's a strange dead area at the top of the control - like the origin has been offset slightly :

 

FYNvHVD.png

 

I've checked the margins and padding of both the controls I'm using, so it's not that (probably wouldn't be since the back buffer gets properly cleared), but I can't find anything obvious. 


I've noticed that the presentation parameters and display mode settings both have their resolution set to my screen's resolution, so I'm guessing they're not really used by the GL device. I also update the viewport of the device to the size of the GLControl whenever a resize event occurs. 

I'm rendering the lines using a scaled 1x1 texture, setting the origin of the sprite batch draw call to (0,0):

 

// aStartPoint = (0.0f, 0.0f)
// anEndPoint = (500.0f, 100.0f)

float angle     = (float)Math.Atan2( anEndPoint.Y - aStartPoint.Y, anEndPoint.X - aStartPoint.X );
float length    = ( anEndPoint - aStartPoint ).Length();
aColour.A       = myOpacity;

aSpriteBatch.Draw( 
        myLineTexture,              // Texture
        aStartPoint,                // Start point of the line
        null,                       // Rectangle (not needed)
         aColour,                    // Colour of the line
         angle,                      // Angle between the start and end point
         Vector2.Zero,               // Origin
         new Vector2(length, 1),     // Scale
         SpriteEffects.None,         // No effects needed
         0);                         // Might want to modify this later, the layer is essential the z coordinate

 

This is the xaml I'm using to set up the window, when I create the GLControl I set it as the child of the WindowsFormsHost :

 

<Grid>
        <Grid.ColumnDefinitions>
            <ColumnDefinition Width="Auto" />
            <ColumnDefinition Width="*" />
        </Grid.ColumnDefinitions>
        <Grid.RowDefinitions>
            <RowDefinition Height="Auto"/>
            <RowDefinition Height="*"/>
        </Grid.RowDefinitions>
        <WindowsFormsHost x:Name="myEngineViewHost" Grid.Column="1" Grid.Row="1" Width="500" Height="500" Margin="0" Padding="0" />
        <TabControl Grid.Column="0" Grid.Row="1"  Height="Auto" Name="myTabControl" Width="Auto">
            <TabItem Header="Objects" Name="myObjectsTab">
                <Grid />
            </TabItem>
            <TabItem Header="Templates" Name="myTemplatesTab">
                <Grid />
            </TabItem>
            <TabItem Header="Layers" Name="myLayersTab">
                <Grid />
            </TabItem>
        </TabControl>
        <Menu Grid.Column="0" Grid.ColumnSpan="2" Grid.Row="0" Height="20" Name="myMainMenu" Width="Auto" >
            <MenuItem Header="_File">
                <MenuItem Header="New" />
                <MenuItem Header="Open" />
                <Separator />
                <MenuItem Header="Exit" Click="MenuItemClicked" />
            </MenuItem>
            <MenuItem Header="_Edit" />
            <MenuItem Header="_View" >
                <MenuItem Header="Grid" IsCheckable="True" IsChecked="True"/>
                <MenuItem Header="Snap To Grid" IsCheckable="True" IsChecked="True" />
            </MenuItem>
        </Menu>
    </Grid>
</Window>

 

Anyone spot what I'm messing up here? The width and height of the WindowsFormsHost are static (500) just while I'm trying to figure out what's going on.

 

I'm guessing it's to do with the way I'm setting the viewport. 


When a resize event triggers, I pass with width and height of the control to a function that creates a new viewport at (0,0,width,height). 

I can offset the y coordinate of the viewport to make it look like the control is rendering at the correct point, but I'm not sure where that offset is coming from. Given the code above, if I subtract 20.0f from the viewport's Y coordinate it renders correctly.

 

Cheers!

0

Share this post


Link to post
Share on other sites

How far down is this occuring? Could it be related to this line:

 

<Menu Grid.Column="0" Grid.ColumnSpan="2" Grid.Row="0" Height="20" Name="myMainMenu" Width="Auto" >

 

where you set a height of 20?

1

Share this post


Link to post
Share on other sites

How far down is this occuring? Could it be related to this line:

 

<Menu Grid.Column="0" Grid.ColumnSpan="2" Grid.Row="0" Height="20" Name="myMainMenu" Width="Auto" >

 

where you set a height of 20?

 

Getting rid of the menu and extra row was on of the first things I tried, but it didn't make any difference. Resizing the control increases the gap as well.

 

I got in touch with one of the MonoGame devs, and he pointed out a line in their implementation of the XNA GrahpcisDevice :

 

GL.Viewport(value.X, PresentationParameters.BackBufferHeight - value.Y - value.Height, value.Width, value.Height);

 

So the viewport actually gets offset by the back buffer - and there isn't any way to modify the back buffer properties in the WindowsGL implementation of MonoGame. 

 

I picked up the source code and built my own lib with that offset removed, hasn't caused any problems yet but I guess it's early days :)

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