Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Upgraded from 3.0.9 to 4.0.3 with these errors

Discussion in 'World Building' started by limpin_jezus, Feb 24, 2019.

  1. limpin_jezus

    limpin_jezus

    Joined:
    Nov 20, 2015
    Posts:
    18
    ProBuilder 3.0.9 to 4.0.3 after upgrading Unity 2018.2.20f to 2018.3.6f. I get these errors:

    Library\PackageCache\com.unity.probuilder@4.0.3\Editor\EditorCore\LogEditor.cs(27,37): error CS1503: Argument 1: cannot convert from 'UnityEditor.ProBuilder.Pref<LogLevel>' to 'UnityEngine.ProBuilder.LogLevel'

    Library\PackageCache\com.unity.probuilder@4.0.3\Editor\EditorCore\LogEditor.cs(39,94): error CS0117: 'LogLevel' does not contain a definition for 'Default'

    Library\PackageCache\com.unity.probuilder@4.0.3\Editor\EditorCore\LogEditor.cs(120,33): error CS1503: Argument 1: cannot convert from 'UnityEditor.ProBuilder.Pref<LogLevel>' to 'UnityEngine.ProBuilder.LogLevel'

    Any ideas about how to resolve?
     
    Last edited: Feb 24, 2019
    limpin_jezus, Feb 24, 2019
    #1

  2. gabrielw_unity

    gabrielw_unity

    Unity Technologies

    Joined:
    Feb 19, 2018
    Posts:
    960
    Hi! Could you let me know what your exact steps were? That will help determine where the errors are coming from. Thanks!
     
    gabrielw_unity, Feb 25, 2019
    #2

  3. limpin_jezus

    limpin_jezus

    Joined:
    Nov 20, 2015
    Posts:
    18
    Sure. I had a project built in Unity 2018.2.20f. I had ProBuilder package 3.0.9. In that project. I opened the project with Unity 2018.3.6f and let Unity upgrade the project. So far so good. ProBuilder 3.0.9 no errors in upgraded project. Go to package manager and see there is an upgrade to ProBuilder. Use package manager to upgrade package to 4.0.3. The 3 errors above are the result.

    If I remove the package and reinstall it fresh at 4.0.3, I get the same errors. If I revert back to 3.0.9, everything is fine. .net 3.5 or 4 doesn't seem to make a difference in the project settings.

    Thanks for the help.
     
    limpin_jezus, Feb 25, 2019
    #3

  4. gabrielw_unity

    gabrielw_unity

    Unity Technologies

    Joined:
    Feb 19, 2018
    Posts:
    960
    Ah ok- that's a flawless upgrade process, flawed result :( Sorry for the trouble! I'm not aware of any existing issue that would cause this, so could you create an official bug report via "Help > Report a Bug"? I'll ping the team here, too. Thanks again!
     
    gabrielw_unity, Feb 26, 2019
    #4