Simon.Anderson Posted January 23, 2017 Share Posted January 23, 2017 Hi All, Given Unigine 2.3.1 supports C++ 14/Visual Studio 2015 (now with edit and continue, resharper for C++ etc and all that good stuff) AND the API is now consistent across both UnigineScript and C++/C# is there any reason to keep using UnigineScript at all? Given C# is now also supported I'm struggling to come up with a reason to keep coding in UnigineScript ( other than there is way more UnigineScript sample code ). Is anyone in the same situation? Does anyone know of a situation where UnigineScript would be preferable? Any help/opinions would be much appreciated. Cheers, Simon 1 Link to comment
ulf.schroeter Posted January 23, 2017 Share Posted January 23, 2017 UnigineScript might have a lower entry level, as it is build-in and only requires a simple text editor. Also for legacy code support it is (at least for some time) for sure required. Nevertheless for any project having sone coding requirements I would strongly recommend using C#/C++ due to professional debugging support. Debugging more complex code in UnigineScript was a pain and prodctivity killer for years. Link to comment
Simon.Anderson Posted January 24, 2017 Author Share Posted January 24, 2017 Thanks for that ulf! Yes, unfortunately we have a lot of legacy code also. Link to comment
Recommended Posts