That it to say, the problems with Carrara's UV mapping utility, most of which go back to version 4 or earlier; Non-standard cylinder map (wraps the face of one row instead of splitting at an edge). UV map corrupted when welding vertices in model room. "Nil pointer error" when detaching polygons in UV mapper. Impossible to do a locked 180 rotate (one can only do this freehand). UVmapping lost with several ordinary modeling routines (oddly enough, you can split an edge with edge tools, or collapse sub-D's for a denser modeler and still maintain the UV map. Tesselate with the tesselate tool, though, and the map reverts to spherical default.) And the list of "features, not bugs"; UV mapper window doesn't remember settings or window size (and the default is too small to use). Non-standard selection and navigation tools in UV mapper window. (Slowly, this is coming around; control-Z is now "undo" instead of "select all," double-click on an edge propagates selection now...) No "relax" function. No numeric functions, or manipulators; the only way to move a point is by dragging it -- and that doesn't work properly if there are other points even NEAR it. No "snap to grid" either. Oh, and related: Polygon group names vanish during editing of mesh -- even using SELECTION tools can cause this. All of these have been logged, many made it to the "confirmed" stage. As of over two years, though, not a one has been as much as assigned. Am I just being stupid continuing to struggle with mapping my models in Carrara (and Steve Cox's UV Mapper for all those things Carrara does REALLY badly)? Should I break my piggy bank for the bucks for a real UV mapping program? It does make for such a nicer workflow if you can map in Carrara whilst working on the model in question. For instance; take a dress with a set of buttons. The dumb way to map this is to finish the dress, export to mapper, collect all the buttons, laboriously flatten them out... The smart way is to build one button and map it before you duplicate it to finish off the dress!