Theoretically, if everything else fails (e.g. because there's a problem with scaling, or you don't have Studio installed at all, and also don't want to!), you should be able to convert a morph injection manually, by creating a Poser-compatible pz2.

First you'ld have to unzip the .dsf file to get the ASCII text.
From that file, delete all the DAZ blurb except the "deltas" block:

[ 15, 0.02561665, -0.07484436, 0.02943885 ],
...etc...

Now replace ALL "[" with a "d", delete all commas, and also delete all "]"
Now it should look like this:
d 15 0.02561665 -0.07484436 0.02943885
...etc...

Enclose this by a morph injection code, like this:
{
version
{
number 4.01
}
actor head:1
{
channels
{
targetGeom newMorph
{
name My New Morph Channel
enabled 1
forceLimits 1
min 0
max 1
trackingScale 0.02
keys
{
static 0
k 0 1
}
interpStyleLocked 0
indexes ***
numbDeltas ***
deltas
{
# here goes the "deltas" block
}
blendType 0
}
}
}
}
/>

Now you only have to fill in the right amount of "indexes" and "numbDeltas" as marked by a placeholder *** in above code.
You can find them here in the .dsf file:

"vertex_count" : 39096,<br></br>
"deltas" : {<br></br>
"count" : 13748,<br></br>

/>

At least I could imagine that this is a way that could work.
I can't check it currently because of lack of time. But maybe it's a starting point, just in case...

Peter

I don't think so...
V4 has "water-tight" nostrils yet had that problem with some textures.
I think it might have to do with some textures still using Ambient_Color/Value settings to avod them looking pitch black.
I use IDL and my own shader tree for V4, and the nostrils use the same shader as the rest of the figure. Never had problems with nostril glow since then.

I might be wrong about the cause of nostril glow... but it works for me.

Peter

And, *why" has it to have no holes (which the term "water-tight" means I suppose). What happens if there are small holes present? Gamma ray flux overflow in 3D Printing Module, leading to immediate warp core breach? Mr. LaForge, I want ANSWERS! ;)

glitteraty,
This may work with clothing (clueless because I only have PP2014), but when it comes to complex objects it's different (In my example, I chose the wristwatch for a reason because it incorporates rigid and deformable parts at the same time).

I don't think that it will work well with rigid objects, and I also suppose (note well!) that the decimation tool doesn't provide options for rigid objects.
So it's back to good old handicraft...

Peter

I think I know what you want to achieve, and I think it won't be possible:

With all the different figures, different material zones, and most of all: node setups, it is almost impossible to write a "one script covers it all".

A simple example:
I made a figure which has several "options" attached to the diffuse map, like makeup, blushing/sweating, lip's moisture, and whatever.
This is all in a shader tree which also includes SSS, specularity and whatever, and it would be a nightmare to edit manually.
But "I was smart and added a lot of blender nodes" to easyly swich between the options :/

Good so far.

However, if you write a script that shall hunt down the specific node which you want to change, your script would have to have some kind of AI - in order to determine what each node actually does, and which node is "THE ONE" which must be modified.
It also must account for the settings of the blender nodes, i.e. which part of the shader tree is current.

Now back to the initial problem of identical material naming:

I model a bird with "wings" and "legs/feet/claws"
Next I model a whale, which has "flukes" and "fins"
because I have nothing better to do, I spend the rest of the week modeling a centipede: no "arms" at all, but lLeg1 + rLeg1 up to lLeg100 to rLeg100.

Any idea about a common naming convention for these three?
And I don't even talk about tails here, though some animals and male humans could eventually share some here :D

Summary:

I believe that such a script can be coded, and it would probably be of great help for people who frequently work with a particular figure.
However, I see no other way than that this script must be written for this particular figure, and all it's particularities.
Anything different in other figures would break the script, because it's nearly impossible to cover all eventualities (as I described above)
So a "personalized" script would be necessary for every original figure, and all it's particularities, and 100 legs or wings...

Peter

Mike,

I don't have Blacksmith so I don't know what this program can actually do.
Creating a geometry that has all the necessary extra polygons included isn't the problem.

The problem is, as I wrote in my post, to adapt the joint zones and to bring back the morphs.
However, if all that Blacksmith (or any other external modeler) can do is creating a Wavefront object which is imported back into Poser as either a morph or (in my suggestion) a body part replacement, then I'm afraid that, in order to integrate it into your figure, you'll have to resort to the tools which Poser currently has. (And some are really magnificent)

Of course, if Blacksmith has the tools to make the projected modifications and then export it as a "Poser-ready cr2 figure", that would be a completely different story (and a serious reason for me to consider buying Blacksmith).

Because, you see, I've been fiddling with what you suggest in your OP, for some time too.
(Though my motives may differ: being a little pervert ;) , I rather think of nipple rings and other body piercings to stay in place, no matter how the body bends...)

So let's see if there are other suggestions posted. This could become very interesting because it once more pushes Poser 3D to the limits.

Peter

Why don't you two just go to 4chan and fight your "willie size" issues there?

(Disclaimer: Just my own skill level and knowledge here, there may be other ways)

On a basic level, you can do this (just tried it).
There are however a lot of caveats that come with this method.

I tried it with a wristwatch, and here's what I did:

• I added the wristwatch, and then exported the left forearm (to which it is attached) and the wristwatch as a single Wavefront object. Keep everything unchecked in the export options except "Include existing groups in polygon groups" and "Preserve existing material names".
  EDIT: And make sure that you figure is absolutely zeroed before exporting - no morphs, no scales, no anything else!
• Then I deleted the original wristwatch from the figure and reimported the object I had created before.
  A forearm with the wristwatch should load, in the same place as the figure's forearm.
• Select the figures's left forearm, then from Poser "Object" menu select "Replace Body Part with Prop".
  The original forearm will be replaced with your forearm with the watch.

That was the easy part.

BUT: =====

Because the watch is now a part of the forearm geometry, the bending of joints will affect the watch too!
This might not be a problem in case of the strap, but you certainly don't want the casing to bend and deform with the wrist joint!
So you'll have to edit the joint zones in question, and traditional rigging would lead you nowhere here. You'll have to use weight maps.
Like this, I think you could weight map the watch casing in a way that it moves along with the strap, while keeping it's rigid shape. Interesting challenge, and probably worth looking further into.

Yet, there's a much bigger problem:
Because of the different poly count, all morphs that were in the original forearm are lost!
You can bring them back if you load another, identical figure which still has it's original forearm with the working morphs, and just use the "Copy Morphs From..." Poser Menu Command to copy the forearm morphs into your modified figure.
BUT (there's a lot of "but", I know...):
Poser does copy the morphs (in sometimes questionable quality, so check each morph for irregularities after copying!).
But it does not copy the dependencies, if there are any. So spinning the "forearm thickness" dial in the BODY actor won't affect the (new) left forearm morphs.
You can remedy that by either setting all morph dials in the forearm manually, or you must edit the cr2 file and recode the dependencies, one by one.
Quite a job to do...

Yet, there's another "BUT": Though it's improbable in the case of a forearm which is rather neglected by *Third Party Morph Injections" which use pmd files, it might become an issue in other body parts:
Because of the differing poly count, those morph injections won't work on the, your modified, body part, so it starts all over again: Load a figure duplicate, inject the morphs there, copy them to your new figure, resurrect dependencies...

How all this could work with clothing, I have no idea. But given the amount of work necessary only for that stupid wristwatch, I doubt that it's a practical way to go at all.
Maybe in a future "PP2525, if man is still alive" :D

HTH
Peter

Not a gerbil to be precise.
It's a "Jerboa" - a "Desert Rat". British 7th Armoured Division sign, WWII. Knowing history doesn't harm - Google is your friend... ;)

-P-

Now this is strange...
I'm using PP2014 SR 3.2, since you asked, and that "Show Hidden Parameters" option worked in all SRs. Funny.
I know that I might sound like a SM "Customer Support" dud right now, who always tells you the standard reply:
"uninstall/reinstall Poser"...
But sometimes it's the only way if Poser screwed up.

I had a funny issue when in the "Render Settings" box all the buttons below (OK, ABORT, etc.) were gone, nada, nichego.
They returned only after a fresh intall of Poser. Doh!

Peter

But that would make it a "BNVIATWAS"!
From what I saw hitherto, most "NVIATWAS"s have hair styles that would take poor Vicky two days to style - and then, add the time to practice sword fight! :D
;)
However, I only can emphasise the other part of your post re. the learning curve. We all started like this, didn't we?

