I've worked up a nifty background using TerraDome components in Poser Pro 2014.

The image is based on a set that I've used 4 times in the past, over the last 4 years -- so it's time tested geometry and camera settings, etc.

The only thing I've changed is the textures -- both on the ground and in the sky dome. There's also a water plane, as it's an island setting.

When I rendered it at the size of the Poser window, it's perfect.

So, I upscaled it to 3000x3000 and rendered. The top part looks great.

But, in the bottom 1/4 or so, some of the landscape -- which in the small render appears as just nice, reddish-to-black tones -- has become transparent somehow. So, I end up seeing the water and stuff below it -- mostly in the areas that were just smooth textured (red-to-black) on the smaller original.

I tried it at 2000x2000 and 1200x1200 with similar results -- though each time the area of error seemed to be getting smaller.

If I go back to the preview window -- with the same render settings -- its FINE again.

Anyone have ANY idea of what might be going on here?

Should I turn of the program, reboot, and reload? 'Cause that's about all I can think of to do right now.

Thoughts?

Solutions?

Suggestions?

Thanks!

-- Steve

When you re-size the PP2 or CR2, the Y scale also gets re-sized, so the enter item needs to be re-translated along the Y axis.

Are you saying that changing the output changes the size of the base files? And therefore errors are being introduced?

If so, how do I re-translate the foremost part of that picture/figure along the Y-axis?

Exactly what are you suggesting, and how should I do it?

Thanks.

-- Steve

I had assumed you were changing the size of the PP2 or CR2. If you are changing the size of the texture file or material node dimensions, that may introduce unexpected results in the final render. I can't tell what exactly is happening in this case.

Can you show us your renders? That may help immensely ... and whatever settings you changed in the size differences.

The only settings I've changed between the two are the render resolution -- from rending at the preview window size to rendering at 3000x3000.

No other settings were changed.

I'm attaching 3 pix. One is the original one -- which appears as it should. The 2nd is a reduced version of the 3k render. The 3rd is that reduction with the error areas marked -- most is below the white line near the bottom, but there's also a small "blocky" area that I've circled.

Hope this clarifies and helps you help me.

Thanks.

The funny thing is, the larger the render gets, the larger the error area seems to grow. Nothing at preview size, more at 1000x1000, even more at 2000x2000 (both attached, reduced to be the same size). And then the most, by far, at the 3000x3000 resolution I want to use.

Again, I have changed no other settings except the render size. I even tried turning off the RayTracing, to see if that would help, but it didn't. The size of the render seems, somehow, to be the key. I also moved the camera up slightly, wondering if maybe the height was somehow putting it below the surface of that front object -- but no luck.

And, again, I've used this same set (with different textures) with no problem. The only changes to the set are adding the volcano and its SFX and moving the tiny ships around on the bay. Plus the change of texture, sky zone texture, and lights.

But, again, what puzzles me is that it looks fine -- perfect -- in the small preview-sized render.

Help, please! (I'd like to get a genuine full-size render, rather than cobble together good and bad pieces in photoshop.)

Here's those 1000x1000 and 2000x2000 size renders.

Well, isn't that a quandary? ... ok, we have a challenge!

I ended up combing several versions to fix that bottom area (with reasonable tolerance), but I'd still like to know what's going on with it, so I can maybe re-render later.

And so it doesn't happen again.

Still welcoming thoughts. Thanks!

-- Steve

That should have read "combining" (not "combing").

-- SDS

sdsullivan posted at 11:33AM Fri, 08 July 2016 - #4274997

I ended up combing several versions to fix that bottom area (with reasonable tolerance), but I'd still like to know what's going on with it, so I can maybe re-render later.

And so it doesn't happen again.

Still welcoming thoughts. Thanks!

-- Steve