Well...That now made me red in shame.

Thank you very much my friend, you solved both my problems, those dials are not hidden for the feet, however they were hidden for me and appeared as soon as i turned IK on for both legs.

Thank you very much again my friend

DarkEdge is Right, he helped me a lot with a similar issue, but, using QUIDAM STUDIO.

Anyway what worked for me was using the original geometry(which is inside your runtime in the geometries folder), or exporting ONLY the head and working on it then exporting it, also check if Blacksmith is not generating new polygons dynamically(pixologic´s Sculptris does this).

You might get some insight from this Thread --> Destroyed Vertices...

Thank you all for your help, awesome tips.

I managed to get everything working, unfortunately i have always to work with original geometry.

here is what i was aiming for guys:

http://www.renderosity.com/mod/gallery/index.php?image_id=2218951&section_id=1&genre_id=2&np

C:Program Files (x86)PixologicSculptris Alpha 6

Thank you very much for you help DarkEdge. I´ve done like you said: 1st: I zeroed the figure then exported according to your instructions only the head and then reimported as a morph into poser, then dialed 1, the head doesn´t explode,but, it moves a tad back. 2nd: I zeroed the figure then exported the whole body again folowing your instructions, and then reimported as a full body morph into poser, then dialed 1, nothing happens, dialed higher numbers, again nothing happened. if i export according to icandy265, it is also OK. I had it done before and the explosion happened, however, now i´m sure that i must´ve done something wrong. BUT, i must say that the Geometry explosion only occurs if i do a full body export, edit and then try to reimport it as a full body morph or only part of it as a moprh target for some part of the body (doesn´t matter) it will explode; exporting only a body part editing and bringing it back as a morph target will work fine. Thank you again m8, do you have any suggestions on how to fix it (other than loading the original geometry)?

After testing according to nruddock suggestions i can confirm that the problem still persists, definitely poser is doing some weird stuff when exporting, i suspected as much when i compared the size of the original file and the size of the one exported, they are different, which for me means different stuff on the file, thank you for your help anyway, but, maybe we could still figure out what is wrong. Thank you icandy265, i would really like to know what happens when poser exports it, maybe it inverts the vertices?

Sorry m8, but, i still don´t get it. how come when i export the figure from Poser it gets destroyed when used as a morph target and it doesn´t happen when i get it from this folder Poser Pro 2010RuntimeGeometriesFOLDER_OF_THE_MODEL, also i did notice that the poser exported file size is different from that of the original geometry gotten from the folder above. I don´t get it, could you explain to me why does that happens? The certain stuff is that somewhere the vertices get messed up, but where?why doesn´t the modelling app mess up the vertices when using the original geometry(not the one exported from poser)?

Well guys, as a last attempt i went for the original geometry file inside poser directory (Poser Pro 2010RuntimeGeometriesFOLDER_OF_THE_MODEL), imported it on QUIDAM, tried the modifications, exported it again exactly like i did before and guess what...it worked, with no problem, but, if i get it straight from the library and export it through Poser then things get hairy, my guess is that poser is messing with the geometry when it exports it...what could it be doing?

nruddock -> tried you script m8...sadly it didn´t work(or i screwed). When i said " on the mirrored side", i meant the way QUIDAM works, when you´re editing one side of the model QUIDAM does the exactly the same thing on the other side, so, if you´re pushing vertices on one side it will do the same on the other side as well. the Odd stuff is like i said before that, if i export only the head(or hand, or hip...or any part)of the model and then edit it, it comes out OKay, the weird stuff only happens when editing a fully exported model, and only when i try to use it as a morph, if i import the edited mesh inside poser it looks perfect...weird IF any of you have more suggestions i would appreciate that, but, thank you anyway for every effort so far, i really appreciate that.

Thank you all for you effort to help guys markschum -> Yes it does look perfectly Normal Cage -> The problem happens Randomly, sometimes on the mirrored side and sometimes on the other side, Does UV Mapper have a free version? BionicRooster -> Thank you man, just tried your method and unfortunatley it didn work...the results are the same, but thank you anyway, maybe if you explain it better i could narrow down where i did it worng(if i did), because the model went in with all group names intact and came out with the group names screwed(object1, object2....objectN), i managed to find the Object which was the head and tried it with no luck I found out that if i export only one part of the model from poser and then do the modifications on Quidam and then export it works flawlessly, the same is not the truth when i export the whole model and then work on it...i´m trying exporting without the internal parts now(eyes, Tongue...)to see if it affects the export thing...lets see how it comes out.

Thank you BB,

That actually worked, it was not a problem with primary and secondary display, but, i´m pretty sure you were right when you said that it was a problem with the way windows manages the screen(s), plus, i must add that when the library window was brought back it was resized to a minimum.
Thank you you for the advise LostinSpaceman, but, i had tried that already and it didn´t work.

Thank you very much

Thank you for the links(i saw those threads before) however, the issue is not the same, the other guy was experiencing problems with Poser main Interface while i have problems with the library window which in Win7 X64 is not a child window , it is an independent application(lsmguiair.exe), and that´s a real pain in the ### because that little bugger doesn´t have the mxaimize, minimize or restore options if you right click on it neither it will respond to the keyboard shortcuts...