Overview
A micro-guide for SteamOS/Linux (with links to detailed guides inside) for those that know what they are doing and just want an overview to make sure they hit all the right boxes.
Overview (Linux)
[Nov. 7th 2020 Update] Unity Hub is now best experienced (on SteamOS current) using the AppImage found here: [link]
I will update the guide when I have time. Leave a comment below to encourage the update and I will get right on it.
Welcome to the SteamOS/Linux Quick Start Guide. (Other OS’s and guides are planned.)
Quick Note: These guides show you how to setup UnityHub and Unity Editor on your SteamOS Linux Machine. To actually contribute to our workshop, we have tools in the works to do so. Contact us in chat or forums and we will get you those. These guides will soon cover that, the process is still in Alpha so we are not documenting it yet.
This is literally all we are doing.
[link]
If you desire a highly detailed w/ pics step by step guide checkout:
[link](Below Guide can be found linked to from above guide, just putting here for completeness.)
[link]
The 2 guides above try to cover every detail about the CommunityUs Workshop Environment. Both for the new and advanced *nix operator that might want every detail.
Below is the fast past micro-guide for quick starting your dev env.
Exit Big Picture Mode
[link]Password and Steam Desktop Client
In Terminal: Setup a password, and launch Steam with Steam Console option so we can track the PID progress.
FlatPak Package
In new terminal:
Or view complete windows/user interface setup here:
SECTION: [Package UI] FlatPak
[link]
FlatHub and UnityHub
Launch CommunityUs and choose “Play UnityHub (Prereq. FlatPak & Workshop 101)”
It may or may not ask for password again, depending on what you did above. You are encouraged to read the detailed guides to see exactly what is going on in your system.
~10 min.
Watch the PIDs in Steam Console or since we launched Steam Desktop Client from command line, we can see more verbose log in Terminal…so we know it is working. This will take a while on first setup esp. on slow internet.
Steam Console vs. Terminal Log
Expect CommunityUs to say “Running” for about 8 min. before you see a UnityHub window. But you can follow the progress in the consoles.
After that, check behind the Steam Client, sometimes the window to accept UnityHub license shows up behind the Steam Client.
So long as the app shows “running” you are good (it means the background install is running.) If you get anxious that it hung, just watch Steam Console for new PIDs to appear, that means it is working.
For more details and picture based guide:
Guide Index:
[Part 2] Intall UnityHub
[link]
[coming soon] Our Workshop Tools Setup for Unity
not finished yet.