This means the characters your using were designed for an older version of Poser. You can still use these figures by choosing the FireFly render engine.

Open the Render preferences by click the Render menu and choosing Render Settings ...

Then switch to the FireFly tab

Then Click Render Now (Firefly)

 Poser doesn't import cameras from FBX but here's a trick to do it. In the app you're exporting from add a prop like a cone and parent the camera to the prop. Then export the scene and include the prop. Import the scene into Poser and parent a dolly camera to the imported prop at frame 1.You will need to aim the camera manually. But, now the camera will track the way it did in the source app.

I haven't used the FBX import in a while so I had to make sure it hadn't got broken. It imported the animation as expected. Where did the FBX come from?

The combine figures rarely worked. If you were getting usable results you were getting lucky. Once we have proper unimesh, single skin figures implemented  Things like the combine figure function will reappear and this time they'll actually work most of the time.

The weird way Poser figures have always been cut up is why that cause problems, It would attempt to re-group the figure and the clothing. Usually the auto-created groups just wouldn't work.

Could be the texture cache too. If it has to reload the textures after the render it will take longer. Try increasing the size of the cache.

There's a free version of UVMapper get that here: https://www.uvmapper.com/

Open the OBJ file for the item you need a template for.

Save the template from UV Mapper.

First before exporting on the Poser Figure menu set the skinning method to "Simple Bones Single Skin"

FIle > Export > FBX be sure to check off all the body parts you want to include.

Then be sure include geometry is selcted

Poser export options

This will get you in the right vicinity. You'll probably need to fix some bone orientations once imported into Blender..

Updating the python scripts is original author. Some scripts are an easy update some are not. There is a Python that will link the runtimes from an older version of Poser to the current version.

Here's a link to it from my Dropbox:

https://www.dropbox.com/s/wx4ht0vs5e45vnt/N3D%20Link%20Previous%20Runtimes.zip?dl=0

Get Poser 11. Use it to import the DAZ stuff you use and save it in native Poser form. Then if in the future you want to just use Poser 12 you can.

We've approached DAZ about updating DSON and they showed no interest. We can't, we don't own it. For it to work it has to include some code from DS.

The worth of upgrading to P12 depends on where you are now and the hardware you're running. Poser 12 added significant hardware support with support for Optix and RTX GPU's. The render speed improvement is exponential if you're using an RTX video card. Easily 10 times faster. Even CPU rendering saw significant improvements with the addition of adaptive sampling. There is a downside to P12. With the end of life of Python 2 we were forced to migrate to Python 3. Some older Python script aren't forwards compatible.Poser 12 also removes the Face Room. Some of the technical limitations of the face room were hampering future figure development. Single skin or "Unimesh" figures aren't compatible with it's technology.

And that's just the difference from Poser 11 to 12.

The exact release date for P13 is not set yet. There will be upgrade paths but none of that's been set.

The most likely culprit is bag geometry. There are combinations of geometry that break the subdivision in Poser. An example of this is something called collinear facets. Another that can cause issues is non-manifold surfaces. Poser attempts to detect these and avoid attempting to render them but the possibilities of weird geometry are endless.

The work around is to use the older version of Poser (Yes you can have more than one major version installed on your computer) and remove items from the scene until it will load properly. That at least you'll know what prop or figure is causing problems.

Awesome. Definitely stashing this one in my bag of tricks.

Oh and I almost forgot yes you can do some tiny formatting in the simple dialog ...

import poser

poser.DialogSimple.MessageBox("1. This is my super interesting\n2. There's even more!")

But the simple dialog won't expand if theres more than will fit. That's why the web link is probably the better solution.

If you want formatting beyond just text use the HTML solution. And as pointed out above the HTML doesn't have to be on the web. It can be in a local folder. It can be a PDF too.

webbrowser.open_new("http://www.mycoolwebsite.com/MyAwesomeReadme.PDF")