<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Unity - Tag - vo.rs</title><link>https://vo.rs/tags/unity/</link><description>Unity - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 16 Feb 2019 17:45:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/unity/" rel="self" type="application/rss+xml"/><item><title>Unity3D on Arch Linux</title><link>https://vo.rs/story/unity3d-on-arch-linux/</link><description>&lt;p&gt;The first time I tried to install Unity on Arch Linux, the build failed at ninety per cent because &lt;code&gt;/tmp&lt;/code&gt; filled up. Not because the machine was short of disk — it had plenty — but because &lt;code&gt;/tmp&lt;/code&gt; was mounted as &lt;code&gt;tmpfs&lt;/code&gt;, which lives in RAM, and Unity&amp;rsquo;s installer is a multi-gigabyte download that wanted to unpack there. That single gotcha is the whole reason this post exists. Unity runs perfectly well on Arch, but the failure modes are unusual enough that the official instructions never quite cover the case you actually hit, and the AUR package changes shape every couple of years. Here is how it works today, why each step matters, and what to do when it breaks.&lt;/p&gt;</description><pubDate>Sat, 16 Feb 2019 17:45:00 +0000</pubDate></item></channel></rss>