No worries at all @knhn, and if I remember correctly I originally got it from @lewis or @ManChicken, or someone else, sorry I forgot 
thanks @john-geehreng and @knhn . All fixed. Yesterday was not one of my best days. Update to 2025 was a big headtache 
1 Like
Hey @taylaner, that one is definitely on my list of things to get done. I’ll let you know as soon as I have a new version ready.
3 Likes
Hi
I’m new to python hooks.
my biggest problem is my IT dept.
I work for Warner Bros.
The idea of having my Flame connected to an outside server is a non starter.
Is there a way to download the Python scripts and install them in a secure location on my server?
many thanks in advance.
Hi @Rhiltzik
go to the Logik Portal and look for a link to the DropBox download page. it’s near the bottom of the page.
1 Like
@MikeV Thanks for all your work on the Portal.
We’ve just upgraded to 2025 (from 2024) and I’m trying to make use of the new Centralised Components features, so amongst other things python scripts are stored at a shared network location and not at /opt/Autodesk/shared/python.
Is this possible and still use the Logik Portal?
I’ve downloaded the latest v6.2.0 and have tried two things:
- keep it in a containing “logik_portal_v6.2.0” folder and copy it to network location of other python scripts. Here it errors and tells me to re-install at /opt/Autodesk/shared/python/logik-portal
- remove it from containing “logik_portal_v6.2.0” folder (which I thought was the right thing to do, irrespective of the copy destination) and copy it to network location of other python scripts. Now it doesn’t appear in the Flame menu at all (but Flame can still see other python scripts at this location)
Afaik it’s not posssible to point the sysconfig.cfg for Centralised Components to two locations… so does this mean to see Logik Portal we need to keep all our python scripts with it locally as pre-2025?
Thanks
@cicero - if you point the centralized cfg to /opt/Autodesk/shared/python do things work?
this directory almost certainly gets created or re-used when flame is installed.
if you need the same scripts to be installed on every machine it’s only a couple of minutes to deploy that across a network.
otherwise mike has to rewrite all of his scripts to path to your special paths,
the path to some of his scripts is in the first few lines at the top of each script:
e.g.
# ---------------------------------------- #
# Main Script
SCRIPT_NAME = 'My Special Script'
SCRIPT_PATH = '/opt/Autodesk/shared/python/logik_python/Scripts/my_special_script'
VERSION = 'v2.0'
Yes they do, thanks.
I guess I was just asking for a sanity check, that having access to Portal means all python scripts need to stick with that sript locally, and can’t be centralised. That’s fine now that I know.
Hey @cicero
I haven’t had a chance to adapt the portal to work with the Centralized workflow yet. One thing you could try if you want to keep all the scripts in one location is to create a symlinked folder of the shared network folder where you want to keep all the scripts and then replace the /opt/Autodesk/shared/python folder with that symlinked folder.
Mike
1 Like
Thanks Mike! And thanks for all you’re doing!
4 Likes
i guess this isnt planned at all? I was trying to make a centralized config for our studio to unify everything finally but i get the same error of course
I never quite understood why the script location was hardcoded but I’m sure there’s a good reason. Any script I’ve taken from the portal to use for us I’ve gone and changed the path manually as we have a centralized config.
For our own hooks we use the built-in method to get the location to then do whatever else we need it for.
script_path = os.path.abspath(os.path.dirname(__file__))
3 Likes
I’ve updated most of my scripts on the Logik Portal to use this now instead of having the path hard coded into the scripts. So they should be much more flexible now on where they can be installed to. For the Logik Portal I’m working on adding the ability to select where the scripts get installed too.
Mike
11 Likes
I just put out an updated version of the Logik Portal that will let you select the path where scripts get installed to. By default this is set to: /opt/Autodesk/shared/python. When changing this path, just make sure the path that gets set is a path Flame will be looking for the scripts in.
Mike
6 Likes
Just to say @MikeV, I just got round to updating our scripts and the Portal itself to a centralised location, which is going to help a lot with managing multiple suites etc.
All working well so far… Thanks again for the update, and for all your work!
2 Likes