How to apply the Windows software renderer if your GPU does not support GMS2

If you get crashes very shortly after opening GMS2 or GMS2 won't start at all, then it's worth checking if this is because your GPU doesn't support the hardware acceleration GMS2 uses.

This is often required in some remote desktop or VM setups also - again, depending on the hardware involved and the settings of the remote/VM software.

It's worth noting that if you have just updated your GPU drivers but not yet rebooted you may also be in this state, so do reboot your PC first to rule out any temporary driver issues.


Confirming the Issue

If you open GMS2's log file you'll see a crash message like the following is the last thing written:

[10:43:42:931(8fae)] --------------------------------------------------------------------------------
[10:43:42:931(8fae)] Main Exception Handler: System.AccessViolationException
[10:43:42:931(8fae)] Exception message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[10:43:42:936(8fae)] Exception stack: at OpenTK.Graphics.OpenGL.GL.DeleteFramebuffer(UInt32 framebuffers)
at YoYoStudio.Graphics.Texture.DestroyRenderTarget()
at YoYoStudio.Graphics.Texture.Destroy()
at YoYoStudio.Graphics.TextureManager.DestroyReleasedTextures()
at YoYoStudio.IDE.Run()
at YoYoStudio.IDE.Execute(String[] _args, Int32 _initialWidth, Int32 _initialHeight)
at YoYoStudio.Program.Main(String[] _main_args)
[10:43:42:936(8fae)] --------------------------------------------------------------------------------


Installing the "mesa" Driver

Open Explorer/My Computer and navigate to your GMS2 install folder (yours will likely differ from mine shown below - the default is C:\Program Files\GameMakerStudio2\). Then go into the "mesa" subfolder.


You'll see a file in here. Copy/drag this opengl32.dll file up one level so it goes into your main GMS2 install folder.


Then try running the IDE again, and all should be working now.

Please note that as this is a software renderer it will use your CPU and so your CPU usage figure in Task Manager might well be higher than you'd expect.


If this still doesn't fix, please open a new Helpdesk ticket and include the ui.log file mentioned above, plus a DXDiag report. (Windows key + R, type "dxdiag", OK. Wait for the progress bar to finish, then click Save All Information. Attach the text file you've just saved to the Helpdesk ticket, rather than pasting in its contents, please.


Have more questions? Submit a request


Article is closed for comments.