The past couple weeks have rather been absorbed by boring, but essential, housekeeping. Now that we’re moving into using Unity more prominently, as well as Unity assets, we’ve been taking care of the not overly simple task of getting all the devs up to the same basis.
We’re in the process of updating the codebase from v5.5.0 to 2017. And the tooling that’s available for 2017 is not the same, and doesn’t work as well, as 5.5.0, without having to modernise a lot of things. Whilst we can continue in 5.5.0, it would be better in the long term to update the engine and use the more modern, and more optimised, API. Especially in the use of assets, it’s rather essential everyone be on the same version so we’re not chasing extra bugs. And we all use Windows, Mac, and Linux, so it’s not been a simple affair.
MonoDevelop, the IDE Unity usually ships with, is undergoing some changes and is this year to be replaced with VisualStudio, which is nice. Until then Goldie’s rather on the back foot and having to fix her own tooling in order to assist with our dialogue assets.
The simple version is that in order to work deeper in Unity as a team, we need everyone updated and functioning. It’s not an easy affair and headaches are had by all. But it’s worth not having to build our own engine from scratch. It’s boring, but essential work, and we now have the right assets licensed for everyone and versions matched, there’s just some extra work needed to get everyone running again. For me it’s been rather fortunately timed, as I’ve had to spend some time recently looking after my old mum.
Here’s a new concept I’ve been working on, however. I wanted to make an elegant dress look armoured, basing it loosely on a DnD character of mine.
Until next time!