mcjComeHere - The 2023 Version is Here - With 4 Figure Handling Options

function

Havos said:

Check if  she has the X,Y and Z values applied to the hip. If so that will cause her to rotate around the world centre not herself. The x,y, and z translation should be on the root figure. Was the hip selected maybe when the script was applied?

Thank you Havos, your suggestion gave me a clue, at least I can now rotate her by select the hip, not the figure.

But for the mcj script, no matter I select the root figure or her hip to apply the script, still the same result, figure came, coordinates left in the world center, the root figure's coordinates are all 0, the hip coordinates became very large numbers. 

Havos

function said:

Havos said:

Check if  she has the X,Y and Z values applied to the hip. If so that will cause her to rotate around the world centre not herself. The x,y, and z translation should be on the root figure. Was the hip selected maybe when the script was applied?

Thank you Havos, your suggestion gave me a clue, at least I can now rotate her by select the hip, not the figure.

But for the mcj script, no matter I select the root figure or her hip to apply the script, still the same result, figure came, coordinates left in the world center, the root figure's coordinates are all 0, the hip coordinates became very large numbers. 

Strange, I have that same script, and for me the translation is applied to the root, not the hip.

Edit: Looks like I have the old version of the script not the new one. The old one moves the root, the new one moves the hip, which is pretty crazy as in reality you almost never want the hip to translate, rotate, maybe, translate, almost never. There is a parameter were you can specify the node to translate, but I could not get it to work, no matter what I typed in, it always moved the hip. I will stick to the old version of the script.

The workaround for the new version is to place your figure inside a group, and then apply the translation to that. You can then unparent the figure from the group, and it should have the translation applied to the root. Not great, but it is a free script, so you can not complain.

Richard Haseltine

Merged the separate thread with the main thread, please don't post the saem topic in multiple locations.

function

Havos said:

Strange, I have that same script, and for me the translation is applied to the root, not the hip.

Edit: Looks like I have the old version of the script not the new one. The old one moves the root, the new one moves the hip, which is pretty crazy as in reality you almost never want the hip to translate, rotate, maybe, translate, almost never. There is a parameter were you can specify the node to translate, but I could not get it to work, no matter what I typed in, it always moved the hip. I will stick to the old version of the script.

The workaround for the new version is to place your figure inside a group, and then apply the translation to that. You can then unparent the figure from the group, and it should have the translation applied to the root. Not great, but it is a free script, so you can not complain.

Hi Havos, thank you again. You gave a great help. I downloaded the old version and studied both, yes, the new one clearly pointed out that it will use the hip once the inherits is the DzSkeleton, not the DzBone, don't know what this mean, but thing becomes easy, just invalidate that sentence is enough.

So finally I edited the line 132: [ if  node.inherits  "DzSkeleton" ] with a simple - in the word as this: [  if  node.inherits  "Dz-Skeleton"    ]. Now the script works fine, everything is correct. 

Havos

function said:

Havos said:

Strange, I have that same script, and for me the translation is applied to the root, not the hip.

Edit: Looks like I have the old version of the script not the new one. The old one moves the root, the new one moves the hip, which is pretty crazy as in reality you almost never want the hip to translate, rotate, maybe, translate, almost never. There is a parameter were you can specify the node to translate, but I could not get it to work, no matter what I typed in, it always moved the hip. I will stick to the old version of the script.

The workaround for the new version is to place your figure inside a group, and then apply the translation to that. You can then unparent the figure from the group, and it should have the translation applied to the root. Not great, but it is a free script, so you can not complain.

Hi Havos, thank you again. You gave a great help. I downloaded the old version and studied both, yes, the new one clearly pointed out that it will use the hip once the inherits is the DzSkeleton, not the DzBone, don't know what this mean, but thing becomes easy, just invalidate that sentence is enough.

So finally I edited the line 132: [ if  node.inherits  "DzSkeleton" ] with a simple - in the word as this: [  if  node.inherits  "Dz-Skeleton"    ]. Now the script works fine, everything is correct. 

It was a good idea to edit the script. I deleted lines 132-139 completely as I can not think of any reason why I would want to move the hip.

mCasual

i'll look into this soon, maybe add the option of moving figures either by the hip or by the root node

I use mostly mcjParent to move things around sometimes in conjunction with mcjMakeTarget

there's another script named mcjCometh here.

for some of those scripts I sometimes would like if only the X-Z coordinates were changed, for cases when the Y location is already at the correct altitude

oops looks like I did add "axis locking" in 2022 

notably when working with gigantic scenes like the [correction] Moebius87 and Ajax dystopian city blocks

 

in case you wonder what's that stick above the car, using (mcjParent I think)

it's Y-rotation contains the strength of the attention William and Hanami

have for one another and controls their body animation

something like that

and was 

 

 

 

mCasual

ah ok i will add a checkbox titled "move figures using root node"

Havos

mCasual said:

ah ok i will add a checkbox titled "move figures using root node"

it might be a good idea to make that the default. Since a lot of people will want to y rotate the figure after moving it then you want the hip x and z translations to be 0

mCasual

i still have to make registry access D|S 5 compatible and package it,

