Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1211605
Regression
No
LightingData.asset always generated as binary file when Asset Serialization mode is set to Force-Text
Steps to reproduce:
1. Open LightingData.Asset with a text editor in case_1211605 LightingData\Assets\Scenes\SampleScene
2. Notice that it is binary
Expected results: LightingData Assets created while Asset Serialization mode is set to "Force Text" are Text files
Actual results: LightingData Assets created while Asset Serialization mode is set to "Force Text" are Binary files
Reproducible with: 2017.4.34f1, 2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (2020.1.X):
This behavior is by-design. Lighting Data Assets can potentially be huge, as we store a lot of precompute data in them. Generally, we do not want to handle them as text, and some frameworks used by us do not have proper text serialization in place.