GMS2 Required SDKs

YoYo QA Dept
  • Updated
Follow

This article details the required versions of the various tools and SDKs that GameMaker Studio 2 requires. 

We do not recommend using third-party tools ahead of what is listed below - GMS2 won't know how to support them properly and you may give yourself build errors or even IDE instability.

Be aware also that for everything below we only offer support for physical machines running a single OS natively - we do not support any variant of virtual machines, including Parallels or Bootcamp on a Mac, "Hackintosh" PCs, or Windows emulators on a Linux distro, etc.

 

This FAQ assumes IDE v2.3.7.403 using Runtimes v2.3.7.474. If you're not on this version, we'd strongly recommend you update first and then follow this guide. We will only offer Helpdesk support if your issue is in this version or a newer beta release - for all older releases, you will almost always be asked to update and confirm your issue still exists before we will investigate your ticket. 

 

 

Using the Windows IDE

  • See general system specifications in the popup on the GMS2 info page.
  • For help with any file/folder permissions, network issues, or antivirus clients interfering with your usage of GMS2, please see this FAQ on the files/URLs GMS2 needs to be able to access.
  • Visual Studio is required when building Windows YYC, Windows x64, and anything to do with UWP or consoles - see the target's own section below for specifics.
  • Note VS2015/VS2017/VS2019 requires at least Win 7 with SP1 - it won't install on Windows 7 without at least SP1 (and nothing older than Windows 7 is supported at all)
  • If you are using Spine images in your game, then GMS2 2.3.7 and above requires your files to be exported with Spine runtime 4.0 specifically. Older versions of GMS2 require specifically 3.7. No other versions are officially supported (your images may work fine, but we cannot guarantee this).
  • Steamworks SDK 1.42 is required if you're doing Steam builds. No newer versions are officially supported (your builds and submissions will usually work fine, although we cannot guarantee this, but newer functionality in the SDK will definitely not be present in GMS2).
  • A separate physical Mac is still required for targeting macOS, iOS/iPadOS, and tvOS - see the target's own section below for specifics.
  • When targeting the other machine, we would highly recommend both machines are connected to your network using Ethernet, rather than WiFi, as this can result in issues when building large projects for YYC.

Apple released a change with Catalina 10.15.4 and newer which breaks some SSH connections from a PC to a Mac during the macOS/iOS/tvOS build processes if using 2.2.5 or older, so always use the 2.2.5 Mac IDE to do builds for those platforms if you need to stay on 2.2.5.

(We would of course suggest you just update to the current release.)

 

Using the Mac IDE

Please don't use macOS/iOS/tvOS/Xcode developer and beta builds as soon as they are released, as Apple's beta builds are often subject to large changes and an issue in one version may not be present in the next update - be aware we will only look at Apple's "GM Candidates" and fix issues present in their release builds.

  • See general system specifications in the popup on the GMS2 info page. (However, also note the requirements for Xcode further down this list, as using old versions of macOS may work with GMS2, but you would be blocked submitting games to the App Store.)
  • As of v2.3.7, GMS2 has native support for running on M1 architecture Macs, so no longer needs any Rosetta compatibility to be enabled in Big Sur/Monterey - if you did previously enable "Open using Rosetta" inside "Get Info" for the GMS2 executable, please uncheck this OS setting now as it will cause unwanted results.
  • For help with any file/folder permissions, network issues, or antivirus clients interfering with your usage of GMS2, please see this FAQ on the files/URLs GMS2 needs to be able to access.
  • Whenever possible, we would recommend you leave case-sensitivity off when setting up your macOS machine (which is the default when installing macOS), as whilst we removed this requirement from GMS2 itself as of v2.3.0, we cannot control what the external build tools SDKs require, so you may find some platforms will still fail to build projects.
  • Mono 6 is required to be installed on your Mac, otherwise you won't be able to build any projects - if for any reason this fails to be installed automatically by GMS2 you can download the installer from https://download.mono-project.com/a...-MDK-6.10.0.104.macos10.xamarin.universal.pkg
  • Xcode is required to be installed separately before you can build any "Apple platform"  packages - see the macOS and iOS/iPadOS/tvOS sections below for specifics.
  • In general, we would always recommend using the latest non-Beta Xcode release, as this is the version Apple want you to be using. If this is not supported on your Mac, then we will try to support you as long as we can, but Apple will eventually stop your machine from being able to build apps and there is nothing we can do about this.
  • An Apple Developer account is required before you can use Xcode, and you will need Xcode to build and codesign the application as per Apple's platform requirements - and this developer account will need to be the paid version if you want to give your app to anyone else (only dev testing on your own machine is free these days). If you are a school/business, you only need one Apple account - you don't need one per student/staff member!
  • If you are using Spine images in your game, then GMS2 2.3.7 and above requires your files to be exported with Spine runtime 4.0 specifically. Older versions of GMS2 require specifically 3.7. No other versions are officially supported (your images may work fine, but we cannot guarantee this).
  • Steamworks SDK 1.42 is required if you're doing Steam builds. No newer versions are officially supported (your builds and submissions will usually work fine, although we cannot guarantee this, but newer functionality in the SDK will definitely not be present in GMS2).
  • A separate physical Windows PC is still required for targeting Windows, UWP, and any consoles - see the target's own section below for specifics.
  • When targeting the other machine, we would highly recommend both machines are connected to your network using Ethernet, rather than WiFi, as this can result in issues when building large projects for YYC.

 

