Render frame composition consistency

I’ve got a kindof frustrating job. A client insisted I use flamingo for this job to be more consistent with some previous imagery.

I previously did a series of renders of their product with various color schemes. Their website has a utility to allow the user to pick various material combinations and the site then pulls the correct render from a matrix. (I did a lot of combinations.)

Now they’ve added some new colors and I need to go back and render the new combinations.

The problem I’m having is that the renders aren’t composed identically… i.e. the image jumps around in the frame when switching between the new and old images.

I’ve determined this is because my toolbar setup has changed since I did the originals. I don’t fully understand how given a fixed image size and fixed camera position this is even possible.

Is there a way I can get the original exact composition without a ton of trial and error f*cking around with my toolbars?

And is there a way I can avoid this problem in the future if they add more colors down the road?

It sounds like an issue of your viewport size is getting pushed around by toolbars making the viewport that you are rendering from not identical to the previous ones.

You can force this by getting the resolution of your originals, making sure you’re rendering at the same height and width. You probably are. Then make sure that your viewport is the same size as the rendering or some fraction of this size if it doesn’t fit on your display. You can also import the views from your old file to make sure the camera is set the same.

How do I set the viewport size to a specific size?

When you do not have anything selected in a particular viewport, going to Properties will give you all information on the viewport, camera, target, and wallpaper. The viewport properties are title, width, height, and projection. You can change the width and height in those fields.

Thanks wim, I don’t mean to be dense but my viewport properties window reads out the width and height but they aren’t editable fields. Maybe I’m missing something.

Must be the latter :grin:

It’s only editable if the window is not maximized - otherwise it’s “stuck” to available space given to it by Rhino…


Thanks for that additional piece of information, Mitch. I didn’t think of that. I mostly use it on free floating viewports…

OK great. Many thanks guys.