Search Unity

Question NetCode Client Build Have Problem

Discussion in 'NetCode for ECS' started by AznableMiao, Feb 4, 2021.

  1. AznableMiao

    AznableMiao

    Joined:
    Apr 19, 2017
    Posts:
    9
    Hi, i build a windows client, and have a problem with netcode generated code "UnityNetCodeNullCommandDataSendCommandSystem".

    Here is log
     
    AznableMiao, Feb 4, 2021
    #1

  2. Chris7332

    Chris7332

    Joined:
    Feb 28, 2014
    Posts:
    1
    I ran into a similar issue when I had the API Compatibility Level in the Player Settings set to ".Net 4.x" and was building with the Platforms Package (which can only build for Mono 2.x if you're using the Classic Build Scheme). Try with API Compatibility Level set to ".NET Standard 2.0" and see if your issue persists.
     
    Chris7332, Feb 16, 2021
    #2

  3. AznableMiao

    AznableMiao

    Joined:
    Apr 19, 2017
    Posts:
    9
    After I changed the build backend in "Classic Scripting Settings", the error disappeared. It was strange but I can't reproduce this error now.
     
    AznableMiao, Feb 20, 2021
    #3

  4. NovaEiz

    NovaEiz

    Joined:
    Sep 6, 2017
    Posts:
    53
    I have the same problem, but only on Android.
    And it is not solved in any way.

    Although I created a build for Android 2 months ago. And everything worked. The packages are still the same, only Visual Scripting has been added.

    What to do? Will this be corrected?
     
    NovaEiz, Jun 7, 2021
    #4

  5. NovaEiz

    NovaEiz

    Joined:
    Sep 6, 2017
    Posts:
    53
    It is possible that 2 months ago I did an Android build in Unity 2020. But I don't remember exactly.
    I believe that this is the problem of 2021.

    I really want to build on Android.
    How soon can we expect a fix?
     
    NovaEiz, Jun 7, 2021
    #5

  6. AznableMiao

    AznableMiao

    Joined:
    Apr 19, 2017
    Posts:
    9
    Try to go back to 2020?
     
    AznableMiao, Jun 18, 2021
    #6

  7. CMarastoni

    CMarastoni

    Unity Technologies

    Joined:
    Mar 18, 2020
    Posts:
    896
    It is an incompatibility with 2021. Unfortunately is hard for NetCode (end DOTS in general) to be always compatible with the latest Unity 2021 (for many reasons). Please continue to use 2020.3.12f1 instead.
    I know that everyone would enjoy much having all the 2021 improvements
     
    CMarastoni, Jun 28, 2021
    #7
    optimise likes this.

  8. optimise

    optimise

    Joined:
    Jan 22, 2014
    Posts:
    2,129
    @CMarastoni. Actually I just hope I can get new Netcode package version soon but seems like it's dragged by new Entities package version. Is that new Entities package version have massive changes that hugely affect the release date? The release frequency is too low compares with last year 2020.
     
    optimise, Jun 28, 2021
    #8

  9. CMarastoni

    CMarastoni

    Unity Technologies

    Joined:
    Mar 18, 2020
    Posts:
    896
    The problem is not the NetCode package (it has been ready from long time already, I would say from February pretty much).
    It is more the way DOTS release has changed that prevents many package to release their updates. We are now making sure all dots packages works together when we release a new update. That of course are delaying things a bit.
    And indeed there are major changes in NetCode, especially the way code-gen works.
     
    CMarastoni, Jun 28, 2021
    #9
    Lukas_Kastern and optimise like this.

  10. Krooq

    Krooq

    Joined:
    Jan 30, 2013
    Posts:
    196
    I'm getting the same issue in a build for Windows.
    Strangely only IL2CPP is working for me with Mono 2.x throwing the error.
     
    Krooq, Aug 7, 2021
    #10
    AdamBebko likes this.

  11. AdamBebko

    AdamBebko

    Joined:
    Apr 8, 2016
    Posts:
    168
    I'm getting the same error in unity 2020.3.18. Building for MacOS. some combination Switching to il2cpp and .net 2.0 fixed it
     
    AdamBebko, Sep 20, 2021
    #11