Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 25 9:50 pm)
Kiera-
That's not the issue. The issue is they are already smart props. Deformer sets like Wyrmmasters are great for Vicky 3 since they will also deform clothes. They also save memory since they allow me to use any clothes on v3 without creating MTs for each clothes item.
The problem is, when you save a scene with a v3 and then reload it using a magnet pack to deform her shape and the shape of the clothes, poser will duplicate the magnet channels for the clothes item when you reload the scene. So every dial is effectivily doubled, trippled, quadrippled etc.
This makes reloading a scene a huge, time consuming situation since I either 1) have to go back through and zero all the second, third etc dials (which can be like 8 per body part on each cloth item) or I have to delete the whole figure and reload it and pose it again.
This makes batch rendering completely useless since I can't set up a scene, save it, then start a batch file to render them in full size overnight since, upon loading, poser will duplicate the magnet channels.
Magnets make v3 viable for me. If I had to make MT sets for each clothes item I'd go nuts and the memory usage would go through the roof. This has been a bug in poser since poser had magnets and, wuite frankly, I don't understand why it would even arise. It makes no logical sense and so it probably can be easily fixed. CL has had at least four chances to fix this and have not done so.
Message edited on: 08/16/2004 11:03
When should I expect to see this bug? I ask because I have Poser 4.0.3.126, wherein I have loaded V3 with all morphs injected, upon which I have applied the Sarah Spriteling magnet deformers. This figure wears As Shamin's Lingerie 02 set, which has its own magnet set (and has the Sarah Spriteling set applied too). When I save a scene containing the above, it reopens the same as it was saved as far as I can tell.
Another issue with dupes(?) that bugs me a bit, is when I tell Poser not to continue searching for missing textures. After what can be a very long wait, Poser inadvertently tells me once again that it couldn't find the first missing texture, and asks me again if I want to continue searching. Sometimes it only takes a brief while after that to get back to the preview window, but sometimes it seems like the entire search for missing textures cycle seems to repeat itself again? Anyone know why?
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.
CL manager: "So, how can we make Poser 5 useless to professional people trying to produce material quickly?"
CL programmer: "Hey, I know, we'll duplicate every magnet channel on clothing attached to a figure upon loading of a scene so the user has to zero out 4 to 8 channels on each body part for each piece of clothing. And we'll duplicate them over and over and over upon each load. Plus the duplications won't have any real pattern to them so one of those smart aleck end users can't write an app or python script to go through, find the duplicate channels and remove or zero them. Imagine if they have like 4 figures in a room. Man they'll be screaming like mad."
CL manager: "Boy, that sounds good. But I assume we'll fix that after Poser 4 right?"
CL programmer: "Oh no. We won't fix it in pro pack, nor P5 revs 1 thru 3. That's the beauty of it. So now all those people trying to use high end figures without having to make MTs for all the clothes will have to constantly zero out channel after channel after channel. Plus we'll make setting the channel to 0 take like a second to 3 seconds, even on a 3 ghz P4. Or they can go through and delete all the clothes and figures and replace them in the scene. Now isn't that good?"
CL manager: "Yup, that'll make P5 almost useless to professionals who are trying to use our product for real work applications. Good thing we absolutely ignored any and all feedback from the renderosity community on the bugs that were really important to fix. Hey, this face room needs some more useless features that don't work."
Message edited on: 08/16/2004 00:28