green trees changed

Did something change between Enscape 2.7 and 2.8, or did the library assets get adjusted? Sure would be nice to have control over asset colors...

(image with the more saturated trees is rendered in April with 2.7, image with washed out green is rendered today. Some lighting adjustments are a little bit different, but not enough to cause such a significant saturation difference.)

Oh, I'm not saying I want the oversaturated green back necessarily, I just feel it went too far the other way. Of course - like you mention - having control over the color adjustment would be optimal. Hope that's high up on the development agenda

But I did want to ask a technical question - were the assets adjusted recently? (So it wouldn't make a difference to go back to an earlier version of Enscape, the trees would render less saturated regardless?)

This brings up another point. If the assets that were placed and rendered at one point in time get changed by you all, that breaks my ability to render consistent images. In this example above - I made some changes to the background site model, but everything else was supposed to stay the same. Now my renders don't look the same because of the de-saturated trees. (I tweaked the lighting a bit - but if I had used the same settings as before - the trees would be the only difference besides the minor model changes.)

My stop-gap request:

Would there be a way to time-stamp the placement of the assets so that the right version of them gets loaded when Enscape calls them up from your server? (As a work-around until such a time when we can customize asset colors.)