And another surprise came out of a Mystery Star: The Swindle can also be run natively with a 4.6.3f1 Linux Unity runtime (I had to include Steamworks libraries in the runtime for it to work, though).

Thanks! I've added that to the table on GOL wiki :).

In other news, after short discussion on Discord, PCGamingWiki now list the Unity version as a property, see Property:Unity engine build. It only list the versions for games that had it contributed and some games that have changed the build since may not be up to date (it only keeps the version of the most recent test), so everyone can feel free to contribute to PCGW directly by posting the versions of the games tested by adding |build=2017.1.0p5 and |ref with the check date. See Verdun or any other Unity game that have it filled for an example if you want to contribute. Hopefully that will ease up finding that certain game for the files if one doesn't want to install Unity :). I've also updated the wiki with the up to date info about it.

P.S. That also reminded me how I found this thread ;)

P.P.S. I also forgot to remind that earlier, but since StarCrawlers was mentioned in this thread, it is worth noting that it has been updated back in October 27 to work on Linux , so it shoulesn't be needed to get working anymore I guess :)

EDIT: Had to correct links as GOG forums didn't wanted to format them properly…

I have updated the instruction of obtaining the Linux player files from official Unity page on the GOL wiki – you do not have to use Wine as you can download Linux installer directly without the Unity Download Assistant. I have onl tested it for 5.x and 2017.x versions, but feel free to test it with the other versions :). That should make darktjm happier, too :P.

https://www.gamingonlinux.com/wiki/Unity_Games_Working_On_Linux_(User_Ported)#Manually_extracting_files

Thanks for that! The last time I looked, it seemed as if they had stopped including Linux players/interpreters in their releases. Didn't know about those separate 'Linux Support for Editor' installers. :)

No problem :). It only seems to work with Unity 5+ releases though. For Unity 4 you still have to download the whole >1GB archive and extract it, but at least you don't need Wine for that as well.

In case of beta and some patches releases, there is another link link starting with https://beta.unity3d.com/download/ instead of http://download.unity3d.com/download_unity/ so you can try that if the first one does not work. Some releases are actually available in both servers, e.g.

- http://download.unity3d.com/download_unity/d597d0924185/TargetSupportInstaller/UnitySetup-Linux-Support-for-Editor-2017.1.2p4.exe
- https://beta.unity3d.com/download/d597d0924185/TargetSupportInstaller/UnitySetup-Linux-Support-for-Editor-2017.1.2p4.exe

I will update the wiki with more detailed guides tomorrow probably.

Also, I'm fiddling with Mac games a little, so may post a write up on porting Mac games based on the available sources (mainly the linked Russian guide) :). Since Unity 5 Windows uses its own shaders resulting in Pink, so using Mac as a base to port can actually help with the pink plague.

That would certainly be a huge leap forward. Unity 5 shaders is what I wanted to take a look next. IIRC, the translated Russian guide talks about de-compiling the shader files and re-compiling them natively. That sounds like a lot of work, so if we could find a shortcut via Mac versions, that'd be really great.

Nice, I’ve always been curious about how to handle Mac software on Linux ;)

I should do the write up on the wiki soon, but in the meantime this Russian blog post explains how to download and extract the files from itch.io game and how the folder structure differs there (you basically only need to cut and rename the data folder and default unity resources and you can delete the rest and add the files from the Unity install instead). The guide should be pretty clear when translted by Google Translate anyway.

I'd have to look how GOG packages Mac installers, but with Steam when you download depots with steam Console (download_depot <appid> <depotid>) or SteamCMD the files are already extracted so you don't have to worry about it :)

Hmmm.... really interesting. I tried a couple of Unity 5 macOS builds, but couldn't get them to work, I still got complaints about shaders in the Player.log files. After a quick look at that Russian blog post, it may be because I only used the contents of the innermost Data directory and I didn't care about the 'unity default resources' and 'UnityPlayerIcon.png' files. Will try it later tonight. :)


