Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 24 6:22 pm)
Attached Link: http://www.pygott.demon.co.uk/mapper.htm
There is a program called supermapper at the link that might fix this problem. Load the object into it and click on Action fix face normals and then, when that is done, resave the object.Poser doesn't use the normals in the OBJ file, so removing the normals (the 'vn' lines) won't help. Try using the group tool in Poser.... select only the offending facets then click the 'Reverse Group Normals' button. I agree with randym that 5 and 6 are usually fussier than 4 on this matter. In some cases like this, where Poser can get confused about what's inside and what's outside, I've had to rebuild the mesh as two "nicely closed" groups.
My python page
My ShareCG freebies
My python page
My ShareCG freebies
Well the first image was loaded in P4 and rendered in P4. The second image was loaded in P5 and rendered with the P4 renderer. I figured it best to compare apples with apples as far as renderers go. I have no clue why P4 is treating this obj differently than the 2 later versions of the program. If it helps any I created the obj in Carrara 4 as a spline for each strap and then exported as an OBJ. I've tried exporting as a 3ds and got the same results when I load/import into P4. David
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.