Search Unity

Command Line Build Fails During Setting Of Worker Threads For Enlighten

Discussion in 'Editor & General Support' started by giacomohomunculus, Apr 15, 2019.

  1. giacomohomunculus

    giacomohomunculus

    Joined:
    Oct 3, 2018
    Posts:
    20
    Hello,

    When I build my project with the Editor open everything works fine.

    When I do it from the command line, and look at the log, it fails consistently at the same point, and this is always what is at the very end of the log:

    Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.039687 seconds (Nothing changed)
    Setting up 4 worker threads for Enlighten.
    Thread -> id: a50 -> priority: 1
    Thread -> id: 32cc -> priority: 1
    Thread -> id: 36b0 -> priority: 1
    Thread -> id: 60c -> priority: 1
    [Package Manager] Server::Kill -- Server was shutdown
    Cleanup mono
    Exiting batchmode successfully now!

    This is on a Windows 10 Enterprise tower with decent specs. The command line args are:

    C:\Program Files\Unity\Editor\Unity.exe
    -projectPath
    C:\Users\uy486d\Documents\Project
    -quit
    -batchmode
    -executeMethod
    HoloToolkit.Unity.BuildDeployTools.BuildSLN

    (see https://github.com/Microsoft/MixedR...kit/BuildAndDeploy/Editor/BuildDeployTools.cs for build method)

    In the log I see this towards the top:

    GfxDevice: creating device client; threaded=0
    Direct3D:
    Version: Direct3D 11.0 [level 11.1]
    Renderer: NVIDIA Quadro P4000 (ID=0x1bb1)
    Vendor: NVIDIA
    VRAM: 8083 MB
    Driver: 22.21.13.8601

    In the log of the Editor build, I see the GfxDevice has threaded=1.

    Any guidance on what may be the issue here?

    Thanks