maybe maybe make sure it works with DS 1,2,3

 

mCasual

Havos said:

Check if  she has the X,Y and Z values applied to the hip. If so that will cause her to rotate around the world centre not herself. The x,y, and z translation should be on the root figure. Was the hip selected maybe when the script was applied?

The script doesn't touch the rotations 

if the hip node is far from the root node and the root node is rotated

and you move the root node in front of the camera the figure/hip will still be far away

OK I know the 4th option I'll add

[Move Hip Here, by using the root node]

thanks for making this idea resurface

mCasual

The 4th option

( mcjComeHere2023 will be online in less than an hour )

 

 

mCasual

to me more complete we could have a script that brings the camera at a specific distance in front of the figure object

because when the Scene is huge, for example a city, the built-in "frame object" of daz studio keeps us far and away

this was a problem with my [correction] Moebius87 and Ajax dystopic city scene

this could be quite useful come to think of it, the camera could be aligned to face-the-face of a figure, which is different from just framing the head

mCasual

The 2023 version is at the same Bat Address same tacky basename: 

https://sites.google.com/site/mcasualsdazscripts3/mcjcome

( which, by the way, was not intentional and due to cursor issues )

Omniflux

mCasual said:

i still have to make registry access D|S 5 compatible and package it,

@mCasual are you able to expound upon this?

mCasual

i've been told by someone not from Daz

that the more direct access to the registry I used so far

was/is deprecated and will/may be removed from DS5

so I use this

var oSettingsHelper = new DzSettingsHelper(); //Compatible with DS5

function getSettingDS5( key, defVal )
{ 
    var path = "mCasualJacques/" + appName;
    var val = oSettingsHelper.get( path, key, defVal );
    return( val );
}
function setSettingDS5( key, val )
{ 
    var path = "mCasualJacques/" + appName;
    var val = oSettingsHelper.set( path, key, val );
}
function saveSetting( key, keyVal )
{
    setSettingDS5( key, keyVal );
}
function saveBoolSetting( key, keyVal )
{
    setSettingDS5( key, keyVal );
}
function getSetting( key, defVal )
{
    return ( getSettingDS5( key, defVal ) );
}
function getBoolSetting( key, defVal )
{
    return ( getSettingDS5( key, defVal ) );
}

 

 

Omniflux said:

mCasual said:

i still have to make registry access D|S 5 compatible and package it,

@mCasual are you able to expound upon this?

function

mCasual said:

to me more complete we could have a script that brings the camera at a specific distance in front of the figure object

because when the Scene is huge, for example a city, the built-in "frame object" of daz studio keeps us far and away

this was a problem with my Stonemason dystopic city scene

this could be quite useful come to think of it, the camera could be aligned to face-the-face of a figure, which is different from just framing the head

 Yes, yes, I always confused in a big scene, my camera or perspective view can not move to an object or figure by one click, when choose the object and RMB/LMB click the magnifier or [+] in the view port, DAZ brings me the whole picture of the scene, far away to the object.

If you can solve this problem, it is a great help. By the way, really appreciate for your quick response and modification to this root/hip problem!

Silver Dolphin

Thank you!!!  Your scripts are always useful.

barbult

This (2023) script always puts the selected item behind the camera instead in front of it. The old version works as expected, with the selected item placed in from of the camera. I had Y Translate Locked checked and Move Root Noide. I tried with a primitive cone to simplify things. Am I doing something wrong?

I think I figured it out. It isn't behind my camera, it is too close to my camera to see it, I think. When Y is locked and the item is at Y=0, it can be below the view of my camera.

mCasual

barbult said:

This (2023) script always puts the selected item behind the camera instead in front of it. The old version works as expected, with the selected item placed in from of the camera. I had Y Translate Locked checked and Move Root Noide. I tried with a primitive cone to simplify things. Am I doing something wrong?

I think I figured it out. It isn't behind my camera, it is too close to my camera to see it, I think. When Y is locked and the item is at Y=0, it can be below the view of my camera.

thanks i think it will be easy to fix, substracting vectors instead of adding

i'll fix it right now and post the announcement below

oops i see you were locking a coordinate

there's also a script named mcjComethHere ( i forgot what it does exactly

lets see ..

https://sites.google.com/site/mcasualsdazscripts7/mcjco

Select a figure, usually in the Scene Tab

Run the script

The figure now stands 4 meters ( 12ft ) in front of you

 

mCasual

personally the script i use most to move things around is mcjParent

it can parent things to one another but it can also move their World-Space positions and orientation, even in an animated way

and while you're at it, get mcjMakeTarget, combined with mcjParent it has many many uses

https://sites.google.com/site/mcasualsdazscripts/mcjmaketarget

https://sites.google.com/site/mcasualsdazscripts3/mcjparent

 

barbult said:

This (2023) script always puts the selected item behind the camera instead in front of it. The old version works as expected, with the selected item placed in from of the camera. I had Y Translate Locked checked and Move Root Noide. I tried with a primitive cone to simplify things. Am I doing something wrong?

I think I figured it out. It isn't behind my camera, it is too close to my camera to see it, I think. When Y is locked and the item is at Y=0, it can be below the view of my camera.