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
-
zemayk
Jan 27, 2020 13:58
NJMCDirect is an online portal where you need to pay the fines. It takes only a few minutes of time to pay for the ticket. This is the easy way to pay the fine compared to paying the fine manually in the court.
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
- A new Additive Scene cannot be created when an empty Untitled Scene is not dirty
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
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.