I use Poser 9, now, but because I haven't figured out how to use script/D3D Perfect (in Poser 9) for the V4 tanlines, I go back to Poser 7. I do the same for the V4 Wet skin Shader. I haven't figured out how to use either in Poser 9. But when I open Poser 7 for a Figure, here's what I get!  Can you help?  Thanks!

Did you use V4W-Mapped?
Poser 7 does not work with a W-Mapped figure.
Just guessing.

Poser 1, 2, 3, 4, 5, 7, P8 and PPro2010, P9 and PP2012, P10 and PP2014 Game Dev
"Do not drive faster then your angel can fly"!

I have used Poser 7 many times to add shading or skin moisture.   This is a new thing that is happening.  Thanks!

Don't know what a W-mapped figure is!

V4 is also available as V4WM.  This last one being a newer Weight-Mapped V4 figure.
Weight mapping is the newer rigging method., and Poser7 can not read those.

From the screengrab it sure looks like a rigging issue, so my first thought was;
This could be V4-WM in Poser7. 

But if you never downloaded V4-WM, it must be something else.

Poser 1, 2, 3, 4, 5, 7, P8 and PPro2010, P9 and PP2012, P10 and PP2014 Game Dev
"Do not drive faster then your angel can fly"!

Poser 9 uses a different version of Python than Poser 7, and that may be why your scripts don't work.

You might check with the vendors of the tanlines and wet skin scripts to see if they've updated for Poser 9 compatibility.

---

PoserPro 2014, PS CS5.5 Ext, Nikon D300. Win 8, i7-4770 @ 3.4 GHz, AMD Radeon 8570, 12 GB RAM.

I agree with moriador.  It sounds that you are using old Python Script files where they will not work, especially if the script is compiled .PYC.

As for what's happening to the figure... is it the default V4, or has something been done to it that relies on scripts (such as the complete Perfect version)?

I've had PZ3's blow up on me before without switching versions of Poser. In my case, I'd saved with External Binary Morph Targets, and they have a bad habit of doing strange and unpredictable things.

---

PoserPro 2014, PS CS5.5 Ext, Nikon D300. Win 8, i7-4770 @ 3.4 GHz, AMD Radeon 8570, 12 GB RAM.

To my understanding, External Binary Morph Targets have been corrected in the latest Poser iterations; there is less likelihood of file corruption when saving back to the Library or scene PZ3s.  

Quote - To my understanding, External Binary Morph Targets have been corrected in the latest Poser iterations; there is less likelihood of file corruption when saving back to the Library or scene PZ3s.  

Maybe so, and I thought I'd heard that, too (it's good to know that the issue has been dealt with). But having your work blow up on you makes you hesitant to try it. Given that I save about every ten minutes, I'm not going to be totally confident with "less likelihood". I guess superstitions die hard, you know. :)

---

PoserPro 2014, PS CS5.5 Ext, Nikon D300. Win 8, i7-4770 @ 3.4 GHz, AMD Radeon 8570, 12 GB RAM.

Thanks all!  

Have you check with the developer about updates. There were some updates in 2011

I assume these are the poducts you are using

http://d3d.sesseler.de/index.php?software=poserpython

Gary

"Those who lose themselves in a passion lose less than those who lose their passion"

I must say that this doesn't always happen.   Some of the V4s accept the tanlines and wetskin in Poser 7.   

But that's just it.  Poser underwent a Python script change after Poser 7, so any compiled script released for just P7 and before will not work in P8 to current.