Mon, Dec 23, 2:44 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 22 10:18 pm)



Subject: In Poser 5, take the poser square....


smiller1 ( ) posted Fri, 12 March 2004 at 3:35 PM · edited Mon, 23 December 2024 at 2:20 AM

Attached Link: http://www.apvn53.dsl.pipex.com/Temp/Square%20Problem.jpg

file_102153.jpg

...put it into a scene and render. Do you get something like the image in the URL? More importantly, does anyone know how to fix this easily? I hav an object that is made up of loads of these squares and I can't use it in Poser 5 unless I can solve this problem!


ockham ( ) posted Fri, 12 March 2004 at 3:44 PM

file_102154.jpg

That's cool! On the left is the one-sided square, on the right is the two-sided square. Must be a SR4 "feature", or else there's a Martian trapped between the facets of the square, trying to send a distress message in visual Morse.

My python page
My ShareCG freebies


smiller1 ( ) posted Fri, 12 March 2004 at 3:48 PM

It's not an SR4 feature, I've always had this problem with Poser 5, but I've been able to avoid it...till now. I really don't want to rebuild the prop I made with these poser squares in Poser 4. I'm wondering if Poser 5 replaced the square's obj file. I may have to re-install Poser 4 to get the original object.


saxon ( ) posted Fri, 12 March 2004 at 4:06 PM

Isn't this the one where a tiny bit of displacement resolves the issue?


ockham ( ) posted Fri, 12 March 2004 at 4:09 PM

You got my curiosity roused... The OBJ files are identical in P4 and P5. The PP2 (after extracting from PPZ form) are also identical. So switching files probably wouldn't help.

My python page
My ShareCG freebies


saxon ( ) posted Fri, 12 March 2004 at 4:17 PM

file_102155.jpg

Yep, displacement solves it...


saxon ( ) posted Fri, 12 March 2004 at 4:17 PM

file_102156.jpg

and after...


Little_Dragon ( ) posted Fri, 12 March 2004 at 4:44 PM

I usually attach a Simple_Color node, myself.



stewer ( ) posted Fri, 12 March 2004 at 4:56 PM

In most cases, simply checking "remove backfacing polygons" in the render settings fixes it - no displacement necessary.


JHoagland ( ) posted Fri, 12 March 2004 at 5:07 PM

I've had this problem happen before. It gets really annoying when you use a flat square prop (with an image) as a background. If this is the same prop that was used in P4, why would "remove backfacing polygons" help? Isn't this prop just one polygon? (Hence the name "flat square".) How many polygons are in this prop and how could someone have originally built it with reversed polygons? --John


VanishingPoint... Advanced 3D Modeling Solutions


ynsaen ( ) posted Fri, 12 March 2004 at 5:15 PM

Jhoagland, it does work, though. The reason it happens is because P5 is trying to render the backfacing polys -- which there aren't any of, and so, nothing. however, I generally prefer to use the displacement option -- and no node is needed. It allows for a bit of speed.

thou and I, my friend, can, in the most flunkey world, make, each of us, one non-flunkey, one hero, if we like: that will be two heroes to begin with. (Carlyle)


stewer ( ) posted Fri, 12 March 2004 at 5:21 PM

The "square" prop are two polygons, the "one sided square" is only one polygon. The problem is that both polygons in the square prop are in exactly the same place (they share the four corner vertices), only facing in opposite directions (opposite normals). FireFly is trying to render both polygons, and due to the limited precision of 64bit floating point calculations, you get artifacts.


smiller1 ( ) posted Fri, 12 March 2004 at 5:22 PM

Thanks guys! I thought that maybe the obj file had been replaced or corrupted with the Poser 5 install, but it obviously isn't that. I'm off to bed now, thanks to you guys this problem won't kep me awake. :0)


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.