Using the Ubuntu IDE beta

Note that this IDE is not suitable for a production environment at this time. Please continue to use a Windows/Mac as your main development machine and give feedback on the Ubuntu IDE if you wish to try it.

  • This early beta IDE is specifically for Ubuntu 20.04 LTS versions and no other distro is offered any support - it may work if you can install the .deb, but we will not answer tickets about other distros or customised kernels, etc., as we are only interested in Ubuntu feedback.
  • You must have Mono 6 installed first (it does come with Ubuntu 20.04 LTS, so you should have it already). Beyond that, GMS2 will try to install any required components during the installer process, so ensure you are connected to the internet first.
  • A separate physical Windows PC is still required for targeting Windows, UWP, and any consoles - see the target's own section below for specifics.
  • A separate physical Mac is still required for targeting macOS, iOS/iPadOS, and tvOS - see the target's own section below for specifics.
  • When targeting the other machine, we would highly recommend both machines are connected to your network using Ethernet, rather than WiFi, as this can result in issues when building large projects for YYC.

 

GMS2's Supported Export Platforms

 

Windows  (setup guide)

  • For building VM packages you don't need anything extra to be installed, as GMS2 includes everything required.
  • For building YYC packages you will need Visual Studio installed on your PC also (Community Editions are fine) and configured as per the relevant section in the setup guide above.
  • Note that VS2019 is not supported in anything older than GMS2 2.3.1 and so for older GMS2 versions you will need VS2017

For simply playing GMS2 games: XP is not supported at all. Vista and Windows 7 players will need to ensure they have DirectX 11 installed, otherwise the game will not run. Certain functionality in the game, like security when doing HTTP requests or using any third-party extensions, may prevent the use of Vista/Win 7 (or might require your players to install the final Win 7 Service Pack) and we are unable to do anything about this.

Prior to GMS 2.3.1 all games are 32bit-only, but GMS2 2.3.1 and newer allows the individual developer to pick 32bit/64bit.

 

macOS  (setup guide)

For simply playing GMS2 games: OS X 10.9 or later is required for AppStore games and OS X 10.7 or later is required for non-AppStore games. All games are 64bit-only.

 

Ubuntu  (setup guide)

  • GMS2 2.3.0 or above: supports Ubuntu 20.04 LTS 64bit and Ubuntu 18.04 LTS 64bit.
  • In GMS2 2.3.1+, you also have the option of building ARMv7 packages by simply targeting an ARMv7 device when you do your build.
  • Ubuntu 18.04 LTS 64bit is the last version supported by 2.2.5 or older, so please update your GMS2.

For simply playing GMS2 games: Ubuntu 16 or later is required. Other distros can usually run the games GMS2 generates with no issues, but we only state support for Ubuntu, so if you have issues playing games on these other platforms you will need to investigate this yourself. All games are 64bit-only.

ARMv7 architecture support is available for games built with GMS2 2.3.1 or newer if the developer built the package using an ARMv7 device.

 

OperaGX

There are no additional tools required to build OperaGX projects, but be aware you must have the browser installed in order to test your games otherwise you will be shown a website asking you to install Opera GX.

Your games will only work in OperaGX, but you have the ability to publish them to our GX Community (for free) so that anyone else can play them.

Note that this is a high-performance target much closer in functionality to Windows/Mac/etc., than it is to the HTML5 target.

 

