![]() Therefore, It is vital that you test on a cleanly installed Linux machine to ensure that your game includes the required dependencies across all distribution platforms. Additionally, Valve’s Steam client includes its own set of libraries (known as Steam runtime), which provides the user with the required libraries for their games. ![]() To ensure everything is working correctly, we recommend testing your game on a freshly installed Ubuntu 16.04 or 18.04 system - this will confirm if your game runs without installing anything user-side and without having the non-standard libraries present on users’ systems. Please either specify the rpath with the location of these libraries, or ship a launch shell script that will point the binary to the location of these libraries (using the LD_LIBRARY_PATH variable). When transferring your build to us, please include the necessary libraries along with your game. Windows games install redistributables at the time of installation, while Linux game builds are expected to contain all of the needed libraries needed to run the game on a freshly installed Linux system (e.g. The user can work around this issue by manually installing the required dependencies user-side using system tools, but this practice is suboptimal and leads to a poor user experience. As a result, the shipped build is broken, because it doesn’t start at all. Sometimes, games on Linux are shipped without the libraries that the game uses and are required to start the game. In these instances, please let us know the additional libraries (including 32-bit compatibility libraries) that your game requires to run on Linux and we will inform our users. Some tools, like Game Maker or Wine, allow only 32-bit Linux build and some games use a very specific 32-bit code or middleware. Sometimes it is not possible to deliver a 64-bit build. If your game uses the Unity engine, you can use the “ 64-bit Linux” (or “ Universal Linux” if you require both 64- and 32-bit binaries) export in Unity Editor. The ideal solution is to build your game on a 64-bit Linux system (preferably Ubuntu 18.04). not being compatible with big drive partitions (see: Large File Support). The user can work around this issue by manually installing the compatibility libraries user-side using system tools, but this practice is suboptimal and leads to a poor user experience.įurthermore, providing a 64-bit system user with a 32-bit build inadvertently makes the users susceptible to bugs and issues that are 32-bit specific, e.g. This means that shipping only a 32-bit DRM-free build is shipping a broken build that doesn’t start at all. 64-bit systems are currently the vast majority (around 95%) of all Linux gaming desktop installations. In contrast to Windows and macOS/OSX, 32-bit software does not function by default on Linux 64-bit systems. 64- and 32-bit Architecture Support ¶ Problem ¶ Should you have any questions or require any assistance, don’t hesitate to contact us by submitting a ticket or sending an email to our Product team. This will not only prevent the occurrence of many of the issues highlighted in this article, but will also ensure that your game is truly distribution platform agnostic. The guide is written with the desired “click and run” user experience in mind - this means that no additional steps are required from the user to make the game work.īefore submitting a Linux build to us for release, we strongly recommend that you test your build using a freshly installed Ubuntu 16.04 or 18.04 system (the GOG supported distributions). Almost all of them are easy to fix once you learn about them. ![]() Some are specific to popular game engines, while others are related to common mistakes made by developers not familiar with the platform. The following guide covers the most common aspects of making a Linux version of your game. Lobby Management In Game: Examples of Implementation Lobby Management in Main Menu: Examples of Implementation Lobby Browsing: Examples of Implementation Lobby Creation: Examples of Implementation Stats and Achievements: Example of Implementation Importing Achievements Using the Steam VDF File User Authentication Based On Other ServicesĪuthorizing GOG GALAXY Users in Third-Party Services Preparing Depots for macOS Application Bundle Our Recommendations for macOS Game Structure
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |