Is there a way to add scripts to the menu permanently? It's a pain to constantly have to load scripts that I use all the time, like EZSkin3, and such. I want to add them to the script menu and keep them there.

Thanks!

(NOTE: I use a Mac, so the process may or may not be the same on Windows.)

Open the Poser 11 APPLICATION's folder. In its Runtime folder, locate the Python folder. In the Python folder, locate the poserScripts folder, and within that, the ScriptsMenu folder. Drag the script file you want to add into the ScriptsMenu folder (e.g., for EZSkin3, that would be the EZSkin3.pyc file). Quit and relaunch Poser, and the new script should be available in Poser's Scripts menu. Click to run it.

BTW, when I add a new script, I copy the entire Python folder to another location on my drive, since reinstalling Poser could overwrite the application's Runtime, and thus the Python folder within it, with a fresh version that wouldn't contain the scripts I've added. The copy can then be dragged into Poser's Runtime and my added scripts will be included again. Also, be aware that Poser 11 uses Python 2, but Poser 12 replaced that with Python 3, so Poser 11 scripts that haven't been upgraded won't work in Poser 12 (a main reason I'm sticking with Poser 11).

Hope this helps.

BTW, when I add a new script, I copy the entire Python folder to another location on my drive, since reinstalling Poser could overwrite the application's Runtime, and thus the Python folder within it, with a fresh version that wouldn't contain the scripts I've added. The copy can then be dragged into Poser's Runtime and my added scripts will be included again. Also, be aware that Poser 11 uses Python 2, but Poser 12 replaced that with Python 3, so Poser 11 scripts that haven't been upgraded won't work in Poser 12 (a main reason I'm sticking with Poser 11).

Hope this helps.

That is not true in Windows.  A Poser reinstall over an existing installation will only replace those files associated with the application.  Anything else manually installed, such as 3rd party Python Scripts, are relatively safe.

You can add folders to the scripts menu folder for favorite creators like snarly.  

The Poser installer does not remove files you've added to the Poser program folder or any content beyond the basic content that is installed with Poser. But, a re-installation will over write the python buttons scripts with the original ones. If you manually add some buttons to the python buttons by editing that file, write protect the file. The next time you update Poser it will ask if you want to skip the file. And, you do. There are a couple of bits of standard content that I keep modified this way as well.

(NOTE: I use a Mac, so the process may or may not be the same on Windows.)

Open the Poser 11 APPLICATION's folder. In its Runtime folder, locate the Python folder. In the Python folder, locate the poserScripts folder, and within that, the ScriptsMenu folder. Drag the script file you want to add into the ScriptsMenu folder (e.g., for EZSkin3, that would be the EZSkin3.pyc file). Quit and relaunch Poser, and the new script should be available in Poser's Scripts menu. Click to run it.

BTW, when I add a new script, I copy the entire Python folder to another location on my drive, since reinstalling Poser could overwrite the application's Runtime, and thus the Python folder within it, with a fresh version that wouldn't contain the scripts I've added. The copy can then be dragged into Poser's Runtime and my added scripts will be included again. Also, be aware that Poser 11 uses Python 2, but Poser 12 replaced that with Python 3, so Poser 11 scripts that haven't been upgraded won't work in Poser 12 (a main reason I'm sticking with Poser 11).

Hope this helps.

So what's the difference between a .py file and a .pyc?

PYC is compiled.

Runtime>Python>poserScripts>ScriptsMenu is Correct.  As Boni commented, you can create a separate folder to contain a specific script.  You must be in the Application Runtime folder, not the Poser Content.  And it would be best if you relaunched Poser for the script to appear in the contextual menu.

I copied the PYC file into the folder as you stated. I then started Poser, and it wasn't there.

I will attempt it with a folder. Maybe that will help

@hborre and nerd: Thanks! You're probably right that a reinstall would not overwrite my manually installed scripts, even on Mac. I just back up the Python folder when I add scripts because I'm overcautious. And yes, I did edit the Python pallet buttons to add my own. I figure it's just easiest to drag the backed up copy of the whole Python folder into the application runtime if anything goes wrong.

Happy New Year!

So here are the screen captures. Let me know if I did something wrong:

I added the PYC to the folder as directed. I restarted Poser, and it's not showing. And whatever was in the top button isn't there any longer.

Help!

The initial post gave the impression that you wanted it to appear in the Scripts menu. Does it appear there?

The Scripts menu is in the menu bar at the top. It appears you want it to appear in the Python Scripts Palette. I will have to hunt down how to do that, as I am not a python guru. Maybe someone else can pipe in to help.

Yes in comparing the two in Poser 12, it does appear they are independent of each other. The items that I show in the Python Scripts palette do not match up with those in the Scripts menu. Will dig into this some more

It looks like the Python Scripts palette has a little blurb on the bottom to click an empty button (the one with the dots on it) and to choose the script you want to fill in there. But then there are also custom palettes, such as the one that used to be furnished with Wardrobe Wizard, that have an entire palette all to itself. That's the part I am not sure how to do.

If you need an alternative option, the paid "XA - Toolbar for Poser" is still available at Renderosity. Works fine in Poser 11, though like many script utilities it may need the AVfix hot-fix. XA Toolbar can launch along with Poser 11. You can pin scripts to its buttons, among other things. And give each button a custom icon. Then you launch the script with one click on the button.

To add more pallets, you need to edit the mainButtons.py file in a text editor (don't use Word). Lines 8 and 9 load 2 new pallets called custombuttons.py and custom2.py respectively. Those pallets are set up in the same format. I think I just made copies of the mainbuttons.py and edited them. You can find the mainbuttons.py in Runtime\Python\poserScripts under the folder where Poser is installed (as opposed to your content runtime).

import poser

poser.DefineScriptButton(1,  ":Runtime:Python:poserScripts:PythonPalette:geomModButtons.py", "Geom Mods")
poser.DefineScriptButton(2,  ":Runtime:Python:poserScripts:PythonPalette:utilityButtons.py", "Utility Funcs")
poser.DefineScriptButton(3,  ":Runtime:Python:poserScripts:PythonPalette:callbackButtons.py", "Sample Callbacks")
poser.DefineScriptButton(4,  ":Runtime:Python:poserScripts:PythonPalette:renderButtons.py", "Render / IO")
poser.DefineScriptButton(5,  ":Runtime:Python:poserScripts:PythonPalette:materialModButtons.py", "Material Mods")
poser.DefineScriptButton(6,  ":Runtime:Python:poserScripts:PythonPalette:printInfoButtons.py", "Print Info")
poser.DefineScriptButton(7,  ":Runtime:Python:poserScripts:PythonPalette:propButtons.py", "Prop Samples")
poser.DefineScriptButton(8,  ":Runtime:Python:poserScripts:custombuttons.py", "Custom")
poser.DefineScriptButton(9,  ":Runtime:Python:poserScripts:custom2.py", "More")
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

Well, then. Looks like I have some work to do.

Thanks all for the replies. I am going to check this out. On a copy of the script. I don't want to botch things up.

To add more pallets, you need to edit the mainButtons.py file in a text editor (don't use Word). Lines 8 and 9 load 2 new pallets called custombuttons.py and custom2.py respectively. Those pallets are set up in the same format. I think I just made copies of the mainbuttons.py and edited them. You can find the mainbuttons.py in Runtime\Python\poserScripts under the folder where Poser is installed (as opposed to your content runtime).

import poser

poser.DefineScriptButton(1,  ":Runtime:Python:poserScripts:PythonPalette:geomModButtons.py", "Geom Mods")
poser.DefineScriptButton(2,  ":Runtime:Python:poserScripts:PythonPalette:utilityButtons.py", "Utility Funcs")
poser.DefineScriptButton(3,  ":Runtime:Python:poserScripts:PythonPalette:callbackButtons.py", "Sample Callbacks")
poser.DefineScriptButton(4,  ":Runtime:Python:poserScripts:PythonPalette:renderButtons.py", "Render / IO")
poser.DefineScriptButton(5,  ":Runtime:Python:poserScripts:PythonPalette:materialModButtons.py", "Material Mods")
poser.DefineScriptButton(6,  ":Runtime:Python:poserScripts:PythonPalette:printInfoButtons.py", "Print Info")
poser.DefineScriptButton(7,  ":Runtime:Python:poserScripts:PythonPalette:propButtons.py", "Prop Samples")
poser.DefineScriptButton(8,  ":Runtime:Python:poserScripts:custombuttons.py", "Custom")
poser.DefineScriptButton(9,  ":Runtime:Python:poserScripts:custom2.py", "More")
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

I was hoping a python guru would come to the rescue. Thanks RedPhantom!

RedPhantom posted at 12:33 PM Sun, 1 January 2023 - #4452855

To add more pallets, you need to edit the mainButtons.py file in a text editor (don't use Word). Lines 8 and 9 load 2 new pallets called custombuttons.py and custom2.py respectively. Those pallets are set up in the same format. I think I just made copies of the mainbuttons.py and edited them. You can find the mainbuttons.py in Runtime\Python\poserScripts under the folder where Poser is installed (as opposed to your content runtime).

import poser

poser.DefineScriptButton(1,  ":Runtime:Python:poserScripts:PythonPalette:geomModButtons.py", "Geom Mods")
poser.DefineScriptButton(2,  ":Runtime:Python:poserScripts:PythonPalette:utilityButtons.py", "Utility Funcs")
poser.DefineScriptButton(3,  ":Runtime:Python:poserScripts:PythonPalette:callbackButtons.py", "Sample Callbacks")
poser.DefineScriptButton(4,  ":Runtime:Python:poserScripts:PythonPalette:renderButtons.py", "Render / IO")
poser.DefineScriptButton(5,  ":Runtime:Python:poserScripts:PythonPalette:materialModButtons.py", "Material Mods")
poser.DefineScriptButton(6,  ":Runtime:Python:poserScripts:PythonPalette:printInfoButtons.py", "Print Info")
poser.DefineScriptButton(7,  ":Runtime:Python:poserScripts:PythonPalette:propButtons.py", "Prop Samples")
poser.DefineScriptButton(8,  ":Runtime:Python:poserScripts:custombuttons.py", "Custom")
poser.DefineScriptButton(9,  ":Runtime:Python:poserScripts:custom2.py", "More")
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

So if I add the buttons to include the EZSkin3 PYC, do I need it to be in the scripts menu folder, or just in the poserScripts folder?

I was hoping a python guru would come to the rescue. Thanks RedPhantom!

HAHAHA well you are better off than I am. At my age (don't ask) I look at anything that resembles any kind of code and my eyes glaze over. LOL

BTW, in P12 Bastep has a Scriptstarter Python Script that conveniently competes with Poser's native panel.  It might be a good replacement If you want to update to that feature.

rokket posted at 12:48 PM Sun, 1 January 2023 - #4452858

RedPhantom posted at 12:33 PM Sun, 1 January 2023 - #4452855

To add more pallets, you need to edit the mainButtons.py file in a text editor (don't use Word). Lines 8 and 9 load 2 new pallets called custombuttons.py and custom2.py respectively. Those pallets are set up in the same format. I think I just made copies of the mainbuttons.py and edited them. You can find the mainbuttons.py in Runtime\Python\poserScripts under the folder where Poser is installed (as opposed to your content runtime).

import poser

poser.DefineScriptButton(1,  ":Runtime:Python:poserScripts:PythonPalette:geomModButtons.py", "Geom Mods")
poser.DefineScriptButton(2,  ":Runtime:Python:poserScripts:PythonPalette:utilityButtons.py", "Utility Funcs")
poser.DefineScriptButton(3,  ":Runtime:Python:poserScripts:PythonPalette:callbackButtons.py", "Sample Callbacks")
poser.DefineScriptButton(4,  ":Runtime:Python:poserScripts:PythonPalette:renderButtons.py", "Render / IO")
poser.DefineScriptButton(5,  ":Runtime:Python:poserScripts:PythonPalette:materialModButtons.py", "Material Mods")
poser.DefineScriptButton(6,  ":Runtime:Python:poserScripts:PythonPalette:printInfoButtons.py", "Print Info")
poser.DefineScriptButton(7,  ":Runtime:Python:poserScripts:PythonPalette:propButtons.py", "Prop Samples")
poser.DefineScriptButton(8,  ":Runtime:Python:poserScripts:custombuttons.py", "Custom")
poser.DefineScriptButton(9,  ":Runtime:Python:poserScripts:custom2.py", "More")
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

So if I add the buttons to include the EZSkin3 PYC, do I need it to be in the scripts menu folder, or just in the poserScripts folder?

You shouldn't need to move it. Just make sure the path is correct.

That worked, thank you so much RedPhantom!

I am going to add the ezdome in there now, too. I don't use the construct, but I want to be able to add the dome from time to time.

LaFemme is a little shy...

Now I am happy. I got what I wanted. Thanks again for all the help. This forum is invaluable.