Announcement

Collapse
No announcement yet.

Unity 2019 - Project Porting Error Resolution

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Unity 2019 - Project Porting Error Resolution

    With the release of A18, Unity 2019.1 is now used. When upgrading Unity and attempting to port over your project you may run into a plethora of beautiful red errors in the console.

    This is likely being caused due to your saved project settings referencing the old .NET 3.5, whereas .NET 4 is now used:
    Edit > Project Settings > Player > Other Settings > Configuration > Scripting Runtime Version > .NET 4.x Equivalent

    .NET 4.x error spam should now be resolved in your ported project and related scripts working.

    #2
    Thanks! I'm sure I would have run into this.

    Comment


      #3
      May I ask if a new ExportAssetBundles.cs is required for the unity 2019?

      Comment


        #4
        So far my 2018 unity works just fine in a18. I'm told the script also works in 2019 though...

        Comment


          #5
          Thank you very much, but my model displays "Object reference not set to an instance of an Object" on the console.

          Comment


            #6
            The exact version of Unity that was used for the A18 is 2019.1.0f2.
            But the exact same version seems impossible to download from the developer's website.
            Then what version of Unity would you recommend to use?

            Comment


              #7
              Go here and download the very bottom one. 2019.1.0. Pretty sure that's the correct version.

              https://unity3d.com/get-unity/downlo...141.1548400595

              Comment


                #8
                Originally posted by bdubyah View Post
                Go here and download the very bottom one. 2019.1.0. Pretty sure that's the correct version.

                https://unity3d.com/get-unity/downlo...141.1548400595
                Yes i know that i can download another close version, but how it will work?
                Maybe, then download version 2019.2? or 2019.3?

                Comment


                  #9
                  Don't do 2019.3, do 2019.2

                  Comment


                    #10
                    Originally posted by Guppycur View Post
                    Don't do 2019.3, do 2019.2
                    Yes, thank You, i also subconsciously chose 2019.2.9f1.

                    Comment

                    Working...
                    X