Renderjuice 2.4 was released on March 29, 2024

​
Key Summary

  • Improved file naming for downloaded render outputs, matching the name of the .blend file.
  • Enhanced performance and reduced load time for the application, resulting in over 30% improvement in time to first load.
  • Implemented better caching strategies to make the app more responsive.
  • Fixed an issue where the sidebar was not staying minimized or expanded.
  • Improved application styling during the validation and booting phases, making it easier on users’ eyes.
  • Fixed a strange edge case where the website app styling was intermittently getting removed, caused by an upstream dependency in the codebase.

​
Download File Output Names

When you used to download all render outputs from the application, the file names could end up being a little confusing, especially when you were rendering multiple scenes at the same time. The zip file output will now match the name of your .blend file so they’re easier to tell apart.

​
App Load Performance, Renders Page, Navbar

The renders page where you can see all your jobs should now better handle proper naming, particularly when they’re long.
We noticed the app payload was quite heavy for the frontend, so we’ve reduced bundle size by a couple points, but also drastically reduced the time to load for the application (>30% improvement in time to first load). The UI was also sending off a ton of requests that were unnecessary, so we’ve implemented some better caching strategies to make the app far more responsive on your end! We fixed an edge case where the sidebar was not staying minimized or expanded.

​
App Styling

We improved the look of the application during the validation phase and the booting phase, so it’s a bit easier on our users’ eyes. We’ve also cleaned our code structure a little bit, so that we can ship some upcoming features 😉. We fixed a strange edge case where the website app styling was getting removed out intermittently. It turns out the cause was one of our upstream dependencies in the codebase, so we’ve fixed that!