I've been making some test renders of some things I've been working on. I'm rendering over a background image and I keep getting a small area (1 or 2 pixels wide) at the top and left side of the rendered image that the background is showing through. The window is set to match the background image. I'm using Firefly with raytracing.. no IBL or AO. There aren't any gaps between the walls, ceiling or floor. I've tried changing the size of the rendered image and it still happens. The only way I've been able to stop it is to paste the background image on a plane and render that way. Any ideas or is this happening to anyone else.

Yes. In fact, I only saw this last night for the first time when I tried to render over a procedural background shader. Looks like it's another one for Poser 6 SR1!

fyi I've just reported this to CL and referenced this thread as your screenshot shows it so well.

A lot of people have commented on this issue. It seems to be consistent throughout platforms, as well. It happens no matter the background, and only one pixel along the left and top. I think they call it "render shift". As nigh insignificant as it is, I hope they fix it in the next release. Whereas cropping in an image editor is a simple solution, it shouldn't be necessary to do so.

I'd missed that discussion. I've been too busy wrestling with binary morph files that drop the morphs from figures saved to the library, and the ever present "You are out of memory, your scene has been trashed and the last six hours of work deleted for you" error ;) I will say that overall I'm very satisfied with P6. The Firefly renderer still hasn't been fixed, but at least it now tells you when it can't continue, unlike P5 which just sat in an infinite loop pretending it was doing something. Even this latest irritation isn't the end of the world, but it is one more to add to an ever lengthening list.

Yeah I noticed it to. The temporary fix IMO is to just render everything a few pixels bigger than your target size and then crop it in photoshop. kind of a pain though, and DEFINATELY needs fixed.

Thanks.. I never saw the threads where this was mentioned. Rendering bigger isn't an option when you are rendering an animation. Having to crop that many images would be real pain IMO.

You could do the cropping in your video editor, EdW. There's no need to do it manually to each frame. That's some nice work, by the way, although you need to adjust the UV-mapping along the sides of the countertops to make the tiling less obvious.

I've had this problem too. Go into your render setting and increase the texture size, that might fix some of it.

That's true LD.. I guess I'm just lazy and don't want to have to crop them:) and thanks for the comments. If you're interested in the model, the base model is a freebie for the members at one of those sites that I can't give the link to.

That can easly be fixed. Maybe you didn't move the scene by the Z min enough.

I can crop them all in Mirage very easily, Plus any decent video editor can do it. You can also do it with a photoshop action.

I finally got what you were saying. It's a bug in P6, you have to crop :(

"That can easly be fixed." akura_

Thats a bold statement for something that is a consistent cross-platform render issue. If you look closely at some of your own images (specifically the girl with the gun on the couch), you'll notice the one pixel grey band along the edge. The background ALWAYS (to my knowledge) shows through. If its easily fixed, please provide the necessary steps.

Message edited on: 04/19/2005 21:05

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2201159

EdW, this is a definite problem with P6. Above is a link to the thread I started awhile ago about the problem. I submitted a bug report to CL and CL replied asking me to make sure the drivers for my graphics card were the most recent and if that didn't solve the problem, to let them know and they would submit the problem to their techs. Well, my drivers are up-to-date and I replied back to CL letting them know this and that the problem still continues. I even provided CL with the above link so they can see the discussion about this problem. I have not heard any response since my last reply. I'm hoping this means they're hard at work on a fix. I'm keeping my fingers crossed:)