Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
903103
Regression
Yes
[upgrade project] Errors on upgrading AssetStore "Tanks!!! Reference Project" project to 2017.1
Upgrade project problem - this project works fine in 5.6.0p2
On importing "Tanks!!! Reference Project" project from A$ to 2017.1 - errors appear.
How we can reproduce it
1 Create ne project
2 Go to AssetStore and find "Tanks!!! Reference Project" (https://www.assetstore.unity3d.com/en/#!/content/80165)
3 Import this package to your project
Actual result: when importing will be finished you will see 4 errors:
- "A polygon of TankTurret is self-intersecting and has been discarded. Try cleaning the mesh before exporting."
- "A polygon of Cliff3 is self-intersecting and has been discarded. Try cleaning the mesh before exporting."
- "A polygon of Column02 Shadow is self-intersecting and has been discarded. Try cleaning the mesh before exporting."
- "A polygon of Column02 is self-intersecting and has been discarded. Try cleaning the mesh before exporting."
Expected results: there should not be any errors
Comments (6)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
ArgusTheGameMaker
Feb 02, 2018 12:47
Same problem here in unity 2017.3.0f.
kakapakapaka
Sep 04, 2017 21:11
great blog and nice one
problemecium
Jul 18, 2017 19:44
Confirming not fixed. All meshes I have imported throw this warning upon opening a project in 2017.1.0f3 .
lod3
Jul 13, 2017 18:16
Not fixed. Getting this error for every single mesh (131 of them) in ICE Creature Control. Same error, just for different meshes. Only in 2017.1.0b1