I've Posted on the Poser Python Scripting as well. Looking for a quick response, because I need it urgently. I recently uninstalled & reinstalled my Poser Pro 2014. Everything was working fine until I noticed that the 'PoseWriter Panel' under the Scripts menu is not working. Funny thing is everything is right there, and when I create a pose with a figure, and save the pose using PoseWriter it even says the Pose is 'written and ready' and also indicating where it is saved. Unfortunately nothing is saved. However I do get an error code, every time I close Poser after attempting to pose a figure through PoseWriter Panel. I'm not very familiar with Scripts and their error code. I really need to get this fixed as this posing script is what I rely on posing my figures with efficiency and ease. Below is a screenshot of the error code I get when I close Poser application:

Thanks,

Your screenshot didn't show up. Having never used PoseWriter, what is the advantage? By the name, it sounds like it saves poses, but you can do that with the library, so I'm assuming there's more to it.

Try running poser as admin. May not have security rights to actually write out the pose file.

Did you install all the available SR's for PP2014? Where are you saving the poses?

@ RedPhantom: Netherworks PoseWriter is supposed to be the better way to save poses, at least that is what is recommended for SASHA-16. Simply adding poses directly to the Library ignores any ERC or JCM induced values, it just saves the local values of the joints.

Does anyone know how to change where the Poses are saved using Pose Writer?

In his other scripts you right click on the destination then browse to where you want to save.

Thank you Sunfire! Got it! :)

You're welcome.

RedPhantom posted at 7:16PM Sat, 29 May 2021 - #4419079

Your screenshot didn't show up. Having never used PoseWriter, what is the advantage? By the name, it sounds like it saves poses, but you can do that with the library, so I'm assuming there's more to it.

Sorry for the late response. Somehow I didn't get the notifications for the forum. Thought I had it on. Advantages of this Pose script are so many. Unlike the general pose application, this applies pose to the whole figure, the hands included. Also other various options you can't get from the general pose creator like, applying pose to props from its scale and all.

Below is the screenshot is the screenshot I missed. But I actually have a new error message now when trying to apply the pose using that script. So I'm just gonna post both screenshots now. Thanks

bwldrd posted at 7:25PM Sat, 29 May 2021 - #4419080

Try running poser as admin. May not have security rights to actually write out the pose file.

That was never the issue. But just tried that to be certain. Still get the same new error message I just mentioned on this forum. Poser crashes now when I try to apply a pose using the script. Is there anyway to reinstall it. I tried looking for the script separately. But it doesn't appear to be available as a standalone script anymore. Once again I'll post a screenshot of the error message. I really need to fix this. Thanks.

Perhaps I need to uninstall Poser Pro by removing all contents from the system, and then reinstall for the script to work again. Just to be clear I did not remove all Poser contents from system when I uninstalled before as mentioned on post. I'm guessing these script files remain as saved content, like the poser content library, although they are not saved in the same directory. I feel like there's an easy way to resolve this, without having to do all this. Thanks

Make sure you have all the updates to your poser installed as well.

Sunfire posted at 5:05PM Mon, 31 May 2021 - #4420189

Make sure you have all the updates to your poser installed as well.

Thanks. Will do. I got the Service release pack 3. Which is the latest update for PP2014 as far as I know.

Thanks everyone for tall he help and input. Looks like the best way to fix the error is to uninstall and completely remove all poser content from my system before reinstalling it. Also as suggested in Python scripts forum help.

Cheers.