Search Issue Tracker
Fixed in 2017.4.X
Fixed in 2018.1.X, 2018.2.X
Votes
0
Found in
2018.2.0b5
Issue ID
1038721
Regression
No
[Wintermute] Unity crashes when switching from Enlighten to PLM if the editor install path contains non-Latin characters
Steps to reproduce:
1. Install Unity in a folder with some non-Latin symbols. Or find a folder which contains Unity and change folder's name to "ąčęUnity"
2. Launch Unity
3. Create a new project or open an existing one
4. Navigate to the Lighting Settings window
5. In the Lightmapping Settings section, change the Lightmapper from Enlighten to Progressive Lightmapper
Actual result: Once project is opened, Unity crashes
Reproduced on Windows 10
Fixed in: 2018.3.0a1
Backported to: 2018.2.0b9, 2018.1.5f1, 2017.4.8f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
Add comment