Peter

Well, what can I say? :O
Nothing at all, I think. It speaks for itself. And END OF THIS ISSUE.
Back to the thread's topic!
And I firmly stand up to my opinion as posted above, because I strongly believe that upholding backwards compatibility at all cost is like cutting our legs off because the "amebae" which we stem from had'nt these.
Peter

ho-hum...
I still remember from the time when "I" started with Poser, how enigmatic and unpredictable all the strange new functions were. At times I was totally lost and thought of giving up!
However, it was a stupid assumption of mine that a program as complex as Poser could work "load-click-make art". Instead, I read several thousand web pages od tutorials, forums, and spent uncounted hours in the Poser program itself, trying, failing, trying again ad nauseum...

Please understand that you won't get a simple "walk-through" to your question - it's impossible! If you look around in the forums, you'll stumble over countless threads that deal with exactly this problem.
READ them, try out what you find there, and learn! Add bookmarks for threads/websites that appear to be useful, but above all:
KEEP EXPERIMENTING!
You can't destroy your computer if you do something wrong; worst thing that can happen is a (rare) reboot!

There's an old song from the band "Deep Purple", it's on their album "The Book Of Taliesyn" (1968!):
"Listen, Learn, Read On"
https://www.youtube.com/watch?v=uYZaXo4jOu0
Make it so!

Peter

@ adh3d:
Maybe you have a point there, but I think it'll lead us nowhere. V IF we still would care for backwards compatibility at all cost, we'd all still be on DOS, running 8-Bit programs on black/amber screens.
However, this is Poser 10, and it's 2015.
So IF someone is still on Poser 8, or 6, whatever, then: fat chance! He can't use the figure!
But does that mean that we all >>have<< to ignore the great new Poser features, >>just<< because of those few odd people refusing to update??
IF so, then we should all revert to Poser 6, and live happily ever after...

To sum it up:
Staying behind just because of a few dicks who refuse to update results in stagnation, and leads us nowhere.
Do cars still have petroleum headlights, and do people expect to get a fill up at every gas station? ;)

Peter

@ shante:
In the Parameters Pallette, click on the tiny white "right-pointing" triangle top right on the pallette; click "Show hidden parameters" from the drop down menu.
There you are.

Peter