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.

darknoodles

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • darknoodles
    Participant

    My setup is as follow:

      [*]Blender[/*]

      [*]AddonsAssets[/*][*]Blender 2.8x[/*][*]Blender Linux 2.8x[/*][*]Scripts[/*]

        [*]addons[/*][*]modules[/*][*]presets[/*][*]startup[/*][/list][/list]

        This way i can have fully portable Blender, even several OS version using the same addon folder (the Scripts folder is like the one that is in the Blender installation). No need to duplicate addons accross Blenders
        Blender File Path Docs

        I see no reason why to use this path specifically for Verge. Even the fact there are executables inside. UV Packmaster, Quadremesher and others have executables too, and still don’t use this folder, and even let you choose the path to it.

        Edit: Will reformat the list later

        in reply to: Missing pluginUtils.py in addon #27829
        darknoodles
        Participant

        MMhhh weird, my version of the addon is 3.1.1. I downloaded the Verge3d package 2 days ago…
        I tried copying the content of the ‘python’ folder from the verge3d folder into the ‘modules’ folder of blender, it solved some issues but raised others when trying to use the ‘future’ module.

        The issue with the guide is that it forces the user to define a specific scripts path, and i already have one, because i made my Blender fully portable.
        So all my addons are in this path. To be honest this is the first time i see an addon requiring to define the script path especially for itself.

      Viewing 2 posts - 1 through 2 (of 2 total)