Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 23 1:20 pm)
Yup, that's what happens when you start an adventure in the rainy season and forget the TV :)
Yeah - no wonder she's grinning!
I purchased it this morning. Had to do the regedit fix because my path was still showing the old Metacreations folder. (CodeTwister you really have to fix that quick or you will be buried by bad press). Did some experimenting with my wrap and yes it works. Works well :)
I do need to ensure that I'm using it correctly, currently its making morphs for all the body parts, some of which I then have to delete. Anyone help me here?
It looks as though CodeTwister has produced a very valuable tool for those like me that produce clothing. I'm going to keep working with it. In the mean time I give it a thumbs up provided the registry glitch gets fixed.
I've been hearing people mention this Tailor, but I can't seem to find any information on it. Like Jarm, I don't have a clue what it is. PhilC, I still have the old MetaCreations path, too, so does this mean it only works with the CL version? I won't touch RegEdit with a ten foot pole! So far, I've only heard some comments in passing about this program, but no real information. Melanie
Codetwister unfortunately timed the release of his awesome tool with a get-a-way weekend with his family... so he is unavailable for comment or to fix the program... but I suspect he'll fix it up quickly. I suggested having a user definable field with a browse button to allow the user to manually locate the Poser.exe and tell the program where to look. Should be able a 10 minute fix for a coder like him.
The program automatically reads the figure morphs and builds them into the dress even though the geometries are different. Quite frankly its brilliant. The regedit thing is a glitch which I understand from reading an earlier thread, Code twister is now aware of and if fixing. I'm not a programmer but can understand the principles of what's going on. I don't think that CodeTwister or the store testers are to be panned for missing this, its just one of those things.
I don't blame you for not wanting to tread those mysterious registry corridors. I only did it because I had a good supply of garlic and ash steaks ready at hand. I suggest you wait a couple of days and purchase once its been fixed. But I would suggest that is the only reason you should delay.
Its my impression that CodeTwister has not got the same degree of internet access as some of us and also that English is not his first language. Hence his communication may be slightly hindered. I'm sure that folks will take this into consideration when reviewing forum posts on this subject.
This looks brilliant. Honestly, if it were out for Mac I'd buy it in a heartbeat, and I bet I'm not the only one. I always love to see new Poser stuff. I just wish more of it were available on my beloved Bondi blue translucent little platform. ;) I would love to hear about it if there's ever any considerations in that direction. I'm not a programmer myself, but there are some who are...
Attached Link: Link to other thread pic I'm not sure why the registry is like that...I didn't even have that Poser3file key (I had a pz3file key though). Manually creating the poser3 one worked fine for me. I'm guessing it has something to do with the version you first installed (i.e. Metacreations or Curious Labs) or something, and whether you reinstalled it to some other location later on. Anyway, PhilC from my experiments there's two ways to transfer morphs. 1. Select any morph and transfer it. If it would affect a neighboring area (like a Mike bicep morph that would "balloon" part of the forearm area), it will create morph dials in that adjoining parts too. It seems to be pretty generous about it though...making dials for even the slightest effect (the bicep morph would probably create a morph in the collar too). You can either leave those dials and turn them to carry the effect of the one morph through the area (almost like it makes the pbm dials for you), or delete the ones from the extra parts and transfer the individual morphs that exist in the model for each part yourself...again deleting the extra ones. For some things, the automatically created dials seem to work just as well so check them out before deleting. Could save some effort. 2. Select all the morphs in each body part that are usually slaved to one body morph dial, like pbmMuscular1 from Mike2, select the "like one body morph" option, then create the morphs in the clothes. This process takes longer, but it seems to recreate all the morphs without extra "interpretation" of how they might affect other areas. Too bad it doesn't make a FBM dial to control them. The effects are not always perfect. Lower rez to the clothing meshes is a factor, as is "non standard" parts to the clothes. For example, the link is a post of my trials with Mike Muscular3 and the Adventurer suit...note the problem with the cape. Still, the greatest thing since sliced bread if you ask me! Using default bodies with all the clothes or waiting an eternity for morphable versions is a thing of the past! Now what I really need is a tutorial that explains how to recreate a FBM dial and slave all those pbm dials to it in the clothing so I don't have to change each part one by one. There must be one somewhere...come one folks throw me a bone!
From the bit I've played with the program on my own clothing I seem to see several items that may affect clothing makers who want to use this... 1. The closer the clothing item follows the GROUP outlines of the target character the better. In other words the edge of the groups in the clothing should parallel the edge of the groups on the character, as close as possible. The "shape" of the mesh "inside" the group doesn't seem to matter except as outlined below. 2. A higher mesh "density" seems to translate into a "smoother" looking morph. Low density models seem to ripple badly when shrunk or expanded. 3. Triangulating the clothing object seems to help lower density items make a "smoother" morph, but not as much as a higher mesh count. The above observations are based on my own tests and observations. I am not affiliated with Codetwister in any way. In all this is an amazing program. I expect that, as it gets into wider use it will only improve. Codetwister has added a significant tool to the Poser community. mike
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.
Cause Michael's been at it again :)
www.ladyfyre-graphics.com