Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 12 3:30 am)
I am not familiar with Cinema4D but check if you have non-planar polygons, if so triple them, check if you have polygons with the normals reversed if so flip them. You might have back to back polygons that need to be merged. Try to have only three point or four point polygons. Hard to tell without seeing the wireframe.
Dominique Digital Cats Media
Im not a expert with the Poser Grouper, but I read bloodsongs tut about fixing normals and I basically did like leather-guy suggested - no fix - In any case it took me longer to play with the grouper than to reconstruct the problem areas with a different approach (no use of booleans)like thgeisel suggested. I try to avoid it now - just would have been nice to use it some times... At one time I got so frustrated that I downloaded the trial version of Rhino and started digging through the interface. Maybe it
s the kick in the ass I needed to learn Rhino whick is I think a better choice for modelling for Poser Thank you all for your response! kelc
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.
In the picture you see the same prop.
On the left side (imported and textured obj.) before and on the right side after turning into a prop and reloading from library.
I modelled it in Cinema and exported to obj. I noticed this kind of disappearing with two other of my models. One common thing is that in the areas that don`t show up boolean operations were involved in creating the model. In Cinema everything is fine and normals seem ok. But in Poser !
Any clues to what went wrong during prop conversion -
Is it a Poser Problem?
Do I have to curse Cinema?
Or just simple human incompetence?
kelc