#347639
I rendered a first view out of Rhino5, up to SL11, then from the same Rhino file, I rendered a second view after stopping the first render and saving the MXI (in order to resume it later, at night)
After rendering the second for some hours, I stopped it and saved it's MXI too. Now I resumed the first MXI to render at night.

The first MXI now gives an image where the two files are visible at once... what's happening here? I've had this happen before!

http://www.flickr.com/photos/68335713@N ... hotostream
#347653
The second time you rendered, it wrote over the first MXS. So when you resumed the 1st MXI, it read from the MXS that was different. Make sure that if you plan to resume an MXI, you save an MXS with it that it will use to resume.
#349138
The problem is that you are resuming a mxi made from a different mxs with different geometry but the same name. So Maxwell thinks the mxs is the same (as it has the same name) but it is not; nevertheless it starts adding new light information to the old mxi that comes from the most recent scene file (which has different geometry).

Putting all together: Don't hit resume when you are not resuming anything but making a new render.
hardware question :)

I can easily create an usable render in 15/20 mi[…]

Maxwell for Rhino on Max missing Toolbar

Hello, For some reason, the Mac version of Rhino[…]

Let's talk about Maxwell 5.2

Price for sure matter a loot. Speed is the core i[…]

Materials translucent with V5.1

Well, the problems can be in the chair, the monito[…]