Daggerfall Workshop Forums

Sure! just wanted to check if you already had it in the roadmap, but i agree there is no need to think about it before upgrading

Good work as alway interkarma!

Can I begin upgrading my mod projects to 2018.1.4f1 now or should I wait?

Whenever you're ready. Baseline for git version will be 2018.1.2f1. It's not tested with anything later, but should work OK.

I'm about to cutover in the next hour or two. Prior to this, I've created a unity55-stable branch to contain the final copy of Unity 5.5 code version for a little while. This will be marked on Live Builds page as Legacy Stable 0.5.

It will probably be a week or two before I release first live builds created under Unity 2018.1.x. In the meantime, I will keep pushing bug fixes to Legacy Stable 0.5. This will be the final build version compatible with legacy Enhanced Sky mod.

Once I cut over build process (sometime in next week or two), the "unity55-stable" branch and related Legacy Stable 0.5 builds will become deprecated and will not receive any further bug fixes or upates. As usual, users will need to test with latest live builds for new features under development and compatibility with latest mods.

How do you manage two branches with different Unity version? Do you use different worktree paths or is safe to just checkout branch on a single folder and open different editor?

I don't plan to manage it for very long, just a week or two. Builds are run cloud side so I probably won't even need to open in 5.5 again on my end, only send a few minor changes across.

But in theory, it should be fine to switch branch and own in appropriate version though. The project and code files are pretty much all text.

Upgraded to 2018.1.2f1 (win 64bit) successfully and everything seems to work okay. I do get this popup twice every time I open the solution in VS2017 which doesn't appear to be causing any issues but it is annoying.

I'm not sure on this one. I'm using VS2017 (Pro) as well and don't get this one. Thread below indicates it might be an issue with needing to update.

https://github.com/Unity-Technologies/A ... /issues/66

Let me know if you make any progress.

Hazelnut wrote: ↑Sat May 26, 2018 8:12 pm 2018.1.0f2 is the closest Linux version, and I suspect will work just fine.

Nice that we can move to the latest Unity editor! Great news.

June 1st saw the exact version released for Linux:

Official Installer:
2018.1.2f1: https://beta.unity3d.com/download/3709a ... nload.html
sha1: 8cb7bb1e3f753af55af8acceefad4ad26dd71b77

That's awesome, thanks for posting that for other Linux users.