Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.1p4
Issue ID
1018144
Regression
No
[ProBuilder] Model export does not work correctly when non-english culture is set used
Steps to reproduce:
1. Open user attached project
2. Select "Icosphere" game object
3. Click on Tools -> ProBuilder -> Export -> Export Obj
4. In Project window select "Show in Explorer" to force assets refresh
5. In the editor console window notice "ImportFBX Errors"
6. Observe that the object imported is broken
Expected result: model export should work correctly when non-english culture is set
Reproduced in: 2018.2.0a5, 2018.1.0b13, 2017.3.2f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment