This has advantages inside SketchUp but not necessarily in other contexts or 3D applications where this structure represents a lot of duplication and waste Double-sided meshes ^ĭouble-sided meshes then are an issue and need to be cleaned before a model can be used in game.
#Sketchup textures not exporting with obj windows
The windows shown above all reference the same texture, but each pane is exported from SketchUp as a separate Object assigned a separate material. SketchUp doesn't collapse objects into larger units in any meaningful way even if they may have a common element between them. And as each of these is a completely separate object, the net result of all this duplication is that SketchUp imports can contain hundreds of mesh items where one or two might otherwise have sufficed.ĭesign note: overall most issues attributed to cleaning up imported SketchUp models relate to this fixing or addressing the over-duplication of mesh data. Whilst this duplication may not be an issue in its own right, if the Window has thickness - it's not just a single planar surface - this can mean SketchUp has actually drawn four or more surfaces - an outer and inner surface for each 'front' and 'back' plane. In addition to this, for SketchUp to texture both sides of each window it has to duplicate and invert the mesh, creating a 'front' and 'back' (or 'inner' and 'outer' surface) that, alongside individualised Material assignments, can then be textured independently if required - double-sided in other words. In other words five distinct and separate Materials referencing the same Texture/Image data. Shown below for example is a section of a SketchUp building after import into Blender although all five window sections are UV mapped using same bitmap image (a glass block - not transparent), each has its own individual Material reference. And whilst SketchUp does provide a number of export options they don't necessarily address this issue of over duplication directly (as it relates to game content), so content often needs to be further edited and optimised in more meaningful ways in Blender or other applications. Whilst this allows for both the inner and outer surfaces of a given mesh element to be textured with relative ease and independently of each other, it tends to be problematic outside the SketchUp environment because the applications is essentially generating too much mesh data for models to be used in game 'as is' - using SketchUp content directly would mean game engines rendering a lot of redundant material unnecessarily, largely because its hidden from view. Redundant duplication ^Īs briefly mentioned in the introduction, SketchUp models are constructed using a lot of duplication duplicate surfaces, duplicate materials, textures, UV maps and so on.
The following highlights and discusses some of the 'extras, options and issues' that might occur, or there needs to be an awareness of, when importing into and/or editing SketchUp models in Blender.
0 kommentar(er)
