Mon, Nov 25, 3:38 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 25 12:38 pm)



Subject: Why is making a simple square with a transparency map a nightmare in Poser 9?


Talos ( ) posted Sun, 26 May 2013 at 11:01 PM · edited Mon, 25 November 2024 at 3:35 PM

file_494774.jpg

I like to do a trick where I separate the background and foreground of landscape photos by editing them in a graphics program, then I make a transparency map of the foreground for Poser and put something weird between the 2 layers like a dinosaur or UFO. This was easy in Poser 6. In Poser 9 the square only loads half the photo? And it renders with ugly black squares or picket fence patterns? In short, an ugly mess. I tried auto fit in materials, normals forward, and had to go back to Poser 6 in disgust. Poser 6 worked perfectly for this simple-minded procedure. Using Poser 6 again felt weird, but it worked. At least there was an option.


Talos ( ) posted Sun, 26 May 2013 at 11:02 PM

file_494775.jpg

Here's Poser 6. Simple. Automatic. Hassle-free.


heddheld ( ) posted Mon, 27 May 2013 at 2:57 AM

not got P9 so only a guess!! check the uv mapping of your square


ockham ( ) posted Mon, 27 May 2013 at 4:45 AM

file_494778.jpg

I don't think it's the UVmapping.  Here's a quick check inside P9.  The left square is the P4 square, and the right one is the P9.  Looks the same.  I also tried the P7 square, still the same.

I use squares for backgrounds all the time, and haven't noticed any problems in P9. 

Makes me wonder if your square prop somehow acquired some bad settings, such as the V Scale on its Image Map node?

My python page
My ShareCG freebies


kalrua ( ) posted Mon, 27 May 2013 at 7:32 AM

Normal forward/Two sided polygons.

 

Solutions

Edite Square----> Single sided

Or

Render setting---->Remove Backfacing Polys


icprncss2 ( ) posted Mon, 27 May 2013 at 8:28 AM

How Poser handles the alpha channel and render over background changed between P6 and P7.

In the old CP fourms and the old DAZ forums there were long threads about the changes.  Uli from EFrontiers kept stating that the changes were the "correct" and that the way P6 handled them was "incorrect".  To be honest with you, I never fully understood all of it.


stewer ( ) posted Mon, 27 May 2013 at 8:57 AM

Are you using the one sided square in P9? If not, try it. 


Talos ( ) posted Mon, 27 May 2013 at 3:46 PM

file_494787.jpg

Stewer is right. In P9 I have to make sure to use "one-sided square", not "square".

Thanks everybody! Embarrassing to get tripped up over something so simple.

 


bagginsbill ( ) posted Mon, 27 May 2013 at 8:10 PM · edited Mon, 27 May 2013 at 8:11 PM

I see you've got it now, but to be sure that all understand...

The Poser prop "one sided square" is a simple square.

Everything else is not. So if the title had been taken literally, the thread would never exist. Use the simple square, i.e. the one sided square.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


MikeMoss ( ) posted Mon, 27 May 2013 at 10:22 PM

Hi

Glad you got it figured out.

That's a useful effect, even in interiors, take a photo with the top of a chair, or other object in the foreground separate it, make a trans map and place and size it to fit in the correct spot when moved to twoard the front.

Place you character behind it and voile, you character looks like it's in the image not pasted in front of it.

Mike

If you shoot a mime, do you need a silencer?


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.