Mon, Jan 6, 9:04 PM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

Forum Moderators: Staff

Poser Technical F.A.Q (Last Updated: 2024 Dec 04 2:47 am)

Welcome to the Poser Technical Forum.

Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)

This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.

New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: morph target madness


Darkworld ( ) posted Mon, 19 August 2002 at 7:51 AM · edited Fri, 02 August 2024 at 12:53 PM

well, im in the extremely frustrating position of no longer being able to do something that i used to take for granted i.e. morph targets. nothing i am doing is different now but for some reason when i create morph targets for figures or props after i have extracted the geometry and done the texturing etc, it always says wrong number of vertices and i am unable to use the morph target. i am using rhino 2.0, and i have found that if i create the morph target while the geometry is still embedded in the library file, it works fine, but as soon as i extract the geometry into a separate obj, (and re-add the prop to the library) the morph target stops working- and any attempt to re-add the morph fails because of the vertices error. i have no idea whats going on and i have tried checking and unchecking every single option in poser (when i export as morph target w no world transformations) and in rhino (when i export the modified file as an obj to be used as a morph). These are the steps i usually do: 1) i start with a pp2 file in poser which has an external obj in my geometries folder. 2) i add the prop to my scene, and then export it as an obj, checking the no world transformations option (export as morph target) 3) i use OBJ to 3DM to make the export readable in rhino 4) open the file in rhino and change it as i would like to for the morph. 5) re-export as an obj, which is now the morph target itself. 6) click add-morph target on the prop in poser, and choose my new obj. 7) look at the wrong number of vertices error and bang my head on desk. Steps 1-6 used to work every time, and it's damn frustrating to not know whats different now. any help at all would be most appreciated. thanks! Brian


bloodsong ( ) posted Mon, 19 August 2002 at 9:51 AM

heyas; if it is pointing to an obj, why don't you use that obj instead of exporting? that would be step one to fix. and it'd be faster, too. then look in obj23dm at the options and make sure that you haven't changed anything or turned anything on. i had that happen to me, i did something innocuous like try to remember the material settings or something. if that isn't it, look at the obj. run it through depent (which should be here in the freestuff utilities), and make sure that it only has quads and triangles. if i recall, the obj23dm does something odd with n-gons when it translates. look in the options, it says what it is, there.


Darkworld ( ) posted Mon, 19 August 2002 at 10:34 AM

hmm ill check obj23dm to make sure i did not change any options, unfortunately if i convert the obj in my geometries folder for the prop i get the same error =(


Darkworld ( ) posted Mon, 19 August 2002 at 10:51 AM

i did the following test: i imported the external obj directly into poser as a morph target... that worked (though of course the morph does nothing as it is the default shape) then i changed the external obj into a 3dm for rhino, and in rhino made NO changes to the file at all, exported again as an obj (several times testing different options checked) and in poser it still tells me wrong number of vertices. i checked the options in obj23dm and the only option i had checked was include groups, i tried with this unchecked and got the same error... the only other options to check are textures, materials, and normals, all of which will add extra vertices so i leave them unchecked always. so i guess the error is occuring either in the translation to 3dm, or in rhino when it exports, even though i didnt change anything... ARGH


bloodsong ( ) posted Mon, 19 August 2002 at 6:55 PM

hmmm... did you see the option to turn 5-sided polygons into nurbs or whatnot, in obj23dm? that might be causing some polygons not to be translated correctly, and that's where you lose them. but i'm not sure.


bloodsong ( ) posted Mon, 19 August 2002 at 6:57 PM

hey... did you try another prop in the meantime? if it's just that one, then there's something definitely screwy with the geometry. if it's on all of 'em.... you're in BIG trouble ;)


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.