Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Unity command line hanging while importing assets

Discussion in 'Editor & General Support' started by clint-jones, Sep 21, 2021.

  1. clint-jones

    clint-jones

    Joined:
    Feb 25, 2021
    Posts:
    1
    Using the command line for automated builds, Unity 2019.4 is consisently hanging while importing assets. Yet the project imports successfully when I manually load it in the UI. Could definitely use some suggestions at this point to get fully automated builds.

    The behavior is consistent on different hosts with the same configuration, so it doesn't appear to be environmental. This codebase successfully loaded and built with the Unity 2018.4 command line on the same systems.

    Unity Version: 2019.4.20f1
    UnityHub: 2.4.5
    Mac: Catalina 10.15.7
    Mac mini, 6-Core Intel Core i7 3.2 GHz
    256 KB L2, 12 MB Le3
    32G RAM

    COMMAND LINE ARGUMENTS:
    /Applications/Unity/Hub/Editor/2019.4.20f1/Unity.app/Contents/MacOS/Unity
    -projectPath <path>
    -silent-crashes
    -quit
    -batchmode
    -buildPath <path>

    Last entries the output are:
    ...
    Done importing asset: 'Packages/com.unity.2d.sprite/Editor/UI/SpriteEditor/SpriteEditor.uss' (target hash: '54ab9244337a1d211c5f7cf333d2b012') in 0.022951 seconds
    Shader 'Hidden/FXAA Preset 3': fallback shader 'Hidden/FXAA II' not found
    Shader 'TextMeshPro/Distance Field Overlay': fallback shader 'TextMeshPro/Mobile/Distance Field' not found
    Shader 'TextMeshPro/Distance Field': fallback shader 'TextMeshPro/Mobile/Distance Field' not found
    WARNING: Shader Unsupported: 'Unlit/Transparent Cursor' - All passes removed
    WARNING: Shader Did you use #pragma only_renderers and omit this platform?