Sun, Dec 1, 6:32 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 29 7:57 am)



Subject: Severe Poser 7 rendering bug


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 11:45 AM · edited Thu, 28 November 2024 at 12:03 AM

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?message_id=3256425

file_409276.jpg

I have Poser 7, which I recently upgraded to Poser 7 0 2 132 using the downloadable upgrade: as advised in the thread at this link.

This is a simple test job, display view. The only object is the two-sided square prop, posed with these settings:
square_1    0    scale    Spline    1.0000    10
square_1    0    xScale    Spline    1.0000    7
square_1    0    yScale    Spline    1.0000    8
square_1    0    zScale    Spline    1.0000    9
square_1    0    yrot    Spline    0.0000    2
square_1    0    zrot    Spline    0.0000    3
square_1    0    xrot    Spline    90.0000    1
square_1    0    xtran    Spline    0.0000    4
square_1    0    ytran    Spline    0.0000    5
square_1    0    ztran    Spline    -3.3790    6

Its diffuse color is red=0, green=128, blue=255, with the ground texture map.It looks OK in display, as here.


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 11:47 AM

file_409277.jpg

This is the same, rendered with Firefly.


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 11:50 AM

file_409278.jpg

This is the same, rendered in Poser 7 with the Poser 4 renderer.

This persistent misbehavior is badly crippling my rendering. What should I do? It did not happen anything like so severely before I applied the upgrade mentioned above.

I have run my Windows Vista's defragmenter several times, but it does not show whether it has run through and done its job or not.


Khai ( ) posted Mon, 30 June 2008 at 12:15 PM · edited Mon, 30 June 2008 at 12:16 PM

goto the material and turn 'Faces forward' to ON.

that'll remove it.

it's caused by a zero thickness 2 faced object - both faces are trying to render in the same area.
Turning Faces Forward to on stops this happening.

it's in the manual. I suggest reading it sometime?


ockham ( ) posted Mon, 30 June 2008 at 12:23 PM

An easier solution: don't use the two-sided square.  In nearly all cases the
one-sided square will do the job ... and if you need to show different textures
on both sides of a sign or billboard, just use two different one-sided squares facing
opposite directions.

My python page
My ShareCG freebies


nghayward ( ) posted Mon, 30 June 2008 at 3:05 PM

Quote - goto the material and turn 'Faces forward' to ON.

that'll remove it.

it's caused by a zero thickness 2 faced object - both faces are trying to render in the same area.
Turning Faces Forward to on stops this happening.

it's in the manual. I suggest reading it sometime?

 

If you are struggling finding it the actual node is labeled "Normals_forward". You'll have to go to the advanced tab to find it.


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 4:19 PM · edited Mon, 30 June 2008 at 4:24 PM

file_409282.jpg

Thanks. I tried the one-sided square, and this is the result rendered in my Poser 7 with the Poser 4 renderer. (The display view looks about the same.) The square prop is posed thus: square_1_sea    0    scale    Spline    1000.0000    10 square_1_sea    0    xScale    Spline    3.0080    7 square_1_sea    0    yScale    Spline    1.0000    8 square_1_sea    0    zScale    Spline    1.0000    9 square_1_sea    0    yrot    Spline    0.0000    2 square_1_sea    0    zrot    Spline    0.0000    3 square_1_sea    0    xrot    Spline    -90.0000    1 square_1_sea    0    xtran    Spline    -1.3953    4 square_1_sea    0    ytran    Spline    0.0600    5 square_1_sea    0    ztran    Spline    3.6980    6


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 4:22 PM · edited Mon, 30 June 2008 at 4:23 PM

file_409283.jpg

But this is the render with Firefly. Note the blank area. The blank area does not correspond with the ground plane, because in this render the ground plane is default size. How can I make my Firefly behave properly here?


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 5:14 PM · edited Mon, 30 June 2008 at 5:15 PM

if I use the GROUND prop as the ground, scaled and textured as described above, if I set it to display, it does not show at all, or it appears in the display but not in renders.


Santel ( ) posted Mon, 30 June 2008 at 5:47 PM

Hi, make sure 'shadow catch only' is unchecked for the ground plane.

Regards...


Anthony Appleyard ( ) posted Mon, 30 June 2008 at 9:55 PM · edited Mon, 30 June 2008 at 9:57 PM

file_409296.jpg

*Hi, make sure 'shadow catch only' is unchecked for the ground plane.*

Thanks: that worked.

A remaining minor query: this cutout from an affected image shows a boat's nameplate as a small prop textured from a 61 x 470 texture map. In the Poser 4 renderer the name shows sharp, as intended. In Firefly the name shows badly blurred, as here. Please how to cure this?


Touchwood ( ) posted Mon, 30 June 2008 at 11:08 PM

 Try turning texture filtering to none in the material room. P7 defaults to quality which gives a blurry result.


bantha ( ) posted Tue, 01 July 2008 at 12:13 AM

If turning off texture filtering does not help with the sharpness, please reduce the shading rate in the render options. The default value isn't very good, reduce it to 0.2 or even 0.0 for renders which seem to be too blurry.


A ship in port is safe; but that is not what ships are built for.
Sail out to sea and do new things.
-"Amazing Grace" Hopper

Avatar image of me done by Chidori


Anthony Appleyard ( ) posted Tue, 01 July 2008 at 12:51 AM

Quote -  Try turning texture filtering to none in the material room. P7 defaults to quality which gives a blurry result.

Thanks, it worked.


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.