Hokay...interesting... I just created two cylinders. On the left, a prim from the assembly room drop-down. Texture is a cylinder projection using the Checker pattern function. On the right, a cylinder created from the drop-down in the Vertex Room. No modification was performed on it. In the UVmap drop-down in the Properties Tray was set to Cylinder, and -- most importantly -- Wrap U and V were unchecked. Material on this one is parametric mapping, checker pattern function. Note the nastiness towards the left front face. Now, this is where it gets tricky. If I re-check "Wrap U and V" -- either in Properties or within the custom UV Mapping room -- the cylinder becomes normal. Sort of normal. Actually, what it is doing is splitting the last poly over the margins (the "wrap around") of the UV space. So this would actually be fine and peachy if I was doing a map of, well, a cylinder. With no top or bottom, and no other model occupying the UV map. But the instant I try to scale the UV map, it becomes obvious that this smooth mapping is only being achieved by using the edges of the UV space itself for a seam. I can't scale it, you see, without either detaching the UV's that stretch across the window, or unchecking the "wrap" function -- in which case they reset themselves to wrap around INSIDE the mapped object. Now contrast this with, well, every other application I have used. When you apply a cylinder map, it may or may not be pushed to the edge of the UVspace, but there is an actual seam created, a split in the mesh, so that one row of verts is copied to two sides of the map. In Steve Cox's UVmapper (which I usually use) it is then trivial to rescale, move, etc. as needed. However. Given my previous experience with Eovia, I can almost guarantee that in their eyes this wrap-around-or-through function was not an error or bug, but in fact was designed As A Feature.