{"id":2597,"date":"2021-12-09T12:00:08","date_gmt":"2021-12-09T12:00:08","guid":{"rendered":"https:\/\/www.katsbits.com\/codex\/?p=2597"},"modified":"2023-09-07T15:50:39","modified_gmt":"2023-09-07T14:50:39","slug":"uv-maps","status":"publish","type":"post","link":"https:\/\/www.katsbits.com\/codex\/uv-maps\/","title":{"rendered":"UV Map Basics"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 counter-hierarchy ez-toc-counter ez-toc-light-blue ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-69f55bfba3520\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-69f55bfba3520\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#uv-map-basics\" >UV Map Basics<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#uv-map-elements\" >UV Map Elements<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#default-uv-maps\" >Default UV Maps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#generate-uv-map-%e2%80%93-uvmap\" >Generate UV Map &#8211; UVMap<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#generate-uv-map-%e2%80%93-unwrap\" >Generate UV Map &#8211; Unwrap<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#edit-uv-maps\" >Edit UV Maps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.katsbits.com\/codex\/uv-maps\/#optimising-uv-maps\" >Optimising UV Maps<\/a><\/li><\/ul><\/nav><\/div>\n<p>For newer versions of Blender <b>UV Maps<\/b> play a more important role because, with the removal of the now obsolete Blender Render engine, textures and materials are not rendered on surfaces without them. For correct display this means objects need to be <b>UV Unwrapped<\/b>, and images <b>UV Mapped<\/b> to those unwrapped surfaces, before anything is seen, requiring a basic understanding of <b>UV Maps<\/b>.<\/p>\n<blockquote style=\"background-color: #fc0; color: #000;\"><p><b>Important<\/b>: see <a href=\"https:\/\/www.katsbits.com\/codex\/uv-editing\/\">UV Editing (Workspace) Basics<\/a> for more on <b>UV editing<\/b> generally.<\/p><\/blockquote>\n<h3><span class=\"ez-toc-section\" id=\"uv-map-basics\"><\/span>UV Map Basics<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>UV Maps are essentially two-dimensional representations of three-dimensional structures that have been processed, or <i>unwrapped<\/i>, to form an otherwise flat layout or <i>map<\/i> of an object to which an image or material can be assigned. In other words, for a mesh to appear as though its made from wood, a 2D <i>map<\/i> of the object is needed for the wood texture to appear correctly positioned on the mesh when viewed or rendered. This <i>map<\/i> is the objects <b>UV Map<\/b>, the process of creating it, <b>UV Unwrapping<\/b>.<\/p>\n<blockquote><p><b>Design note<\/b>: although UV Unwrapping and UV Mapping are technically distinct terms they are often used interchangeably to refer to the same process; mapping or preparing an object for image assignment.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-basics.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-basics.jpg\" alt=\"Simple UV Unwrapped object\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>UV Editing Workspace showing a simple (default) Cube mesh object UV Unwrapped (right) to create a UV Map (left) ready for an image to be mapped so it appears in the 3D Viewport.<\/i><\/p>\n<h3><span class=\"ez-toc-section\" id=\"uv-map-elements\"><\/span>UV Map Elements<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>UV maps are edited, manipulated and managed in the <b>UV Editor<\/b>, or <b>UV Editing Workspace<\/b>, using the same basic compositional and selectable elements as a mesh in the 3D Viewport, i.e. a <b>Vertex<\/b> [1], <b>Edge<\/b>[3], <b>Face<\/b> [5], and UV editing specific, <b>Island<\/b> [7]. Each has a corresponding <b>UV Selection Mode<\/b> so the different elements can be selected and manipulated individually, or as part of a larger group or collection, using the <b>Move<\/b> (<span class=\"shortcutkey\">G<\/span>), <b>Rotate<\/b> (<span class=\"shortcutkey\">R<\/span>) and <b>Scale<\/b> (<span class=\"shortcutkey\">S<\/span>) tools available in the <b>UV Editor Toolbar<\/b> (<span class=\"shortcutkey\">T<\/span>) down the left side of the editor. With these, UVs, individually or as part of a larger collection, can be manipulated relative to the square workspace grid that represents the area occupied by an image, the <b>Texture Space<\/b>, it&#8217;s this area that determines the &#8216;what&#8217; and &#8216;where&#8217; placement of UVs with respect to any image mapped to an object. To set the <b>UV Selection Mode<\/b>, in the <b>UV Editor<\/b> click the appropriate button in the UV Editors Header, <b>Vertex<\/b>, <b>Edge<\/b>, <b>Face<\/b>, <b>Island<\/b>, or press (main keyboard) <span class=\"shortcutkey\">1<\/span>, <span class=\"shortcutkey\">2<\/span>, <span class=\"shortcutkey\">3<\/span> or <span class=\"shortcutkey\">4<\/span> respectively.<\/p>\n<blockquote><p><b>Design note<\/b>: when working with UVs and the UV Editor generally, although there are a number of different element types available &#8211; Vertex, Edge, Face, Island &#8211; they are generally all displayed, but not necessarily selectable, at the same time regardless of the active selection mode. For example the vertices of <b>Vertex<\/b> selection mode are displayed in place at UV corners and junctions even though <b>Island<\/b> segments might be the active selection and mode set.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-vertex.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-vertex.jpg\" alt=\"UV Vertex element\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-edge.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-edge.jpg\" alt=\"UV Edge element\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-face.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-face.jpg\" alt=\"UV Face element\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-island.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-island.jpg\" alt=\"UV Island element\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Each element that constitutes an UV map has its own selection mode; <v>Vertex<\/v> [1] selection mode for vertices [2], <b>Edge<\/b> [3] for edges [4], <b>Face<\/b> [5] for faces or surfaces [6] and <b>Island<\/b> [7] for complete UV or detached sections\/segments [8].<\/i><\/p>\n<h3><span class=\"ez-toc-section\" id=\"default-uv-maps\"><\/span>Default UV Maps<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Most of Blenders <i>mesh primitives<\/i>, that is the <i>Cube<\/i> (scene default), <i>Plain<\/i>, <i>UV Sphere<\/i>, <i>Ico Sphere<\/i>, <i>Cylinder<\/i>, <i>Cone<\/i> and <i>Torus<\/i>, the objects generally dropped in to and edited in the 3D Viewport, are essentially pre-unwrapped to include a basic UV map that&#8217;s ready for use (image assignment). In other words in dropping one of these primitives into the scene, <b><i>Add \u00bb Mesh \u00bb [primitive]<\/i><\/b> (or <span class=\"shortcutkey\">Shift<\/span> + <span class=\"shortcutkey\">A<\/span>), the included UV map then only needs to be updated or modified, not created or generated.<\/p>\n<blockquote><p><b>Design note<\/b>: the default UV maps are generated such that they fit within the boundary of the available <b>Texture Space<\/b> (the grid area in the editors workspace). As a result UV maps may not be specifically optimised for the shape represented relative to the amount of space available.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/default-uv-map-primitives.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/default-uv-map-primitives.jpg\" alt=\"Mesh Primitives and their UV Maps\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Each of the default mesh primitives (except Circle object) is UV Unwrapped and carries a basic UV Mapped that can be left as is, or edited in the UV Editor (UV Editing Workspace) &#8211; the maps primarily serve so objects have an appropriate UVMap data block in the <b>UV Maps<\/b> subsection of Object Data Properties (<a href=\"#generate-uv-map-uvmap\">see below<\/a>).<\/i><\/p>\n<h3><span class=\"ez-toc-section\" id=\"generate-uv-map-%e2%80%93-uvmap\"><\/span>Generate UV Map &#8211; UVMap<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Internally UV Maps are not just a flat representation of an object, they&#8217;re an editable component of an underlying <i>datablock<\/i>, <b>UVMap<\/b>. In practice this technically means editable UV maps can be generated in two ways; 1) adding a <b>UVMap<\/b> datablock, or 2) <a href=\"#generate-uv-map-unwrap\">unwrapping the object using <b>Unwrap<\/b> options<\/a>. In either instance a <b>UVMap<\/b> datablock is generated and displayed in <b>UV Maps<\/b> (<b>Object Data Properties<\/b>), accompanied by an editable <b>UV map<\/b> shown in the <b>UV Editor<\/b>.<\/p>\n<blockquote><p><b>Design note<\/b>: the difference between adding a datablock or unwrapping an object essentially boils down to; <i>unwrapping objects<\/i> allow for UVs to be edited for visual affect, whereas <i>creating datablocks<\/i> allows for multiple UV maps to be assigned to a single object, each map has its own datablock, which can then be selected in <b>UV Maps<\/b> list in <b>Object Data Properties<\/b> for editing in the <b>UV Editor<\/b> (each datablock is typically assigned a reset UV map &#8211; <a href=\"#default-uv-maps\">see above<\/a>). Below for example, the <b>UVMaps<\/b> aperture list in Object Data Properties, displays three different datablocks, each accompanied by a unique UV layout that can be modified wholly independently of the other available datablocks.<\/p>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-layer1.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-layer1.jpg\" alt=\"UVMap 'layers' (1)\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-layer2.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-layer2.jpg\" alt=\"UVMap 'layers' (2)\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-layer3.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-layer3.jpg\" alt=\"UVMap 'layers' (3)\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Using UVMap datablocks objects can be assigned multiple UV maps [a-c], each being different from their neighbours, mapped to specifically associated images; top &#8211; reset [a], middle &#8211; default [b], bottom &#8211; individual faces [c].<\/i><\/p><\/blockquote>\n<p>To generate or create a new <b>UVMap<\/b> datablock, in <b>Object Data Properties<\/b> click the <b>+<\/b> button [9] to the right of the <b>UV Maps<\/b> aperture. An entry appears named <b>UVMap<\/b> [10]. Looking to the <b>UV Editor<\/b> on doing this a UV map will have been created, faces mapped individually 1:1 to the available <b>Texture Space<\/b>, essentially resetting the objects UVs in its entirety. To create additional UVMap <i>datablocks<\/i> click the <b>+<\/b> button again, double-click each entry to rename as required (Blender defaults to using an incremental numerical append to make each instance unique, i.e. *.001, *.002 etc. or UVMap.<i>001<\/i>, UVMap.<i>002<\/i>) etc., press <b>Enter<\/b> to confirm.<\/p>\n<blockquote><p><b>Design note<\/b>: when creating a UVMap datablock the associated UV map is typically reset and mapped 1:1 to the available Texture Space represented by the editor grid regardless of face, triangle or ngon selection. In other words, a square UV will fill the square grid, a triangle half on the diagonal, and an ngon based on the number of sides.<\/p>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-reset-uv.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-map-reset-uv.jpg\" alt=\"Cylinder with 'reset' UVs\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>A UV Sphere object (right) with <b>UVMap<\/b> datablock assigned has its UVs essentially &#8216;reset&#8217; so each face occupies the entire available <b>Texture Space<\/b> (left). This is typical for all mesh objects when adding UVMap datablocks to an object &#8211; red = ngon, blue = face, green = triangle.<\/i><\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/create-uvmap-datablock.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/create-uvmap-datablock.jpg\" alt=\"Creating a new UVMap datablock\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Creating a new UVMap datablock in Object Data Properties, click the + button [9] then rename the map if necessary [10] (especially if several maps are being used &#8211; some game development environments require multiple maps to follow a specific naming convention).<\/i><\/p>\n<h3><span class=\"ez-toc-section\" id=\"generate-uv-map-%e2%80%93-unwrap\"><\/span>Generate UV Map &#8211; Unwrap<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>To create a <i>UV map<\/i> manually using <b>Unwrap<\/b>, with an object selected in the 3D Viewport and in <b>Edit Mode<\/b> &#8211; <i><b>UV Editing Workspace<\/b> does this automatically when active<\/i> &#8211; ensure the faces or area to be UV unwrapped are selected, then from the <b>UV<\/b> menu [11] in the <b>UV Editor<\/b>, select <b>Unwrap<\/b> [12], then <b>Unwrap<\/b> [13] &#8211; <b><i>UV \u00bb Unwrap \u00bb [Unwrap\/option]<\/i><\/b>. Alternative in the <b>3D Viewport<\/b> click the <b>UV<\/b> menu [14] then <b>Unwrap<\/b> [15] or another option &#8211; <b><i>UV \u00bb [Unwrap\/option]<\/i><\/b>. In either instance the mesh will be unwrapped and UV map generated based on the option chosen and\/or whether the mesh has been &#8216;marked&#8217; to accommodate UV mapping with <b>Seams<\/b>, <b>Edge Split<\/b> or other modification (<a href=\"#edit-uv-maps\">see below<\/a>).<\/p>\n<blockquote style=\"background-color: #fc0; color: #000;\"><p><b>Important<\/b>: by default UV editing is selection based, that is, UVs must be selected in the 3D Viewport before being displayed in the UV Editor. This behaviour can be disabled (toggled) by enabling <b>UV Sync Selection<\/b> [d], which displays the entire UV map regardless of mesh selection in the 3D Viewport. UV Sync Selection also highlights <i>selection correspondence<\/i> [e], that is, editing a UV vertex or edge in one location [ii] highlights and synchronises manipulations between all positions that vertex or edge might appear in the overall UV map [i &#038; iii]. Faces however, differ. When UV Sync Selection is active, and the selection mode set to Face, selections behave as though they are <a href=\"#edit-uv-maps\">Split<\/a> [f], and can be manipulated independently of neighbouring surfaces without affecting other areas of the overall UV map.<\/p>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-sync-mode.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-sync-mode.jpg\" alt=\"Enabling UV Sync Selection\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-sync-face-select.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-sync-face-select.jpg\" alt=\"Face selection in UV Sync mode\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Image top: Enabling <b>UV Sync Selection<\/b> [d] disables the default selection-based display of UVs in the UV Editor, which also then show connected elements for each selection [e] &#8211; these move in sync when edited. Image bottom: when <b>UV Sync Selection<\/b> is active, face selection and manipulation is as if they are <b>Split<\/b> or detached all the time [f], corresponding faces are not highlighted and can be moved independently of surrounding faces.<\/i><\/p><\/blockquote>\n<blockquote><p><b>Design note<\/b>: if the mesh has not been prepared for unwrapping the resulting map is typically &#8216;reset&#8217; so each face is mapped one-to-one with the Texture Space.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-editor-unwrap.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-editor-unwrap.jpg\" alt=\"UV Editor Unwrap options\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>To generate a UV map using Unwrap, from the <b>UV Editor<\/b> click the <b>UV<\/b> menu [11], <b>Unwrap<\/b> [12] and then an option, typically Unwrap [13]. The creates a UV based on the options selected and whether the mesh (select faces) have been treated for unwrapping (Seams etc.).<\/i><\/p>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/3d-viewport-unwrap.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/3d-viewport-unwrap.jpg\" alt=\"3D Viewport Unwrap options\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>UV maps can also be generated in the <b>3D Viewport<\/b> and the <b>UV<\/b> menu [14] that&#8217;s available when in <b>Edit Mode<\/b> &#8211; make a selection and access the <b>UV<\/b> menu then select <b>Unwrap<\/b> [15] or other option as needed.<\/i><\/p>\n<h3><span class=\"ez-toc-section\" id=\"edit-uv-maps\"><\/span>Edit UV Maps<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Subject to a mesh being UV Unwrapped and a UV Map available, to display and then edit UVs, by default surfaces need to be selected in the <b>3D Viewport<\/b>, on their own (single), as part of a group (multiple), or the mesh in its entirety (all). When this is done UVs corresponding to the selected surfaces highlight in the <b>UV Editor<\/b>, which can then be edited or manipulated [16] using the tools available in the <b>Toolbar<\/b> to the left [17], based on the <b>UV Selection Mode<\/b> set [18], e.g. UV vertices being realigned using the <b>Move<\/b> tool because <b>Vertex<\/b> selection mode it set.<\/p>\n<blockquote><p><b>Design note<\/b>: see <a href=\"https:\/\/www.katsbits.com\/codex\/uv-editing\/\">UV Editing (Workspace) Basics<\/a> for more on the UV Editor and editing UV maps.<\/p><\/blockquote>\n<blockquote style=\"background-color: #fc0; color: #000;\"><p><b>Important<\/b>: subject to <a href=\"#generate-uv-map-unwrap\">UV Sync Select<\/a> (see yellow boxout), by default UVs do not display in the UV Editor [i] unless complete faces are selected in the 3D Viewport, in other words, selection needs to be of intact triangles, faces or ngons using any selection mode, Vertex, Edge or Face [ii].  <\/p>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/incomplete-selection.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/incomplete-selection.jpg\" alt=\"UVs visibility is selection based\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>UVs don&#8217;t display in the UV Editor [i] unless intact surfaces are selected in the 3D Viewport regardless of the selection mode, Vertex, Edge or Face, used to select triangles, quadratics or ngons.<\/i><\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/editing-uvs.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/editing-uvs.jpg\" alt=\"Editing UVs in UV Editor area\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>To see UVs in the UV Editor corresponding faces need to be selected in the 3D Viewport. Once this is done UV elements [16] can be manipulated using the available tools [17] based on the selection mode set [18].<\/i><\/p>\n<p>In addition to editing UVs based on Vertex, Edge, Face and Island selections, they can be broken apart using <b>Split<\/b> so vertices, edges, and faces can be manipulated independently of their surroundings or connecting elements. To do this, in the UV Editor set the Selection Mode and make a selection. From the <b>UV<\/b> menu click <b>Split<\/b> then <b>Selection<\/b> &#8211; <b><i>UV \u00bb Split \u00bb Selection<\/i><\/b> [21] (or press <span class=\"shortcutkey\">Y<\/span>). Depending on the selection mode this will break the selected elements apart, or detach them [19], from neighbouring elements [20] allowing further editing of the UV independently of their surrounds.<\/p>\n<blockquote><p><b>Design note<\/b>: generally speaking <a href=\"https:\/\/www.katsbits.com\/codex\/uv-editing\/#uv-basics\">Seams<\/a> should determine how UVs are segmented or broken apart for mapping &#8211; splitting UVs as described here can lead to unnecessary surface splits in the mesh which might then break <a href=\"https:\/\/www.katsbits.com\/codex\/smoothing\/\">Smoothing<\/a>, so care should be exercised creating content for use outside Blender.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/split-elements.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/split-elements.jpg\" alt=\"How different elements behave when Split\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/split-uvs.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/split-uvs.jpg\" alt=\"Using Split to separate UVs\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>UVs generally cannot be edited independently of their neighbours. However, this can be done in the UV Editor after a selection is made using <b>Split<\/b>. Image top: the basic elements broken into their constituent parts; one vertex splits into several depending on the connecting vertices, edges split similarly depending on connecting edges, and faces split based on intact selections. Image bottom: a single UV face [19] (image bottom) is moved away from the larger selection [20] after its been separated from the group [21].<\/i><\/p>\n<p>Similarly UV elements can be joined in the UV Editor using <b>Merge<\/b>, this allows for different UV configurations within the UV Editor to suit the image being mapped to an object rather than an object being mapped to an image. To do this, make a selection then from the <b>UV<\/b> menu select <b>Merge<\/b>, <b>By Distance<\/b> or other option &#8211; <b><i>UV \u00bb Merge \u00bb By Distance<\/i><\/b> [22] (or press <span class=\"shortcutkey\">M<\/span>). This collapses elements [23] and\/or joins them together [24].<\/p>\n<blockquote style=\"background-color: #fc0; color: #000;\"><p><b>Important<\/b>: by default Blender automatically merges UV vertices that are in close proximity or coincidental to one another when selected, or where not, will behave similar to the <b>By Distance<\/b> option available in the <b>Merge<\/b> menu. In addition, UVs can only be merged where a physical relationships exists between elements &#8211; it is not possible to merge a given UV from one side of a map with that on another unless there is a &#8216;shared&#8217; vertex, edge or face between the two.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-merge-by-distance.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-merge-by-distance.jpg\" alt=\"Merge UVs by Distance\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>When using <b>By Distance<\/b> [22] a threshold can be used &#8211; <b>Merge UVs by Distance<\/b> [23] &#8211; to Merge UV vertices together [24], essentially the same &#8216;remove doubles&#8217; function available to meshes in Edit Mode but for UVs (and UV Editor).<\/i><\/p>\n<h3><span class=\"ez-toc-section\" id=\"optimising-uv-maps\"><\/span>Optimising UV Maps<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The overall structure and general appearance of a UV map is determined by the mesh being unwrapped and the way that might be marked with Seams to force splits, separations, or other detachments, between elements that do not necessarily need to reflect the object being unwrapped, or represent the best layout therein. In other words, maps do not specifically need to retain their original form so can be modified, parts shuffled into space that would otherwise remain unused. This is, in essence, what <b>UV Optimisation<\/b> is, the (re)organisation of an objects UVs to take full advantage of any available Texture Space.<\/p>\n<blockquote><p><b>Design note<\/b>: generally speaking UV layouts sit within the space defined by the gridded area of the UV Editor (<i>Texture Space<\/i>), but may extend beyond (<i>Texture Bounds<\/i>) depending on requirements, i.e. unwrapping a UV that tiles across a large object.<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimisation-default.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimisation-default.jpg\" alt=\"Wasted UV\/Texture Space\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimisation-alt-1.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimisation-alt-1.jpg\" alt=\"Optimising UVs alternative layout I\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimisation-alt-2.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimisation-alt-2.jpg\" alt=\"Optimising UVs alternative layout II\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Image top: the default UV map uses six (6) of the available sixteen (16) units, ten (10) remain. In terms of raw numbers this indicates an inefficient layout. Image middle and bottom: show the same map split into faces and reorganised to make better use of the space, the remained then clear to be used for other items (<a href=\"https:\/\/www.katsbits.com\/codex\/multi-object-editing\/\">multi-object<\/a> mapping) or parts of the same object.<\/i><\/p>\n<p>With this in mind, when organising UVs two general considerations should be kept in mind; 1) UVs <i>relative size<\/i> or scale, and 2) keeping <i>texture density<\/i> consistent across all UVs. In practice this might mean small UV sections being scaled up to prevent pixilation, larger islands being scaled relative to each other so texture patterns match across surfaces, or individual UVs being placed atop each other for 1:1 mapping.<\/p>\n<blockquote><p><b>Design note<\/b>: a great deal of UV map optimisation is determined by outcome. In other words the UV map for a particular object might utilise a combination of approaches, small mesh details might use slightly larger areas of an image to increase texture density while other relatively unimportant sections use overlaid UVs. In practice optimisation does not always obligate or require exclusive use of one approach to UV optimisation over others, the point of is achieve the best outcome possible within the bounds of the mapped image.<\/p>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimising-combo.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 98.5%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-optimising-combo.jpg\" alt=\"Optimised UV map in Blender\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>In practice most UV maps tend to use a combination of approaches to mapping depending on the mesh and how some sections might need to appear more visually detailed than others, for example different areas might need unique texturing [i] whereas as others repeat, in whole or part, so UVs repeat using different areas [i] of the mapped image [k].<\/i>\n<\/p><\/blockquote>\n<p><a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-texture-density.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-texture-density.jpg\" alt=\"UV map empty space\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<a href=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-texture-density-scaled.jpg\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" style=\"width: 100%; height: auto;\" src=\"https:\/\/www.katsbits.com\/images\/tutorials\/uv-editing\/uv-texture-density-scaled.jpg\" alt=\"Scaled UV map\" width=\"900px\" height=\"500px\" border=\"0\" \/><\/a><br \/>\n<i>Image top: the default UV map and corresponding texture density (UVs are rearranged so each UV face occupies a single &#8216;unit&#8217; of the assigned image for clarity). Image bottom: rescaled UVs increases texture &#8216;density&#8217;, how much image is dedicated to a given face, which can improve image clarity.<\/i><\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":5004,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[34,230],"tags":[719,649,833,829,655,651,652,648,830,635,815,647],"class_list":["post-2597","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blender","category-tutorials","tag-datablocks","tag-mark-seams","tag-texture-density","tag-unwrap","tag-uv-editing","tag-uv-editing-workspace","tag-uv-editor","tag-uv-maps","tag-uv-sync-select","tag-uv-unwrapping","tag-uvmap","tag-uvs"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/posts\/2597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/comments?post=2597"}],"version-history":[{"count":101,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/posts\/2597\/revisions"}],"predecessor-version":[{"id":5387,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/posts\/2597\/revisions\/5387"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/media\/5004"}],"wp:attachment":[{"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/media?parent=2597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/categories?post=2597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.katsbits.com\/codex\/wp-json\/wp\/v2\/tags?post=2597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}