Ah, and no brackets around EachActor got it,

(I was using SQL bracketing [table].[field])

Thanks, Struct.

That's very close to what I read online but not quite an answer to my question. Your answer assumes that I know I am on row 0 and I know how many rows there are. I won't. I want to loop.

my question is:

During a looping process how can I refer to the CURRENT row, column 1 and 2?

maybe its: 

For EachActor in ActorList:

    [EachActor].[0]SetParent([EachActor].[1])

have a nice day

What?

We could always change the UV maps associated with an OBJ file with tools like UVMapper, or Objaction Mover.  Those tools go back to the 90s! There’s nothing new there.

You never wanted to do that because nonstandard UV maps were a problem, and a standardized UV maps had distortion problems.  This obviously is still the case.

The original “one size fits all” Genesis (one)  UV map idea failed.  Now we have a DAZ creating official nonstandard (Sorry, "optimized") UV maps for Olivia and Lilith. Just like the difference between the V4 and M4 textures;  They sometimes work together, but not always.

And again I’m not talking about the rigging.

But here if this helps:
Yes, you are totally right, DAZ never made a mistake, DS is better than Poser and Genesis (TM) represents a massive advance in computer science.

(just not one I’m going to use)

z

(geez, I really wish that guy hadn't moved my post to the DS forum)

Hi Male... (?)  (M3?) dia?

You seem a little defensive, and the last thing I want to do is start some kind of flame war.  But it sounds to me like you’re telling me I’m wrong, and then agreeing with me.

The “the one mesh fits all”/ “one UV map fits all” original concept of Genesis (one), that I read in that press release,  didn’t work (for humans) that’s why they came up with Genesis II, (male and female ) with custom UV maps, you can call them “optimized,” I’ll call them “corrected for distortion.” Same thing. One mesh, several UV maps.  Just like M4/V4/Freak4.

Granted: there have been massive improvements in rigging.

But the upshot is I can try to use different textures (of the same Genesis generation) and they may, or may not, work, or be a little bit distorted  -- Just likeM4/V4/Freak4.

I have no idea what you mean by “When you design a mesh properly, whether it's a figure or an outfit, you will not have major issues with texture stretching.”

When you distort a mesh, (make some parts bigger and other parts smaller) the texture will be equally distorted, unless you are using some kind of a procedural, universally-scaled texture.  When distorted to extremes, the distortion will be extreme.  There is no “designing it properly” to avoid this - sorry. (even with "Genesis tech")

So like I said, I think I get it .

Thanks guys,

z

(Move the thread if you like, I’m trying to use Victoria 6 in poser)

I think I understand this now: Genesis didn’t work (as I predicted).  All that texture stretching was a problem. 

With genesis 2, they went the opposite direction, and back to the M4/V4 unimesh concept (I’m not talking about the rigging) with a single mesh that they distort, and then provide different UV maps to us that compensate for the distortion.

So M6 will take G2M morphs but not textures?

Clothing use usually compatible (or fixable) right?

Olympia, Lilith, Victoria 6 are ALL different UV maps?  (what a mess)

What about Steph 6 and David 6, to they take V6 and M6 maps?

My real question is that textures: textures are going to be incompatible across all of these characters? Am I right?

Stores sometimes use glass shelves, or Wire mesh, for this reason.

or they put little lights under the shelves...

I think there are spash OBJECTS (.obj files ) at sharecg.com. You would use a water texture.

oddly enough, I thought of that, and figured it might work once or twice, and not work more often. (what w/ body translations and IK and all)

.. and then I though  why can't i just rotate the #&*%ing scene?!

thanks :)

Quote -
The real point was that, if a pose does not contain BODY transforms, and any x or z hip translations are not to large, you can use the BODY transforms to position the figure anywhere in the scene, in any orientation, at any altitude, and applying the pose will not significantly change the location of the figure within the scene.

That's two big IFs

And like I said, that's what I what was doing. But I got tired of having to rotate the characters.

Actually making it all one big OBJ prop may not be a bad idea, just not ALL of it, I'd leave a managable number of "loose"(animatable)  props...

hmmm...

Well thank you mystic,  but as I said the scene is rotated 90 degrees on the Y axis; Lesbentley's illustrations are more accurate.

(If this was the problem, I could just rotate the images in post)

and BTW: UPDATE:

I tried; I created a cube and parented everything to it! and then rotated the cube and some stuff MOVED.Changed  Y translation.  (I hate  it when you re-parent things and they move wierd.)

So I hit undo 2 or 3 times and Poser crashed!

(maybe it was already in an unstable state when stuff moved wierd.) 

Guess I'll try again...

~~SIGH~~

I've been rotating the characters. :(

But many poses are not properly made, and for poses made for 2 or more characters you can't do that.

Looks like I just have a whole lot of clicking and dragging to do in the Hierachy editor :(

thanks guys

There are too many objects ----

Is there a PY script that will group everything?

BTW in Bryce you do this with Control-A, Control-G. Why is poser so obtuse?

OK I just tried to open the file to render an example and Poser crashed!

I'll try this again after I have sr1.

thanks guys

z

No, it drapes right,

but as the character sits down, the hem of the shirt seems to just get snagged on an invisible hook. there's no other way to decribe it,

I've looked nad I have ealier versions of the file where it works, but if I re-simulate the cloth, now it gets snagged.

I'm thinking its either file corruption or Poser 9. (I've been trying get SR1. but they don't like my seral number, and I cant talk to tech support until monday.)

thanks