The above image shows a comparison between two (cropped) renders of the same scene:

• on the left, rendered directly in Poser Pro

• on the right, rendered with Poser Pro Queue Manager.

There are three obvious differences in the QM render:

1. The displacement bug at the bottom of the cylinder. 

2. The different spiral displacement mapping on the cylinder.

3. The different size/offset of the tiles on the backdrop, both vertically and horizontally.

The cylinder uses one of bagginsbill's Matmatic column shaders, unmodified. All my foreground renders interpreted this shader correctly.

The background uses a tile shader I am working on (to get correct reflections on the curved edges of the tiles). I carefully repositioned the tiles on the backdrop to get a mortar line along the floorline.

Just to be sure that the QM scene snapshot (which it saves before it starts to render) was not corrupted, I opened it in Poser and did a foreground render - it was perfect. This proves that the problem is not in the saved scene, but in the QM render process itself.

Does anyone know something about this already? Does Queue Manager use a different version of the 32-bit render engine to foreground renders in Poser Pro? Is it extra-buggy compared to the foreground render engine? These are my conclusions.

I'm on a Mac, using the 32-bit render engine. I have updated Poser Pro and Queue Manager to the latest release (SR1, for the Base version).

Thanks for any and all feedback!

(edit) just to clarify the difference in render quality... the left crop is from a smaller foreground render. However, I did try a foreground render at the same size as the QM render, and it came out fine.

Today I confirmed what I believed when I read you problem.  It's not really a bug or maybe it is.  Anyway you need to set the exact dimentions of your render.  if you want the full size of the document then set the exact size to that of your document, then the render will be what you see.