Thu, Sep 26, 4:58 PM CDT

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Sep 26 12:28 pm)



Subject: Deleting the PBMCC, PBMDC, etc.


maxxxmodelz ( ) posted Fri, 13 August 2004 at 2:37 AM · edited Tue, 27 August 2024 at 12:33 PM

Are these safe to delete, since I won't be adding any additional morphs to this character? I know DialCleaner will hide them, but whenever I reload the figure afterwards they reappear. I'm thinking of deleting those and saving the figure without them. OK or bad idea? :-?


Tools :  3dsmax 2015, Daz Studio 4.6, PoserPro 2012, Blender v2.74

System: Pentium QuadCore i7, under Win 8, GeForce GTX 780 / 2GB GPU.


Little_Dragon ( ) posted Fri, 13 August 2004 at 3:33 AM

If you're finished designing the character and don't intend to inject any more morphs, it's perfectly safe to strip the remaining blank channels from the CR2.



maxxxmodelz ( ) posted Fri, 13 August 2004 at 8:29 AM

Thanks LD! :-)


Tools :  3dsmax 2015, Daz Studio 4.6, PoserPro 2012, Blender v2.74

System: Pentium QuadCore i7, under Win 8, GeForce GTX 780 / 2GB GPU.


neilp ( ) posted Fri, 13 August 2004 at 9:27 AM

Have a look at my free morph dial cleaner in the free stuff section. It removes them for you... as long as you are finished adding morphs.


Svigor ( ) posted Sun, 14 November 2004 at 5:51 PM

I loaded V3 into P5, injected all body and all head morphs, saved the file as a pz3, and ran morph dial cleaner on it. Nada. 100 pbm morphs per body part after five hours of 100% cpu usage. Is there a way other than morph manager? If not, consider this a feature request for the ability to shift-click multiple files within morph manager. :) :(


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.