Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1308927
Regression
No
Inspector displaying wrong characters when using ANSI encoding and non latin characters in a Shader property
How to reproduce:
1. Open the attached project (case_1308927_Shader_Characters)
2. Open OnlyColor.shader with Visual Studio
3. Delete an empty line or add a comment to recompile the shader
4. Click on OnlyColor.shader to see the information in the Inspector
5. Compare the name of the _Color property in the shader file and in the inspector
Expected result: The names in the shader file and in the inspector match
Actual result: Inspector is displaying incorrect characters
Reproducible with: 2018.4.30f1, 2019.4.18f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a3
Workaround: Use a different encoding for the shader file (e.x. Unicode UTF-8)
Notes:
1. Before recompiling the shader Inspector will display INVALID_UTF8_STRING
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
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
- Context menus open on a different monitor when there are three monitors used
Resolution Note (2021.2.X):
Everything works correctly when using UTF-8. As it's close to impossible to detect the correct encoding, please use UTF-8. We will update the manual to mention this.