P0-MS4: Part 261: 2017.2 Port
by PhoenixGames on Oct.22, 2017, under Art and Designs, P-0, Software and Games, Spiritus Astrum
I am still having issues with the executable of 2017.2.
The project works fine in the editor, I have fixed the vast majority of the errors and warnings, but in the build, I am getting major memory issues.
It seems that there is a memory leak somewhere, that for some reason isn’t present (or at least, noticeable) in Unity 5.6 or in the Editor.
The issue may be caused by the fact that I am creating a lot of objects with very little optimisation, I may need to work on some LOD’s or other optimisations to reduce the memory footprint.
Going back to Unity 5.6 is not really an option at this point, since Unity 2017.2 has fixed some errors that I was getting, and I will need my workflow to be able to accommodate upgrading to later Unity versions in order to take advantage of the C# job system which will be coming in Unity 2018. This is required for my project.