Hi,

 Before I pull the trigger and go with Poser 13, I would like to get answers to the following questions (high level would be just fine):

1- Is the data structure between Poser 11 and 13 the same (e.g. libraries, geometries, characters, etc.)?

2- Does Poser 13 allow running python scripts that can be run in Poser 11?

3- I exclusively use V4, M4 characters (due to being native in Poser 11). Any issues with using these characters in Poser 13?

- Given positive answers to items 1, 2 and 3......what are the three best reasons to switch to Poser 13.

Thank you all,

vxg

To answer your questions....

1. Yes

2. Eh... some scripts work some don't, there's been a lot of changes to the python version.

3. The only issue is the fact that they don't have native superfly materials, but other than that they work fine in 13.

3 Best reasons to switch:

1. Faster and better Superfly. Improved Cycles base means improved PBR renders.

2. Newer python means better scripts. Ken1171_Designs has many scripts that work in Poser 12 and 13 but can't work in P11. He also has a script for P13, that makes using HDRI easier.

3. A free trial period where you can try it first.

Most importantly, content creators won't always continue to support P11.

Sunfire

I am sold! Just to confirm that I should be able to read Poser 11 files into Poser 13 (given that I would copy all the necessary purchased contents into relevant Poser 13 libraries?

Cheers,

vxg

Yes, you should be able to read all your content and scenes, assuming you don't need a script to load it. I don't have much that needs scripts, so I don't know what that would be.

If you have external runtimes, just link them to Poser 13.

hborre posted at 7:52 PM Sat, 2 August 2025 - #4498458

If you have external runtimes, just link them to Poser 13.

Can you get me a link that shows how to link external runtime directory? I was planning to migrate my external runtime content into Poser 13 runtime...

Cheers,

vxg

Just click on tbe add library button in the P13 library window and navigate to the folder ABOVE the Runtime folder. 

The Poser 13 manual explains it.

https://www.posersoftware.com/documentation/13/HTML/index.htm#t=Poser_Reference_Manual%2FBuildingScenes%2FLibrary%2FAdding_Libraries.htm&rhsearch=Libraries&rhhlterm=libraries%20library

And if you're using SnarlyGribbly's EZDome, EZSkin and/or SceneFixer, I have updated those to be used with Poser13+. 
Don't hesitate to ask if you encounter something weird or wrong.

Look at the corresponding sections here: https://cobrablade.net/snarlygribbly/poser.html

You guys at Renderosity are truly awesome! Extremely helpful and engaging.... THANK YOU ALL FOR YOUR VALUBALE ADVICE.

Cheers,

vxg

You're most welcome. :)

Sunfire

Your Poser 11 python scripts almost certainly won't run in Poser 13. I bought Poser 13 and went back to Poser 11 Pro because I was tired of having to do some things using Python in Poser 11 and then having to switch to Poser 13. One big change that made the new version less wieldy was that the ykilled the simple tab in the material room. I use that all the time and go into advanced only to apply a material to all the material zones. You'll have to screw around with nodes instead. Have fun.

Poser 11 is still needed for E-on Vue integration, as it has the required SDK. Vue is free these days, so it may be a useful add-on, especially if you do landscapes, or want to export Poser to other software. Poser 11 can co-exist happily with Poser 13, so why not just have both - then you can do Vue and also run any older Poser scripts as well.