Thu, Feb 6, 4:12 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 06 11:58 am)



Subject: Misleading Texturing problem.


Robo2010 ( ) posted Mon, 14 August 2006 at 9:00 AM · edited Thu, 06 February 2025 at 4:04 PM

file_351007.jpg

In this image, shows an example, I see throughout my years using poser. I even encountered this from purchased products here and there. But today, while texturing after UVmapping these hangers I made many months ago. I find this problem, that appears that UVmapping didn't go so well, or did it? And their is nothing that can be done. When ever I see this problem, I always think their is something wrong, until after I render, all looks ok. This image is before rendering.


Robo2010 ( ) posted Mon, 14 August 2006 at 9:01 AM · edited Mon, 14 August 2006 at 9:02 AM

file_351008.jpg

Then after I render, I see this. Umm...ok...nothing to appear wrong,,,,why does this happen and how? Can this be fixed, and how.


dbowers22 ( ) posted Mon, 14 August 2006 at 3:28 PM

I've noticed if you use procedurals, such as changing the U and V coordinates on the
image node, that they often don't show up in the preview mode.



diolma ( ) posted Mon, 14 August 2006 at 4:33 PM

dbowers22 is right. Most of the Mat-room nodes (once you start twiddling dials in the non-root nodes) don't show up in Preview mode.

Preview mode is really just there for a fast response to changes/additions to objects/camera angles etc. in the scene, not for texture details. AFAIK, there is no fix for this.

And I have to say, I agree with that approach. Analysing the whole scene, including any/all material details would slow Poser (or any other similar app) down to a total crawl. Renders take a long time. That's 'cos they have to take all that into account. The preview is there to give a "general idea" as quickly as possible.
And even then it's not that quick..

Suggestion:
Load your object. Apply your material to it. Render. If the render looks OK, forget about what it looks like in the preview. Go ahead and alter your scene(add stuff, change camera angle, alter lighting whatever) til the general scene is more-or-less what you want. Once you've got the bits'n'bobs in position and got the camera angle right then you have to render (s-l-o-w-l-y) and start adjusting the lighting... ('cos it never matches the preview..)

Getting the set-up correct is the 1st step. Getting the finished pic takes a long time (and involves many renders)...
It's always been that way. In any app.

Cheers
Diolma



Robo2010 ( ) posted Mon, 14 August 2006 at 5:31 PM

file_351046.jpg

The reason I asked, is from the obvious I found today. In this image you can see everything is ok in the preview. But one part really stands out, looking out of place. If I were to give stuff as freebies or even market something (if so), I just do not want to get emails stating.."What is wrong with this?", when thier actually isnt anything wrong.

 

 


Robo2010 ( ) posted Mon, 14 August 2006 at 5:32 PM

file_351047.jpg

My renders do not take long. But here is an after render.

 


Robo2010 ( ) posted Mon, 14 August 2006 at 6:21 PM

file_351052.jpg

Did another render for fun of my AirBase.


nruddock ( ) posted Mon, 14 August 2006 at 6:23 PM

Seeing a wireframe and the UV map might provide some insight.


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.