Thanks. That's kind of you and yes, I'm willing to test it. However, it will be a couple of days before I can get Poser 12. I'll contact you when I have it installed.

Snarlygribbly posted at 10:00PM Wed, 04 November 2020 - #4403108

smallspace posted at 8:35PM Tue, 03 November 2020 - #4403096

D3D's "XL Extended Library" is at the heart of my Poser workflow...So exactly how are you going to update a dead man's scripts?

I have updated that script for Poser 12. I need it to be tested, though - would you be willing to do that?

There are programs like E-On Software's Vue that are far better renderers than any version of Poser but are not designed with character manipulation in mind. The combination of the two is better than either program by itself.

blackbonner posted at 11:03AM Tue, 03 November 2020 - #4402983

If you don't use Poser to render your pictures, why do you use it anyway? I did this for a while and it was not a decent workflow, even with Poserfusion for C4D. I transferred the scene into C4D and converted the textures to Vray. This made the rendering quicker and the results were better, but it took forever to get all the bits and pieces together. And to adding a prop you decided to have in the scene afterwards comes close to heart surgery. That's why Poser as a whole makes the most sense to me. The thing is, the render engine Firefly was in my eyes the perfect fit in case of speed, quality and integration with the material room. Cycles is a different animal and it will take time to get things done like they did before in Firefly. So, to answering your question, without using the render engine in Poser, Poser makes no sense at all, at last in my opinion. You can take the obj file of a G8 out of DS and put it in Blender, rigg, texture and pose it there and render it with the Blender cycles engine. From my perspective this is to much work for a little benefit.

D3D's "XL Extended Library" is at the heart of my Poser workflow...So exactly how are you going to update a dead man's scripts?

jennblake posted at 10:49AM Tue, 03 November 2020 - #4403050

We are currently working on quite a few scripts to update to python 3. We are working with the developers of previous scripts to get them working in Poser 12. As was stated previously, implementing python 3 in Poser did break compatibility with a lot of the existing scripts, but please rest assured we are taking steps to get as many of those working in Poser 12 as possible.

Indeed it does work with the association set to Vue, but that requires you to open the file in Windows thereby causing Vue to launch. There seems to be no way from within Vue itself to load the file.

If you create a terrain and go to the terrain editor, there is an icon that says, "Save terrain". If you click on that icon, it opens up a window to save the terrain as a "terrain model" (prt) file. There are no other file formats available in this "Save terrain" function. (yes, I know you can export the file instead of saving it, but it won't be exactly the same when you re-import it)

I understand that I should have gone out of the editor and simply saved the terrain as a "Vue Object" (vob) file. However, I still don't understand why they would have a "save" function for a format you can't reload. (and the fact that the terrain editor has a save function but doesn't have a load function) It just doesn't make sense...

Still curious as to what you did to trick Poser, but as you Brits say, "Thanks mate!"

Messaged you here.

Sorry Snalry, I was confused. I clicked on the "Snarly's Space" which came up as a dead link in the post. I didn't realize you wanted me to copy the email address.

Snarlygribbly posted at 2:25PM Thu, 19 September 2019 - #4362757

smallspace posted at 10:15PM Thu, 19 September 2019 - #4362701

Well, I'm glad I got your attention. Does this mean you'll fix EZSkin 2 to work with the new Poser?

I already have. I refer to my previous message inviting you to get in touch via sitemail so that I can send it to you :)

In view of python incompatibilities, maybe Bondware should just undo the changes they made to Poser python and roll it back to the code they got from SmithMicro.

Ok. According to Notepad++, line 114 of the XL script says

I somehow doubt that is going to help...

BTW Snarly:

I'm sorry I said EZSkin 3 wasn't as good as EZSkin 2, but I really miss having the effects that are in EZSkin 2. Why didn't you include them in EZSkin 3?

So now I've got both 11.1 and 11.2 to work and my license is set to "permanent". However, 11.1 still phones home and I'm afraid soon SM won't answer.

Looks like a Reality error as well:

"An errror occurred importing addon Reality : ERROR: need more than 3 values to unpack

An errror occurred importing addon Reality : ERROR: need more than 3 values to unpack"

Well, I'm glad I got your attention. Does this mean you'll fix EZSkin 2 to work with the new Poser?

Snarlygribbly posted at 10:39AM Thu, 19 September 2019 - #4362662

smallspace posted at 3:51PM Thu, 19 September 2019 - #4362581

Also, EZskin 2 no longer works. Doesn't like the new Poser's build number. Gives the error message, "EZSkin requires build 21462 or later. You have build 272. This script does not work with your version of Poser." Send me a sitemail with your email address and I'll send you an updated version.

EZskin 3 does work, but version 3 leaves a lot to be desired compared to version 2, especially in the effects department. This makes Snarly sad

Snarlygribbly: Tell me how to read and edit python script and I'll tell you what line 140 says.

Snarlygribbly posted at 10:33AM Thu, 19 September 2019 - #4362664

smallspace posted at 3:54PM Thu, 19 September 2019 - #4362579

This is the error I get when activating the script:

Traceback (most recent call last): File "C:GrafikPoser 10 Pro 64RuntimePythonposerScriptsScriptsMenuDimension3DXL.py", line 3059, in File "C:GrafikPoser 10 Pro 64RuntimePythonposerScriptsScriptsMenuDimension3DXL.py", line 3057, in main File "C:GrafikPoser 10 Pro 64RuntimePythonposerScriptsScriptsMenuDimension3DXL.py", line 26, in init File "C:GrafikPoser 10 Pro 64RuntimePythonposerScriptsScriptsMenuDimension3DXL.py", line 140, in init IndexError: list index out of range

Tell us what line 140 says and we can tell you what to change it to