<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<style type="text/css">.mceResizeHandle {position: absolute;border: 1px solid black;background: #FFF;width: 5px;height: 5px;z-index: 10000}.mceResizeHandle:hover {background: #000}img[data-mce-selected] {outline: 1px solid black}img.mceClonedResizable, table.mceClonedResizable {position: absolute;outline: 1px dashed black;opacity: .5;z-index: 10000}
</style></head><body style=""><blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">
<div dir="ltr">
<div> </div>
<div>> If we would get a more realistic Glass shader (at the same performance level), no one would complain that the render looks different (aka backwards compat breakage)</div>
<div> </div>
<div>No one would complain for a new projects he (or she) is working on. However, if you replace shader completely, then you'll most likely have a complaint.</div>
<div> </div>
<div>It does happen when during movie production when you need to go back to a shot a re-render some frames. If they'll look different you'll be screwed to re-render full shot. This even happened during open movies here in the studio.</div>
<div> </div>
<div> </div>
</div>
</blockquote>
<p>Usually you don't switch Software-versions during production. If you do on purpose then you are prepared to deal with changes. Once a project is finished it is tied to that software version, so if you're going to do some changes later, you dig out that old version of the Software (or you take your time to port it to a newer version).  </p>
<p>That said, minor version numbers should probably be consistent (e.g. the latest 2.7x can render render stuff done in 2.71). So best point for changes would be 2.8.</p>
<p> </p>
<p>Just sayin',</p>
<p>Thomas</p>
<div><br> </div></body></html>