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
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Editor process remains running after closing Editor
- OnApplicationPause pauseStatus is incorrect after losing focus on macOS
- [Mono Upgrade]FileSystemWatcher FileSystemWatcherArgs.Name variable returning the full path instead of the relative file name
- Animator Blend Tree weight defaults to 0 for a frame when AnimationClipPlayable is created with script in Play Mode
- Overridden method is called when calling the base class method using a derived class delegate
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
StephenWoods
Jul 08, 2020 13:30
https://slides.com/raisebrand
https://old.reddit.com/r/BrandInfluencer/comments/hfggds/will_writer_near_me/?
https://makeawill.landen.co
https://www.mindmeister.com/1545073317/the-importance-of-will-writing
https://xifas17362.gitbook.io/espace/benefits-of-will-writing
https://bestrated.wufoo.com/forms/r1nxnhzf0lf6dwa/
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.
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?