is this possible ?

when i have the morph brush open and have a vert highlighted,

could a python script assigned to a hot key,

create a xtran and a ytran and a ztran parameter dial and morph for the vert and name it under it's vert# from the .obj file?

then i could move the frikk -excuse me - deep breath- vert in 3d space with sereneness

i can't offer my first born, but i could offer a 10 dollar g.c. ?

Attached Link: http://www.philc.net/PoserToolBox.htm

thanks ... but it's not gonna help my workflow 

i need something to lock on to a vert.

a long way to do it, would use wings to make 3 morph targets for a vert x/y/z.    but in poser, how would i know the vert# to know which dial to use ...

and would copy/paste the dials in text, updating the vert# work, assuming the morph #s are relative to the coordinates of the vert

i don't know enough about obj files to know what all the numbers refer to.

theoretcally, i could write vba script in ms-access to read in the vert #s and write out a parameter dial section.  assuming again, morph coordinates are relative to the vert coordinates.  but again, there is still the problem of knowing what the vert # is of the vert i want to tweak.

omg, i need to hug my dog and a few beanie boos -

i wrote a program a few years ago that generated morph targets for each point in an exported body part.  it was my only program ever!  probably pretty easy for anyone with experience in programming. the trouble i had was loading the set i would use in a morph.  one vert was never enough so i grouped them by lines and used loader script.  this was poser 5 and the program would bog down.  so the brush came out and i abandoned the thing.

if you need to see vertex numbers you can install bender, and there is a script called view3d which places vert numbers over each vert selected in the view.

i'm with you though a python script to generate the morphs needed on the fly would absolutely kill.

i would try the python forum here too they love this kind of stuff and have been responsive in my experience

view 3d sounds awesome.

found the wiki page for wavefrontformat  http://en.wikipedia.org/wiki/Wavefront_Object_file_format

according to this there is an optional value for weight

 # List of Vertices, with (x,y,z[,w]) coordinates, w is optional and defaults to 1.0.<br></br>  v 0.123 0.234 0.345 1.0<br></br>  v ...<br></br><br></br><br></br>is the vert coordinates the vert#?  cuz then moving it would change the vert #?<br></br>i guess this is where the vert order # comes into play

http://en.wikipedia.org/wiki/Wavefront_Object_file_format

adding to the request, a dial for moving in the direction of the normal  :wub:

took a peek inside a couple of obj files.

Alyson_hr obj and bl*m4 don't have the 'vn' lines in them.  but when you use poser to export their heads for morph targets the obj files have the 'vn' lines.

Alyson has 1 'g chest' line. M4 has 11 'g chest' lines.

You might try using poser in a two or more window configuration. It may make moving the vertices easier since you are limited to direction in the front, side and top views.

in my experience there is no specific list of the number of the vertex in the obj file.  it's simply implied in the order that it is listed.  i use crimson editor to check which number each vert line refers to.

or you could copy only the v lines to a text file and open in a spreadsheet to find line numbers.

usually when i create an obj in blender, the only data that comes out is v lines and f lines, the v that is the vert index and f tells which verts join in what order to make the faces.  other data is generated by poser.

i'm gonna head over to the python area and ask for this script.