Decouple Albedo and SketchUp texture

Please cast your votes in our two ongoing feedback polls here and here!
  • When we select an image file as the Albedo map in the Enscape Material Editor, it overwrites the texture in the SketchUp material. And vice-versa, when we select an image file as a texture in a SketchUp material, it overwrites the Albedo map in the Enscape material.


    Is it possible to decouple the two? The use case would be to use a low-resolution image in SketchUp, while having its high-resolution counterpart in Enscape. Storing high-resolution images in the SketchUp file can quickly make it several hundreds megabytes.


    I think I remember that it was possible in previous version. That when we chose an image file in Enscape, it was decoupled from the SketchUp material texture.

    It is also possible in V-Ray by disabled "Bind".


    We actually want to do this via attributes by using <Source>TEXTURE_PATH_ABSOLUTE</Source> and specifying the path, but it doesn't seem to have any effect anymore.

  • jiminy-billy-bob Could this be why I have a weird texture bug with transmuted objects used with Enscape? I regularly pull in Transmuted objects and when editing them in Enscape it changes the texture sizing in SketchUp. So if I have a 10"x10" texture in SketchUp, then edit that texture in any way in the Enscape texture editor, the SketchUp texture changes to 3'ish, and I have to go back and assign a new texture size in SketchUp. I'm not sure if it's related, but thought it sounded familiar.

  • Ted.Vitale - Sorry I was commenting on the original two posts. I was just curious what they considered high resolution since Enscape tends to downsample things anyway.


    For texture scaling issues between Tranmutr/Enscape/Skp, I wouldn't be surprised if there is some mis-translation going on between meters and imperial units.

  • I’m positive that’s the case and it’s an imperial to metric issue. But Enscape shouldn’t effect the SketchUp texture properties. I thought maybe it might be related to this post since there was some over writing on SketchUp because I see this issue regularly.

  • jiminy-billy-bob Could this be why I have a weird texture bug with transmuted objects used with Enscape? I regularly pull in Transmuted objects and when editing them in Enscape it changes the texture sizing in SketchUp. So if I have a 10"x10" texture in SketchUp, then edit that texture in any way in the Enscape texture editor, the SketchUp texture changes to 3'ish, and I have to go back and assign a new texture size in SketchUp. I'm not sure if it's related, but thought it sounded familiar.

    I thought we fixed this issue by enabling "Explicit Texture Transformation" by default? Can you confirm this happens with the latest version of Transmutr?

  • What resolution textures are you wanting to use?

    Add a decent number of high res textures, especially PNG formats and the SU file size can really balloon to where it starts affecting read/write times and navigation. Like JBB says, better to keep textures in SU under 1k as placeholders, and preferably as lossy jpegs.

  • A great idea. I always try to make texture size down well below 1mb because SKP file size will be unmanageable very quickly otherwise.

  • Add a decent number of high res textures, especially PNG formats and the SU file size can really balloon to where it starts affecting read/write times and navigation. Like JBB says, better to keep textures in SU under 1k as placeholders, and preferably as lossy jpegs.

    Understood, I typically do 2k .jpg with a bit of compression, to balance between lossy and having "enough" quality. But also keep .psd backups. 95% of our use is churning out process renderings though, we usually aren't trying to squeeze out every last ounce of quality. Skp has the "use max texture size" option, with that unchecked everything gets downsampled to 1k for display purposes, so I'm not sure "placeholders" would make much difference in navigation. Though I'm sure we all have different expectations for what constitutes a lot of textures/large file.


    At any rate, some overhauled link management from Enscape would be welcome.