Hello. I’m trying to launch Flame on a mac via the command name and by passing the project settings page by specifying the user and project as it describes in the docs.
https://help.autodesk.com/view/FLAME/2024/ENU/?guid=Flame_API_Python_Hooks_Reference_Python_Hooks_Tips_html
However I’ve tried every combination and the project settings page still appears:
/opt/Autodesk/.flamefamily_2024.2.2/bin/flame.app/Contents/MacOS/flame -J --start-project=the_project_name -U --start-user=my_user_name
/opt/Autodesk/.flamefamily_2024.2.2/bin/flame.app/Contents/MacOS/flame -J the_project_name -U my_user_name
/opt/Autodesk/.flamefamily_2024.2.2/bin/flame.app/Contents/MacOS/flame --start-project=the_project_name --start-user=my_user_name
Is there anything I am doing wrong? Many thanks in advance.
Thanks
Steve
To see what your options are, I’d try:
/opt/Autodesk/flame_2024.2/bin/./startApplication --help
or:
/opt/Autodesk/flame_2024.2/bin/./startApplication --start-project=PROJECT --start-workspace=WORKSPACE
Specifying a user probably won’t work anymore:
--start-user=STRING Deprecated argument, no longer used
ytf
November 13, 2024, 10:48pm
3
I’m not sure the project settings page is bypassed. For instance, if I want to start the application with the project named LostPlanet and the user to be ytf, the exact command line would be
/opt/Autodesk/flame_2024.2.1/bin/startApplication -J LostPlanet -U ytf
This sets the project settings page to the proper project and user, but I still need to hit the Start button.
I think if you specify a workspace with -W=WORKSPACE or --start-workspace=WORKSPACE it will bypass that screen.
philm
November 14, 2024, 1:15am
5
Here’s one of the automatically generated launchers for LOGIK-PROJEKT - it works with flame 2025+
/opt/Autodesk/flame_2025.2.1/bin/startFlame \
-J 1010_abc_def_2025_2_1_delta \
--start-workspace="delta" --create-workspace \
create_projekt_layout.py
3 Likes
Thank you all for the suggestions. I found this works and bypasses the project settings screen which is what I wanted. This is the syntax I used:
/opt/Autodesk/.flamefamily_2024.2.2/bin/flame.app/Contents/MacOS/startApp --start-project=my_new_project --start-user=steveo --start-workspace="Workspace"
Thanks very much.
Steve
3 Likes
kily
November 14, 2024, 4:07pm
7
I tested right know and it works!!. First time I can bypass the start button in selection project window, and I have been trying for a long time.
Note: For 2025, the flag start user is not needed.
1 Like
ytf
November 14, 2024, 4:53pm
8
I know there are a lot of folks who know a lot more about this than I, but I thought that starting flame with /flame instead of /startApplication left some services off.
1 Like
Quinn
November 14, 2024, 8:43pm
9
To aid in all of this I typically set an alias in my shell to start flame.
put this in your .zshrc file
alias flame=‘/opt/Autodesk/flame_2025.2.1/bin/./startApplication’;
kily
November 14, 2024, 10:02pm
10
To clarify, I used ./startApplication (I’m on linux)
ytf
November 14, 2024, 10:08pm
11
and not meaning to nitpick, but I don’t think you need the ./ since you are already specifying the path.
2 Likes
Quinn
November 19, 2024, 8:54pm
12
I didn’t realize that. i’ve been using the same basic alias for years
philm
November 19, 2024, 9:00pm
13
"Hey Siri, start flame..."
"I'm sorry, would you like me to search the internet for flame?"
The ‘.’ stands for ‘start path at current folder’. It’s the companion to ‘/’ which says ‘start path at root’. You use one or the other.
So you do need to use the ‘.’ if you just type ./StartApplication and this folder you’re in is not part of the $PATH environment variable.