Scene file prep when using Redshift
Redshift is cool, Redshift is fun, but using it on a farm requires some attention to detail.
First, and most important, is paying attention to the version of Redshift you’re using to create your scene file. We advise you to run the exact same version as we have deployed on the farm. You can find that version number by simply searching for “redshift version” in the search bar above, and selecting the page for the render app version that you use. If you follow any of our social media channels, we always announce version updates there, with pointers to our blog posts. We strongly encourage Redshift users to follow us on social media because of this.
Why do we recommend running the same version we have deployed? Due to the rapid development cycle adopted by the Redshift team, there is not enough time and testing done on any given public release to offer any assurance of compatibility with other versions, whether older or newer. We’ve seen all sorts of incompatibilities between even adjacent minor point releases, so you should not assume that there is a version that is “close enough” unless you are merely testing for compatibility yourself. Build and test render your scene file with the same version we have deployed, and that will eliminate an entire set of variables that can negatively impact output.
We are often asked about the use of Redshift proxies. We don’t enable or disable any sub feature of Redshift, so they will work as expected for the version being executed here. What is important to note, however, is that the proxy files must be pointed to using relative pathing from the scene file. None of the render app file path management tools will do this for you, so you must do this manually. Provided you implement relative pathing to point to those files from the beginning of your project, you won’t have to change them after that.