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.

GLTF export not fully compatible with Verge3D

Home Forums General Questions GLTF export not fully compatible with Verge3D

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #85693
    martenmonoz
    Customer

    Hi everyone,

    When I export my scene using the “Export to glTF” puzzle and then try to import the resulting .gltf file, I get the following warning:

    “The glTF asset was exported from [unknown]. It may not be fully compatible with Verge3D for Blender.”

    And also this error:

    “Error: v3d.GLTFLoader: Unable to parse model. at Object.onLoad”

    However, when I open the same .gltf file in an online glTF viewer, it loads without any issues.

    Has anyone encountered this before or knows what might be causing this?

    #85694
    visualizer
    Customer

    Does it get imported well in Blender?

    #85695
    martenmonoz
    Customer

    Yes, blender import looks the same as the viewer.

    #85701

    Hi,
    This appears to be a new bug introduced in Verge3D 4.11. Honestly, we never tested such setup. We’ll fix that for the next Verge3D update!

    Soft8Soft Tech Chief
    Want more Verge3D updates? Follow me on X, Facebook, or LinkedIn

    #85704
    martenmonoz
    Customer

    Hi Alexander,

    Thank you for your response. The reason we want to use the export-and-import method is that we have several relatively large apps (with many puzzles) for configuring different pieces of furniture. When configuring a new product, we want to display the previously configured product as well.

    Do you think this is a reasonable solution to keep all the apps manageable, or is there a better way to link and combine them?

    #85707

    I believe that if the previous configuration is not required to be stored in glTF format on user devices (or a web server) it’s better to just deep-clone the entire object hierarchy of the configurable product and move it somewhere (maybe to the background etc.). If the metadata is what actually should be saved, then I’d suggest making a puzzles-friendly dictionary with object configuration (which can be applied to the actual 3D object at any time).

    Soft8Soft Tech Chief
    Want more Verge3D updates? Follow me on X, Facebook, or LinkedIn

    #86011
    martenmonoz
    Customer

    Hi Alexander,

    I think I found the problem/solution with the imcompatibel .gtlf. The file starts with {"asset":{"version":"2.0","generator":"Verge3D"}, If I remove the number form Verge3D like:{"asset":{"version":"2.0","generator":"VergeD"}, the file is imported just fine :)

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