Issue with Monogame resizing

Question

I've converted my XNA project into a MonoGame one.

Whenever I start the application and resize the game manually (ie - dragging the window)...

this.Window.AllowUserResizing = true;

...the game scales in a weird manner.

Namely instead of scaling as it should do, it scales to the point where it looks fuzzy and the mouse clicks aren't working correctly.

The main game map has a hard coded "component size" which means that when the screen gets larger, its supposed to show more of the game - but instead I'm getting poorly scaled components.

Part of my code looks as follows:

const int TILEWIDTH = 50;
const int TILEHEIGHT = 50;
//......
Rectangle rec = new Rectangle(0, 0, TILEWIDTH, TILEHEIGHT);
spriteBatch.Draw(this.game.Content.Load<Texture2D>(tileGraphic.path), rec, Color.White);

So theoretically the pixels are becoming larger. This was working correctly in XNA.

I am in no way handling or overriding the resize command, it was 'just working'.

I found some threads with similar problems, but no solution. Anything I could do ?

Answer 1

I found that in order to get window resizing to work properly, you need to handle resetting the Graphics Device parameters manually, when the window is resized:

this.Window.AllowUserResizing = true;
this.Window.ClientSizeChanged += new EventHandler<EventArgs>(Window_ClientSizeChanged);

void Window_ClientSizeChanged(object sender, EventArgs e)
{
    graphics.PreferredBackBufferWidth = Window.ClientBounds.Width;
    graphics.PreferredBackBufferHeight = Window.ClientBounds.Height;
    graphics.ApplyChanges();
}

So basically, whenever your window is resized, you reset the Graphics Device with the new width/height.

Answer 2

The answer by jgallant here creates a stack overflow. To fix this I did the following:

//add this in your initialisation

this.Window.AllowUserResizing = true;
this.Window.ClientSizeChanged += new EventHandler<EventArgs>(Window_ClientSizeChanged);

---

private bool WindowSizeIsBeingChanged = false;
void Window_ClientSizeChanged(object sender, EventArgs e)
{
    WindowSizeIsBeingChanged = !WindowSizeIsBeingChanged
    if(WindowSizeIsBeingChanged){
        graphics.PreferredBackBufferWidth = Window.ClientBounds.Width;
        graphics.PreferredBackBufferHeight = Window.ClientBounds.Height;
        graphics.ApplyChanges();
    }
}

---

The problem was that graphics.ApplyChanges() calls the ClientSizeChanged to be activated. With this fix, you essentially skip the code from the second call, which makes sure you don't end up with a stack overflow, without having to put any additional calls to graphics.ApplyChanges() in your main game loop.

Answer 3

Fixing the issue was easier than expected

public override void Update(GameTime gameTime)
{
graphics.ApplyChanges();
}

It doesn't seem to impact framerate in any way (still getting 120)

Answer 4

I found that I needed to cache the resolution I had been on, and compare and if they changed, then do apply changes. This made it happen only once. Putting it in game update gave me lots of artifacts and crazy stuff.

void Window_ClientSizeChanged(object sender, EventArgs e)
{
    if (Resolution.currentResolution().X != Window.ClientBounds.Width || Resolution.currentResolution().Y != Window.ClientBounds.Height)
    {
         graphics.PreferredBackBufferWidth = screen.Bounds.Width;
         graphics.PreferredBackBufferHeight = screen.Bounds.Height;
         graphics.ApplyChanges();
    }
}