Thu, Nov 14, 9:42 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 14 4:48 pm)



Subject: Can't add character to library


Eclipse1024 ( ) posted Mon, 04 April 2011 at 2:34 PM · edited Wed, 23 October 2024 at 6:17 PM

I've ran into a bit of a snag with PP2010 that's got me perplexed.  I had done some heavy modification to Powerage's PowerCargo model (changing joints mainly) and have successfully saved the pz3 that includes the revised model.  Early on I had been able to add the model to my library but now that I've changed a few of the textures it's no longer working.

The pz3 is still loadable, I have no problem rendering the scene, and can duplicate the whole figure, but when I try to add the figure to the library the viewport turns black, poserpro.exe pins, and what gets added to the library is a 1mb cr2 file and an obj.  I end up having to kill the poserpro.exe process to continue.

What I find odd is that the cr2 works but one of the textures is stripped and the png file is missing, not to mention the crash the action of adding causes in the first place.

I don't want to have to redo all this work on a fresh model so I'm hoping someone has seen this sort of behavior before that can share insight.

UPDATE:  I took another look at the stripped texture and it actually wiped out the associated UV map for the group.  It's like the library-add didn't complete and some of the info is missing.


Eclipse1024 ( ) posted Mon, 04 April 2011 at 2:54 PM

Played a little more with it.  If I pop into the Setup room and back out without changing anything it wipes out on of the texture groups (along with it's UVMap) but it does allow me to save the figure to the library afterwards.

Anyone know a quick way of restoring the UVMap information for a given texture group?  I could drag the obj into UVmapper but I was wondering if there's a way to do it within Poser.


Eclipse1024 ( ) posted Mon, 04 April 2011 at 3:38 PM

So it didn't actually wipe out the UV information.  What ended up happening by entering the Setup room was a shuffling of just the material names, along with a wipe of all the details in 2 of the materials.  What I was expecting to be the propellor material actually ended up being the map3 material, and so on, so of course the UVs didn't match up. 

I now have it all sorted (other than materials being mislabeled) and the revised figure has been successfully added to the library.  I'd still like to know what strange events happened to have caused all this in the first place.


RobynsVeil ( ) posted Mon, 04 April 2011 at 3:40 PM

It would be interesting to take this cr2 into Poser File Editor to see if everything is where it is supposed to be, and if anything was added/deleted/renamed/otherwise-mucked-around-with.

Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2

Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand] 

Metaphor of Chooks


Eclipse1024 ( ) posted Mon, 04 April 2011 at 3:48 PM

I don't know enough about the CR2 files structure but I'm curious enough about this issue to learn.  I'll open up the bad and the good versions and compare.

Coincidentally, why would some figures be saved as just a very large CR2 while others are a CR2 with a OBJ file?  Does it depend on what was used to create the figure in the first place?  If so, how do these large CR2 files (that include geometry) get created in the first place?  Does it have something to do with the constituent PP2 props that it includes? 

I'm little mirky on how all these various files play together in Poser apparently.


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.