HTML5

There are no additional tools required to build HTML5 projects, and the module supports a wide range of current browsers: all Chromium-based browsers (such as Opera/OperaGX, Chrome, Edge, and Vivaldi), plus Safari and Firefox. Mobile variants of all of these are supported also.

Please note that old IE 11 is not fully supported because it does not support WebGL, and some older mobile device browsers may have the same issue. However, you can usually run games in these browsers if WebGL is disabled in Game Options within your project.

 

Android (including the old Amazon Fire target)  (setup guide)

We do not recommend immediately updating your Android Studio or Java setup whenever updates are offered - always check here first!

  • Only GMS2 2.3.7+ support Android Studio versions newer than 4.2.
  • GMS2 2.3.3-2.3.6 supports Android Studio 4.2.
  • If you are using 2.3.2 or older you need to stick with 4.1, otherwise you will have errors running keystore commands.
  • You can always download older versions of Android Studio from Google here.
  • Assuming you're using 2.3.7, we recommend Android API 30 / NDK 22 for all projects.
  • Build Tools version is blank for API 30+ because Google have changed this so you specify the Compile SDK value and the Android SDK works out the correct build tools you need. If you're compiling with API 30+, then any version you type here will be ignored by Google's tools.
  • Minimum SDK version is 16 for API 28+ and anything built for Android YYC. (Be aware Google Play requires you to use API 30 or above when submitting!)
  • Please note some third-party extensions may require you to raise the minimum SDK version to their requirements, as will enabling "Run Lint code analysis". If your project fails to build, review your whole compiler log for the exact versions you require.

For simply playing GMS2 games: GMS2 itself supports a wide range of Android OS versions, but Google Play does not (and Amazon requires fairly recent APIs also). You may find that you can build and test using old devices and old API versions, but you would not be able to publish these on some stores, and there is nothing we can do about this.

64/32bit device support depends on what the game developer chose when they built the version you're trying to play - however all recent versions of GMS2 only offer 64bit, to comply with Google Play's store requirements.

 

iOS/iPadOS/tvOS  (iOS/iPadOS setup guide) (tvOS setup guide)

Our docs and the GMS2 IDE do not refer to iPadOS as there currently is no fundamental change compared to regular iOS and GMS2 iOS packages work perfectly fine on iPadOS. We will obviously monitor this going forward and react if Apple make a breaking change, but for now just bear in mind if you have "iOS" you have "iPadOS" also.

  • iOS/tvOS 14+ requires Xcode 12.0 or newer to build all projects, which is supported in GMS2 2.3.1 or newer (you can "patch" a 2.3.0 runtime by following this guide but any older version of GMS2 needs to be updated now).
  • You will also need macOS Catalina or Big Sur in order to install Xcode 12.
  • Please note that whilst Xcode 11 will still build projects for iOS 13 and all the way down to targeting iOS 9 or older, Apple doesn't support anything older than iOS 10 and super-old devices often can't access the AppStore so there's no real commercial need to do work to support them, and in order to submit to the AppStore you need to support all the newer iOS versions... So please don't test using only old devices!

For simply playing GMS2 games: iOS 10.0 or above, tvOS 12.0 or above, iPadOS 13.0 or above. All games are 64bit-only.

 

UWP  (UWP on PC setup guide) (UWP on Xbox One setup guide)

Whilst GMS2's Indie Subscription and above include support for Windows 10 Mobile packages, Microsoft themselves don't support this platform as of December 2019 and there is no way to publish your games. Accordingly, we do not offer support for using Win 10 Mobile phones beyond what is written in our setup guide and we cannot say how long Visual Studio will continue allowing you to test on local devices.

  • 2.3.4 requires Visual Studio 2019 (Community Editions are fine to use).
  • 2.3.3 and older requires either Visual Studio 2015 or Visual Studio 2017 (Community Editions are fine to use).
  • In 2.3.3 and older, Windows 10 SDK 10.0.14393.0 is the SDK we require rather than the latest version, but note that newer versions may additionally be required by some functionality/extensions in your project.

For simply playing GMS2 games: Windows 10 or the current Xbox One firmware is required. All games are 64bit-only.

 

 

Consoles

Please note you will only have access to the following links if you have been approved for the specific platform. If you wish to unlock access to a console (and can prove you're a licensed console developer!), please follow our Help Article that will explain the Application Process for Console Access.

Related articles