We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Ok, I Agree

GLTF and USDZ exporters issue with AO map

Home › Forums › Bug Reports and Feature Requests › GLTF and USDZ exporters issue with AO map

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • 2022-10-03 at 1:51 pm #56347
    kdv
    Participant

    Verge3D plugin for Blender ignores texture scaling and cannot export AO map for “glTF 2.0 compatible” material. But it’s possible via the built-in “glTF 2.0” exporter. And it works good. Materials look exactly like MeshNodeMaterial. Combined with the compressed geometry a mesh can be loaded really fast https://v3d.net/bec

    But when exported to GLTF via puzzles it looks a little different )))

    Nearly the same story with the USDZ exporter. Looks a little more funny )))

    Any chance that these exporters will be fixed to apply AO map properly?

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

    2022-10-04 at 6:48 am #56359
    Yuri Kovelenov
    Staff

    we’ll take a look! :good:

    Chief 3D Verger | LinkedIn | Twitter

    2022-10-04 at 6:14 pm #56365
    kdv
    Participant

    Looks like the only way for now is using textures without tiling
    https://github.com/mrdoob/three.js/issues/21906
    The AO map is always tiled as the diffuse map in the Quick Look…

    One more way is creating a tiled canvas before exporting to USDZ. But it encreases the file size significantly.

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.