Don't know if this was addressed somewhere already, but has anyone else had a problem with Poser Pro 2010's background rendering? It keeps rendering an "old" scene, one that was previously loaded or has since chanced. The main render engine does not do this, and I've noticed this behavior on three different computers.

I have reported it and would like somebody else to also report it. I am on a Mac.
In my case I traced it down to the same prop being loaded multiple times that makes a call to the same object file. The prop came from a pp2 configured to work in Poser 5. The internal file name from Poser 4 and 5 when you have multiple props of the same item is not the same in PP2010. There is an extra colon that gets generated in PP2010, that it appears the internal render engine can deal with, but the background render engine can not.

I have not compared to Poser 6 or 7 and how a pp2 is saved off.

You can see what I am talking about by saving the prop off in PP2010 and compare the internal names. You can edit the version 5 prop file to be like the pp210 file and it will work. But that is way to much work based on the amount of older content I have accumulated.

Now I am at work and all my notes are at home. But if need I can be more detailed off my notes if needed.

I have this same problem and I'm currently working on it with Smith Micro.

 I've also had this problem and haven't found a reliable solution.  Like grichter I've found it has something to do with objects in your scene but I haven't been able to figure out exactly what it is.

In one case it was a hair figure and I had applied a mat a pose that was configured for P5.  After loading a PPro mat pose the problem disappeared.

Here is part of what I sent SM. It explains what I think might be happening with the internal names

I don't have Poser 5, so I can't verify. Oldest I have is 6. But it appears to be an internal naming problem in the product. I saved several of the props off in PP2010 and compared the pp2 files in textwrangler by barebones software. Here is what I see. The product is a mens bath room like you might find in a sports stadium and for example has 6 soap dispensers. So when you added 1 it rendered. When you added the second one it did not show up in the render. Look at the naming in the top part of the file and of course it would be off on the last line of the file or the add actor line. What I can not verify is this is how Poser 5 would have saved the props off or if the vendor edited the files and screwed them up. Notice the colons on the numbers. Change SoapDispenser1 1:1 to SoapDispenser1 1 and it works or as saved off from PP2010

This is from the product supplied pp2

{

version
    {
    number 5
    }
prop SoapDispenser1 1:1
    {
    storageOffset 0 0 0
    objFileGeom 0 0 :Runtime:Geometries:(rest of the line removed to protect the artist)
    }

prop SoapDispenser1 1:1
    {
    name Soap Dispenser 2

and this is the PP2010 saved off pp2

{

version
    {
    number 8.2
    }
prop SoapDispenser1 1
    {
    storageOffset 0 0 0
    objFileGeom 0 0 :Runtime:Geometries:(rest of the line removed to protect the artist)
    }

prop SoapDispenser1 1
    {
    name Soap Dispenser_2

I found a workaround for this problem -- at least for myself -- don't know if it will work for everyone.

If I go to the render tab, and then start the background render from there (instead of the preview tab), then I don't have the problem.

I can verify that works on my Mac

 That works for me too.  What a relief! Thanks.

I'll have to try that. It's very weird...I've noticed it will do that even after it a completely new scene has been loaded. Hopefully they get this fixed in the next SR.

I had an odd occurence in this area.  The other night, for no reason, PP2010 rendered my character's texture as the background image.   There were no props involved at the time, as I was doing a test render on the character herself.  When I left render window, the proper background image returned and was visible.  I haven't since been able to reproduce the problem.  Just thought I'd drop that in since it was a possible topic add-on.