Search Issue Tracker

Fixed in 2019.3.X

Fixed in 2018.4.X, 2019.2.X

Votes

0

Found in

2018.3.0a7

2018.3.6f1

2019.1.0a1

2019.2.0a1

Issue ID

1131677

Regression

No

Worker threads for Enlighten are set up when launching a Server Build

Deployment Management

-

How to reproduce:
1. Create a new Unity project
2. Open Build Settings
3. Check the 'Server Build' option
4. Build and Run the project

Expected result: no worker threads for Enlighten are set up upon launch
Actual result: multiple worker threads for Enlighten are set up upon launch

Reproducible with: 2018.3.0a7, 2018.3.8f1, 2019.1.0b6, 2019.2.0a8
Could not test with: 2017.4.23f1, 2018.3.0a6(Server Build feature not yet implemented)

Notes:
Issue does not reproduce when Realtime Global Illumination setting is unchecked

Comments (8)

  1. Saeed-Barari

    Nov 13, 2023 15:53

    same thing happening 2021.3.10f1

  2. GetLitGames

    May 13, 2022 14:12

    Unity 2020.3.24f1 still happening on Server Build when shutting down

  3. Mochnant

    Dec 20, 2021 05:37

    Still occurring in 2020.3.25f1.

    Setting up 12 worker threads for Enlighten.
    Thread -> id: 4b8 -> priority: 1
    Thread -> id: b5ec -> priority: 1
    Thread -> id: b2a4 -> priority: 1
    Thread -> id: af04 -> priority: 1
    Thread -> id: 7448 -> priority: 1
    Thread -> id: b784 -> priority: 1
    Thread -> id: 6450 -> priority: 1
    Thread -> id: 188 -> priority: 1
    Thread -> id: a2b4 -> priority: 1
    Thread -> id: a870 -> priority: 1
    Thread -> id: aa50 -> priority: 1
    Thread -> id: 5e5c -> priority: 1

  4. silviu-georgian77

    Aug 30, 2021 19:25

    Still happens in 2021.1.16f1

  5. Develax

    May 15, 2021 10:20

    Still have this in Player.log in Unity 20.20.2.0f1

    Setting up 2 worker threads for Enlighten.
    Thread -> id: 4078 -> priority: 1
    Thread -> id: 4f38 -> priority: 1

  6. crogersarvr

    Feb 28, 2020 01:33

    This happened with 2019.2.6 on server and android client.
    All Unity lighting is turned off.
    In the future I think it would helpful to list the complete version number for versions where this claims to be fixed.

  7. Killersan

    Sep 14, 2019 11:19

    This issue still occurs in Unity 2019.3.0b3. Can you tell me in which 2019.3.x it was fixed?

Add comment

Log in to post comment