Search Issue Tracker
By Design
Votes
1
Found in
5.0.0b18
Issue ID
664946
Regression
No
[API] Setting the lightmap manually during playmode does not work outside editor
Setting the lightmapping settings to use a certain lightmap and the renderers to use the lightmapping data has no effect outside the editor.
To reproduce:
1. Open attached repro.zip
2. Open scene "MainScene". After 2 seconds in play mode it takes a prebaked lightmap from the resources folder and sets the lightmapping settings to use it. Then it also sets the lightmapping index of the renderers so the lightmap is used
3. Enter play mode in the editor - notice that the lightmap data is loaded up and used by the renderers (not correctly, but it's okay)
4. Build & run for windows standalone
5. Notice that nothing changes after setting up the lightmapping settings
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- Package Manager Filters (Status) dropdown is different color than Packages, Sort or Add package dropdowns
Add comment