Tue, Feb 18, 3:45 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Moderators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 18 7:53 am)



Subject: Question about applying faces from the library


amlaborde ( ) posted Mon, 03 March 2003 at 11:11 AM ยท edited Thu, 06 February 2025 at 9:07 PM

I have downloaded a bunch of faces and have tried applying them to Vicki but with almost every single one I keep getting the message "Some information stored in this library does not pertain to figures of this type" Am I doing something wrong or missing something alltogether on this matter? If I click ok, it still does something to the face but not anything close to what it is supposed to look like, Its all deformed. Hope someone can help. Thanks, Annette


Peter_Marino ( ) posted Mon, 03 March 2003 at 12:08 PM

Are you trying to use Faces meant for Vicki, or for another figure? Are you trying to use Vicky 2 faces on Vicky 1?! More information, please.


amlaborde ( ) posted Mon, 03 March 2003 at 12:17 PM

Well I am using Vicky 2 and the faces say for Vicky. I will have to read through the readmes to see if it says specifically just Vicky or Vicky 2.


Khai-J-Bach ( ) posted Mon, 03 March 2003 at 12:18 PM

hmm get the same.. using Vicky faces on Vicky.. (yes the right vicky) .. gonna be interested in any answers...



steveshanks ( ) posted Mon, 03 March 2003 at 12:40 PM

What it means is you are missing morphs, as an example if i created a morph called big nose then saved the face and sent it to you and you tried it you'd get the error your getting coz you where missing the big nose morph...Is this a Vicky 3 error your getting??...Steve


Khai-J-Bach ( ) posted Mon, 03 March 2003 at 12:42 PM

I'm getting it with Vicky 1 and Vicky 2....



amlaborde ( ) posted Mon, 03 March 2003 at 1:04 PM

Nope this error is with Vicky 2. Thats interesting that I am not the only one who got it. Hmmm.


Jaager ( ) posted Mon, 03 March 2003 at 2:19 PM

As Steve said, that is a general Poser message. It just means that the pose file has a morph(s) that the cr2 does not. It cloud be as simple as a 'targetGeom shape1' that the author left in his original cr2 by mistake. The way to find out: Open the fc2 in Cr2Editor v1.51 Save a face pose of the cr2 you wish to use it on open it beside it. Compare the list of morph channels. Those in the out fc2 that do not match, expand, if the key ( k 0 X ) is X=0 for the extras, then don't worry about it, you are not missing anything.


Tomsde ( ) posted Mon, 03 March 2003 at 3:13 PM

I've had the same message when applying faces created for the original Micheal to Micheal 2. In this case, however, the face does look the same as the illustration usually. Texture maps can make a world of difference, if you texture map for Vicki is different than the texture map used to save the face with there would be a difference in appearance. A screen shot of the face in the library and the face on your model might help people analyse the problem further.


amlaborde ( ) posted Mon, 03 March 2003 at 3:39 PM

Thanks a whole lot for the helpful info. I will check it out in the Cr2 Editor and see if that helps and if not, I will be sure to check out the different textures too. Ya know that thought did cross my mind and I did try rendering one with a few different textures and they were so hillarious, I dont think that texture would have made a whole heck of a lot of a difference. LOL


Jaager ( ) posted Mon, 03 March 2003 at 3:57 PM

If you are applying a V1 face pose to V2, turn off the Victoria2 morph at the bottom of the list in head. Its default value is 1.0. A V2 derived pose will address this morph. V1 does not have it.


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.