Category: Main Games Game Tools BYOND 512.XXXX Stable


No Screenshot

Submit Screenshot

BYOND Suite version 512.xxxx (aka 512.xxxx) stable branch.

Application Details:

Version: 512.XXXX Stable
License: Free to use and share
Votes: 0
Latest Rating: Bronze
Latest Wine Version Tested: 5.14-staging

Maintainers: About Maintainership

Free Download A link to the 512 build repository

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

Everything tested: Login, launching a Space Station 13 game

What does not

Performance is abysmal: Launched Space Station 13 game ran consistently with ~0,25fps and according input lag. None of the different video and WINE configurations I tried changed anything:

  • CSMT vs no-CSMT (Toggled using the winecfg option in wine-staging – when CSMT was enabled the dreamseeker.exe process would additionally consume 100% CPU on one core, but this would not impact the frame rate in any way.)
  • Hardware vs Software rendering (Toggled using MESA's LIBGL_ALWAYS_SOFTWARE=1 environmental setting.)
  • 32- vs 64-bit WINEPREFIX
  • WINE stable vs devel vs staging


Used the equivalent of winetricks wsh57 mfc42 vcrun6 ie8 to prepare the environment. Tested both a clean 32-bit WINEPREFIX and my regular 64-bit WINEPREFIX (yes, I actually maned to install ie8 there…).

What was not tested

Any real gameplay as it was just not possible/bearable.

Hardware tested


  • GPU: AMD
  • Driver: open source

Additional Comments

Also tested with 5.14 devel (non-staging) and 5.0.1 stable versions of WINE. Rating is Bronze as it was technically working, just unusable in practice. The desktop environment used was KDE Plasma 5.19 with the KWin Wayland compositor – running under X11 way not tested.


Some notes on the previously suggested winetricks recipe:

  • The wsh56 and jscript winetricks verbs are deprecated aliases of wsh57 and are not required anymore.
  • Installing ie7 through winetricks does not work anymore, but one can directly install ie8 and BYOND will then launch successfully and show its webviews.
  • As mentioned, it is possible to also perform this recipe on a 64-bit WINEPREFIX – with identical results –, but then installing Internet Explorer 8 for Windows Server 2003 64-bit is a huge pain due to lack of winetricks support for this.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentDebian GNU/Linux Unstable "Sid" x86_64Aug 12 20205.14-stagingYes Yes YesBronzeAlexander Schlarb 
ShowArch Linux x86_64Feb 03 20205.0-stagingYes Yes YesGoldAssaf Y 
ShowUbuntu 18.04 "Bionic" i386 (+variants like Kubuntu)Jun 22 20194.0.1Yes Yes NoSilverAnton Pivovarov 
ShowManjaro Linux 18.0.0Mar 20 20194.2-stagingYes Yes YesSilverAlex Cooper 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Some more SS13 /tg/station workarounds & tips
by Andrew Smart on Sunday December 6th 2020, 23:47
The BYOND cache problem I mentioned might be along the lines of this:
Really awful. Besides re-downloading the same big files into cache over and over again, there is a separate BYOND problem. BYOND fills up the disk with duplicate byond.N.rsc (where N=1...100 or whatever) ~80MB files and creates a ton of empty tmpXXX folders when exiting the game session for some weird reason.

IIRC just use wine-staging 5.17.2~stretch, winetricks ie8 and directx (I don't recall which directx). Nothing along the lines of or lutris

On certain servers the FPS had been awful, I assume due to an unsupported shader on my hardware, or not having MaxVersionGL to 3 in the registry editor as mentioned by Amidaychi in the byond forum posts above.

There are other JavaScript problems I experience on Yogstation (a /tg/station derivative), at present the rapid pipe dispenser icons are missing, the camera consoles don't work, and there is also a not implemented error when attempting to apply a chromosome to a mutation in genetics.

When troubleshooting a JavaScript error, I suggest instead of having the .js file condensed as one line (tgui.bundle.js or whatever), you instead have it cached and run js-beautify on it to un-condense the JavaScript, so that error messages will now have a line number other than 1 and point you to where the problem code is. I'm not sure how to set up tgui for development, but this works well enough for me to get rid of the problems preventing the in-game interface from functioning good enough. The blue-screen NTOS error will have a ".js:#" suffix indicating the line number of the problem and look like this:

Within the BYOND directory (parent to the cache folder) I keep the local copies of the css/js files, and this script to copy the files in:
#!/usr/bin/env bash
f=`(find cache -name tmp* -print &) | head -n 1` #Find the first folder named like tmpXXX
echo "$f"
cp asset.1c341d4cf2c36f562f588bcd7df64c8f.js "$f"
cp asset.1d1a338a8de45d23c32cb4658bf2cbc4.js "$f"
cp asset.72e420828cf5818574f4578703b8bc63.css "$f"
cp tgui-window-1.html "$f"
cp tgui-window-2.html "$f"
cp tgui-window-3.html "$f"

But I have to run it a few times after starting dreamseeker after I load a few interfaces, as it has to cache them first. If I see a messy interface (white or without css styling) then I re-run the script and re-click on the pop-up interface. After around 3 hours of playtime I get one of two errors:
*A white screen with black text like: "Please use a browser which supports JavaScript..." or,
*A tgui blue-screen NTOS error saying Mono.NET ran out of memory. There is memory leak somewhere, and Mono legit runs out of permissible memory. With .NET you can increase the memory limit via a setting, but due to the memory leak you'll always run out if you play long enough, and have to exit and re-join the session.

I could probably write a better script for handling the cache using folder/file watchers so I don't have to re-run the script manually so often. But, this is my present working workaround so I'm sharing it here. Looking at tgui they seem to have code and comments intentionally support IE8 thankfully so I think those developers may be happy to fix any of these JavaScript errors/lines which don't work on IE8 on WINE when brought to their attention.
I play on yogstation with some workarounds
by Andrew Smart on Tuesday December 1st 2020, 12:35
There is a bug with asset cache or something... a BYOND issue not wine. But here are my workarounds for the in-game popup HTML interfaces being completely white:
Line 13228 of tgui.bundle.js has an error, says not implemented, here is context:
return d.componentDidMount = function() {
var e = this.props.value,
t = this.inputRef.current;
t && (t.value = c(e)), this.props.autoFocus && setTimeout((function() {
return t.focus() #line 13228 not implemented.
}), 1)

So I changed this "return t.focus()" to "return t".

Next remove the "" from the following in tgui-window-1.html and tgui-window-2.html, so the local files with our edit are used:

Byond.loadJs('', true);
Byond.loadJs('', true);
Byond.loadCss('', true);

And retrieve those files and keep local copies in the /BYOND/cache/tmp1092/ folder (tmp1092 folder name changes every session). There used to be a tgui.bundle.js in the BYOND/cache but I reason they changed that to asset.1d1a338a8de45d23c32cb4658bf2cbc4.js, so I replaced that that t.focus() in that file.

And there is another bug where BYOND keeps downloading the same ~113.2MB file with a random name like "6768F769" which is then merged into http_cache.rsc. It tries to downoad this every game session, which will result in a many GB cache... to stop that lag-inducing and space hogging annoyance:
sudo tcpkill host
sudo tcpkill host
sudo tcpkill host
Those commands kill any connection from (IIRC) (for asset downloads), so only do this after the assets were downloaded completely once.

And the last issue I've noticed is that over time as they change things, the IE cache must be cleared out. The symptom of this problem is also the in-game popup HTML interfaces being completely white. This is a BYOND problem. I think I delete all folders in /drive_c/users/username/Local Settings/Temporary Internet Files/Content.IE5/

I have no FPS problems, everything works well as far as I can tell. On other servers they may have other HTML popup problems... like those "bluescreen" NTOS displays instead of a white screen. No idea what workarounds you might have to do on other servers, or if they might be similar.