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.

export gltf error

Home Forums General Questions export gltf error

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #38648

    hi i get this error now when exporting to gltf in the app folder, no error if i export into a empty folder, i have the verge directory on a google file stream virtual drive, any clues?

    Python: Traceback (most recent call last):
    File “C:\Users\michael grebstad\AppData\Roaming\Blender Foundation\Blender\2.91\scripts\addons\verge3d\__init__.py”, line 138, in execute
    return gltf2_export.save(self, context, exportSettings)
    File “C:\Users\michael grebstad\AppData\Roaming\Blender Foundation\Blender\2.91\scripts\addons\verge3d\gltf2_export.py”, line 96, in save
    generateGLTF(operator, context, exportSettings, glTF)
    File “C:\Users\michael grebstad\AppData\Roaming\Blender Foundation\Blender\2.91\scripts\addons\verge3d\gltf2_generate.py”, line 3158, in generateGLTF
    generateImages(operator, context, exportSettings, glTF)
    File “C:\Users\michael grebstad\AppData\Roaming\Blender Foundation\Blender\2.91\scripts\addons\verge3d\gltf2_generate.py”, line 2423, in generateImages
    shutil.copyfile(old_path, new_path)
    File “C:\Program Files\Blender Foundation\Blender 2.91\2.91\python\lib\shutil.py”, line 104, in copyfile
    raise SameFileError(“{!r} and {!r} are the same file”.format(src, dst))
    shutil.SameFileError: ‘G:\\Min disk\\Workspace\\Assets\\Textures\\wood\\TexturesCom_PlywoodNew0050_1_seamless_S.jpg’ and ‘G:\\Min disk\\Workspace\\Verge3D\\verge3d_blender\\applications\\insulation\\TexturesCom_PlywoodNew0050_1_seamless_S.jpg’ are the same file

    location: <unknown location>:-1

    #38649

    ive narrowed it down a bit, if i export to a local drive i get no error, if i export to the google file stream virtual drive i get error no matter where on the drive i do it, so obviously something to do with the virtual drive, i also tested if the file system was the culprit since the google drive was a fat32 system, so i tried exporting to a usb drive with fat32, but that worked,

    #38657

    thanks for reporting this. We’ll check it out

    Chief 3D Verger | LinkedIn | Twitter

    #38659

    Hi,
    this is a known Python bug. We need to wait here until the fix will be available.

    Soft8Soft Tech Chief
    X | FB | LinkedIn

    #38675

    thanks for responding, may this be fixed within a year or so? i think the new google drive windows software will move away from the virtual drive solution and be more like a one drive approach, with just a folder structure, would be nice to have it working on virtual drives anyway,

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