Quote:Working with Unity for so many years now, nothing suprises me anymoreThe bad thing is that I don't have any statistics about my customers, not even an email address or any opportunity to make a survey. I would drop Unity 3 instantly, but I'm worrying about loosing customers. Supporting multiple versions is a pain...
Regarding the custom mesh errors: Extrusion is done in two steps: finding edge loop(s) and extruding them. Looks like the sorting inside the edge detection is causing the trouble.
I guess it would be taking a pretty chance to just drop 3.2 support and just see how people react.
But yeah I remember we once had a digital signature solution for our customers which naturally got updated to newer .NET versions. Until it turns out that one of our biggest customers was still using .NET 1.5 and was unable/unwilling to upgrade. It sure is a pain to build and test 2 separate versions.I have one additional question regarding the mesh extrusion btw. Would it be possible to connect the last edge loop with the first (in splines that close and have a mesh going the whole way) in order to avoid shading artifacts due to the last segment being similar to a hard edge? Or would that not really fit elegantly in the current architecture/user workflow?