Most (if not all, I'm not sure) macOS installers come as .pkg files, which are in fact xar archives. After extracting its contents, the next step is to find a file called 'Scripts' in a subdirectory (cannot remember its exact name right now), which is actually a gzipped cpio archive. After renaming it to Scripts.gz, gunzipping it, and extracting the resulting cpio archive, you can finally get to the game content.

Maybe some old GOG macOS builds are still in .dmg format, but the blog post seems to cover how to extract them.

Aaaaand another big update to the procedure described on Wiki – I add the use-case for Mac games, quoting the part about extracting GOG installers from here.

At this point the guide is quite comprehensive already, but I still plan to add the use-cases for extracting Unity files from Mac installers (if for some reason someone already have and want to avoid download a it or that's the only one you can get hands on – think beta version). For Unity 5+ you can also extract the files from the experimental Linux editor (distributed in .deb files), so might cover that, as it might be handy for those using it (it was mentioned in the Russian blog). I also wonder if the beta versions aren't still available physically on Unity servers, just without the link – that's something to evaluate as well.

Other than that, there's "Testing" and "Cosmetics" I want to write-up, changes in plugins list to incorporate mac equivalents and add my findings (I'll probably make it into sortable table) and then the changes to the test table – it's hard to get feedback with no active contributors, but I recently thought about splitting the working results for a separate table and then what I mentioned in discussion, just list the test results based on the most recent with different columns for each table.

At this point, some proofreading and/or suggestions may be welcome, as the page kinda grew :).

I always gave credit where due, mostly based on the Seegras' content that is CC-BY-NA, but the GOL wiki itself is in public domain so the content can be copied freely without any restrictions.

We still do not have the response Yepoleb asked Unity for, but with the comprehensive instructions for extracting the game files and the proof of concept script from the Russian forums (which I haven't tested personally), hosting the files may as well be surplus, with the only trouble being the download size (especially for Unity 4 games). Combined with the simple renames for Mac files, it probably could as well be made into a fully automated procedure!

Also, with PCGamingWiki listing the build numbers for Unity now, guess it makes listing Unity versions simpler than the spreadsheet/table, including community submissions.

If you have an idea for a better place to list the tests (be it working or not), feel free to give idea! So far the GOGmix is definitely useful – I was thinking of making guides/curator for Steam as well.

With that in mind, the next thing I'd probably take as I said is to share it to see if anyone else is interesting in this and post the idea to Lutris as a runner on github, unless someone can hack a working script and/or Lutris code already, then I'll gladly test it ;).

P.S. The Russian forums also brought these two projects to light: https://github.com/taviso/loadlibrary , "a library that allows native Linux programs to load and call functions from a Windows DLL" suggesting it could be some use for loading the plugins that the .so versions can not be found and https://github.com/DerPopo/UABE , Unity Assets Bundle Extractor, sadly a Windows-only (no source available) project that was made originally for 7 Days to Die which allows extracting Unity files as a tool that possibly can help with extracting and recompiling the shaders.

So many thanks for the topic!

I have tried with Reservoir Dogs - Bloody Days 5.6.1p1, it doesn't seem to work :-/
Will investigate more tonight.

Pink Screen of Death™, I presume? It's the main problem right now with v5 runtimes and their shaders. Two possible solutions mentioned by Faalagorn could be:

1) Using the Unity files from a macOS release, rather than a Windows one (I still have to try it again following the instructions of that Russian blog post)

2) Using that Unity Assets Bundle Extractor to de-compile the offending shaders and somehow re-compile them again.

In fact, the game crashes at startup, and sadly, there wasn't a MacOS release for this one (at least on gog), and since the game was removed from digital shops because the dev studio went down...

It may be shaders indeen, since even with Wine, the game doesn't work good (well at least, with Wine it launches... the characters don't appear in game - a bit difficult to play since it's a tactical game ^_^).

And quoting what Seegras, suggested on his blog back then: Though I think that's exactly what UABE does.

There are some translations of shaders available, though don't ask me whether they can be used in our case, especially on compiled shaders: https://www.google.pl/search?hl=en&amp;q=hlsl+to+glsl (there's also Vulkan's/OpenGL 4.6's SPIR-V).

For now, the best bet is to use a Mac as a base or even trying with any other platform, such as web, consoles or even iOS/Android (though the game might be compiled for ARM only) if that's available.

@Huinehtar – you can check the Windows "Plugins" directory to see if anything is missing and also use -logfile which may give you a clue.

Anyway, I added that for now as well 2 other test in the table –if anyone missed this game when it came out over two years ago, the good news it's still free and works on Linux, although leaderboards are not working anymore due to old domain nott being available :P. I also added the info about the xb/xf/xp Linux versions and some beta based on the info available on forums. Will add more info about the Linux Editor later.

Regarding Reservoir Dogs Bloody Days, I got (I have a dual screen) it crashes at startup, no pink screen. Maybe I'm doing something wrong? :(
Or is it a error unrelated to shaders?