Unity .NET 4.6 experimental setting is not supported

Hi Everyone,

Just to make sure you don't turn on .NET 4.6 and stick to the stable .NET 3.5

We are getting more and more issues report that actually link back to the use of this experimental .NET 4.6 and at the present time we can't support such projects until Unity turn this feature as stable.

If you encounter issues, if you can't reproduce them using .NET 3.5, get in touch with Unity support directly so that they can improve and get closer to a support version.

Bye,

Jean

Comments

  • Yes,

    I am running a bunch of new tests on the latest 2018 beta to see if the issues got resolved ( we raised concerned back in 2017.2 but never got a reply), so hopefully it will be ok.

    Meanwhile, you are encouraged to try it out and report any issues to us and Unity should you find bugs when using 4.6 that do no occur when using 3.5, it's going to be hard because once you switch to 4.6 and use some of the new api, it will be impossible to check back...

    Bye,

    Jean
  • xblade724xblade724
    edited June 8
    Heya, any ETA on 4.6 support? Does Unity still call it experimental? We'd like to upgrade to the latest Unity in a few months -- just wanted to make sure we'd get to utilize one of their biggest features~
  • Hi,

    well, on paper Unity is out of experimental mode for 2018 and .net46 support, however, it seems that it's still not as stable as it should, I'll refer to a post yesterday from Robocraft developer that is using Photon, and he seems to wonder about .net46 reliability, which is not a good sign:

    so, I would not recommend at this point to switch to .net46 in production as you could end up being blocked and not able to revert, as going for .net46 makes it impossible to switch back without rewriting it all back...

    you can still upgrade to 2018 latest, but just don't switch to .net46 just yet, or at least fully aware of the possible deadend for short/middle terms.

    If you find during testing some misbehavior, please report back to us, we are actively seeking feedback on how pun performs within .net46 environment on the developers end.

    Bye,

    Jean
  • Hi,

    Just a note on this, that internally, tests with the latest version of Unity shows no sign of issues when using the stable .Net46 runtime.

    So if you encounter issues, make sure you get back us and explain your issue so we can create cases and validate them or else, fix them if we can on our side, or ultimately check with Unity what can be done.

    Bye,

    Jean
Sign In or Register to comment.