So, I tried that -- but it kept the skewed Distance guide! Trying the other one in the article that allowed you to pick the character and body part to focus on. We'll see how that renders out.

But I'd still like an actual fix for the usual tool

-- Steve

hborre posted at 6:55PM Fri, 24 April 2020 - #4387121

I'm going to recommend a script that works very well and maybe better than the Focus Guide: https://www.renderosity.com/mod/forumpro/?thread_id=2945733. I have seen that behavior before but I did not pursue an explanation nor a solution. Anyway, click on the link in that post and eliminate the extension up to the .py. It works with any camera in your scene.

A friend suggested that maybe this happened when I accidentally created a new Dolly camera, deleted it, and the crated a new Rotating camera. So perhaps doing that again...?

But, while that may have caused the problem (not sure), doing it again DIDN'T restore whatever the DOF camera is focused on. :(

A friend also suggested that maybe I could solve the issue by creating a NEW BLANK document and then importing the "damaged" Poser scene into that document.

This did NOT work, either. So, clearly there's something "corrupt" in the existing files -- and no way do I want to re-create that whole set-up!

Nor did Restoring the Camera help. :-(

So, I'm still looking for help -- and hoping that the POSER PROGRAMMING CREW may be able to find and fix this bug in the next iteration.

hborre posted at 9:38PM Thu, 23 April 2020 - #4387121

I'm going to recommend a script that works very well and maybe better than the Focus Guide: https://www.renderosity.com/mod/forumpro/?thread_id=2945733. I have seen that behavior before but I did not pursue an explanation nor a solution. Anyway, click on the link in that post and eliminate the extension up to the .py. It works with any camera in your scene.

Okay, I found the gizmo you're talking about in FVerbaas post.

Where do I put it to get it to run in Poser 11?

-- Steve

Okay, I'll check that out.

Though I'm still hoping for an explanation and a solution, too.

With luck, the people tweaking the code currently may know something. Or some wizard out there may have found a solution and/or explanation.

Thanks!

hborre posted at 7:21PM Thu, 23 April 2020 - #4387121

I'm going to recommend a script that works very well and maybe better than the Focus Guide: https://www.renderosity.com/mod/forumpro/?thread_id=2945733. I have seen that behavior before but I did not pursue an explanation nor a solution. Anyway, click on the link in that post and eliminate the extension up to the .py. It works with any camera in your scene.

PS -- If I didn't turn off the IK, the feet stayed put when I relocated the figure -- which did some very weird things to the body.

I figured it out.

At some point, by accident, I had relocated the figure using the HIP parameter, rather than the BODY parameter. So, apparently, that made the point of rotation outside of the body.

To fix it, I had to undo Inverse Kinemetics (sp?) on both legs -- and then copy down the XYZ location from the HIP parameter (onto paper), and then zero those and transfer what I'd written down to the BODY XYZ location.

The figure now looks identical in the scene, but it rotates properly when I try to spin it. :-)

Thanks for your answer. It helped me figure out what the problem might really be, rather than what I perceived it to be.

-- Steve

Just tried that, and it didn't seem to work. The camera seems to be parented to the universe. Maybe it's not the camera, and only appears to be because I"m using a static photo for a background.

Is it possible that, somehow, the figure is being told to rotate around the wrong point in the Y-axis? Like the center of the scene or something?

How might that happen, and how might I fix it?

-- SDS

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

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

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.

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.

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

Yeah.  That did the trick.

Thanks so much!

I'll have to make a note to myself, so I don't forget between now and the next time I use it.

-- S

Yeah.  Okay.  That makes perfect sense.

I think I figured that out once before -- but that's the trouble with not doing these things very often.

So I need to turn off the other morphs and then re-save.

I don't think P9 has a morph brush.  (Not even sure the non-Pro 10 has.)

Thanks!

I'll let you know how it works.

-- Steve

Yeah, I have SR 3.3 installed, I think.

It was the latest, last I checked.

I had to reinstall late last year when the program stopped working entirely, so I cheked for updates then.

And I looked the other day, too, and didn't find anything newer than I had.