I grabbed Poser 11 since Adobe shutdown flash. But, now my old Dimension3d utility scripts don't work in the new Poser.

What scripts/utilities do you all suggest for Poser 11+ to turn off shadows and smoothing on multiple objects all at once?

Thanks!

Which D3D scripts don't work in P11? It is a known fact that Python 2 Scripts won't run in P12 because of the Python 3 upgrade. Updating those scripts is in the works ATM.

https://www.poserlounge.nl/PLWP/ You need to get AVfix.

Thanks Hborre and RedPhantom !!

I have D3D's old multi-object manager and the newer XO object manager.

I'll give AVfix a go.

Thanks a lot!

AVfix worked like a charm! Even on the old D3D Object Manager which I prefer. Thanks so much RedPhantom for the link and thanks Snarlygribbly for the awesome AVfix !!

hborre posted at 1:48PM Sun, 07 March 2021 - #4414403

Which D3D scripts don't work in P11? It is a known fact that Python 2 Scripts won't run in P12 because of the Python 3 upgrade. Updating those scripts is in the works ATM.

The one I used the most from D3D was his XS (Extended Shader Manager), where I could do something Poser could never handle - editing multiple materials in one go. I love Poser 12, but sometimes I am forced to go back to 11 just to adjust materials with D3D XS. Would take too long without it. Snarly was kind enough to bring it to Poser 12, but it is only partially working. It's a tool that does MANY [incredibly useful] things, and I find it essential in my work flow. Any chance Snarly could get an extra incentive to work on this one? Then I wouldn't have to go back to Poser 11 so often.

I um...could send cookies?

LOL I have tried to sweet talk him, but I understand he deserves more than that for such a effort. I have worked a bit with Ralf's code when we worked together years ago, and I have to say I wouldn't want to be on Snarly's skin on this task. Ralf's code is one of the most challenging to read I have seen in a long time. I don't know how he understood any of his own code.

Nonetheless, I find XS essential for my workflow in Poser, and it has been HARD going without it in version 12. Since the question was asked above, about which of D3D's scripts I would like to have in Poser 12, XS would be my highest priority.

Besides offering the cookies, I really can't help. I never used that script, having relied on Snarly's EZSkin and Semi's Library Manager (now sadly unusable) myself. I personally think all of these scripts made P12 compatible should be offered as paid versions to compensate those working on them. I always hated the 'artists should work for free' approach regarding upgrades or just, you know, version compatibility. It is not easy rewriting code.

I agree that no one should work for free on a challenging task, such as trying to make sense of Ralf's code. If someone would be up to the task, that would be Snarly. He has the source code, but you have to have a will of iron to delve into that kind of cryptic code without a good reason. The best he could do was to have it partially working in P12 without error or crashes, but it's still mostly dysfunctional.

For the record XS does miles more than EZSkin by a long shot. We can even reconfigure and reconnect shader nodes in a different way over multiple materials in 1 go. For example, select all the hair material zones, change the specular values, and plug whatever is plugged into the bump map to the specular channel - all in 1 go. In another example, if we have 40 copies of a prop on a scene, we can edit their materials all in 1 go. Or edit the material from 1 of them, then copy to all others, no matter how many MAT zones they have, all in 1 go.

Is Bondware not paying Snarly?

Seems like it might be complicated to sell the update, since it's based on work by someone else. Unless they can work out a deal with Ralf's heirs.

Maybe we can set up an Indiegogo or something.

I actually don't know what the deal was. I just know he didn't seem motivated to continue working on the XS script anymore than he already did. But I bet Rendo has offered Ralf's family a deal to benefit them financially, or else why would they provide the source code? One thing is for sure - if his code isn't upgraded to Python 3, all his work will be lost. I do not believe Rendo (or anybody) wants that to happen.