• Sam

  over 3 years ago

  Honestly, it's got potential, but completely and totally fails to deliver on it. And there's no documentation, so god help you trying to figure out anything useful.

  For example, there are these little {blend_file}, {blend_file_directory} type tags used in the master config. There's no list anywhere for what tags are available. Nothing but what's pre-filled in the UI. The Blendermarket documentation is to just install the addon. Thanks, I really thought the install was the hard part.

  As to control of your file output, that's a good joke. The plugin overwrites the output directory every time. I can't find a way to just tell this stupid thing what I want my file to be. You can name your output anything you want, as long as that name is Composite. You can sort-of control where it goes, but it's always going to be a mess.

  Want to output a still of frame 1500 and another at 1700? God help you. As near as I can tell, the addon will only use your current timeline position unless you specify animation. If you specify animation, you're back to less than square 1, where the frame number is appended to the file name.

  I've spent more time trying to set this up than it would take to render out what I what to render out by hand.

  MAYBE this tool is an exact fit for Polygoniq's workflow, but if you are anything but that? It's just not going to work or you're gonna have to change. For a batch-renderer output naming is everything, and this just crushes whatever you try to name your stuff to. Literally, I poked at the code. The name "COMPOSITE" is hard coded. Wouldn't it be great if we could use the name of the context or the camera? Something a little procedural?

  The bulk of the UI is good, it renders faster than Render+, it is do damn close.

  1 star rating for the lack of documentation, which had there been documentation, could have saved me 2 hours of trying to make this do what it's not coded to do.

• 

  polygoniq

  about 2 years ago

  Hi Sam, thanks for the feedback! Documentation has always been available via a google doc but since we received feedback that it's not up to par we did an overhaul and now we host a more comprehensive documentation at https://docs.polygoniq.com/renderset/1.7.0/
  It lists the variables, those are also listed in the Preferences UI although it is a small button so you may have missed it. Generally, renderset is designed to output into folders, not files.

  You can render frame 1500 and 1700 by having 2 contexts with different frame_current even if render type is still image. I tested this and it works for me. Please do check out renderset 1.7.0 which implements some of the ideas you mention here. You can now change the Composite name, although you cannot use variables there yet.

  We have a more involved output naming overhaul planned for renderset 2.0 but have to be careful with it because it will break existing files and we have a lot of those. So do our users.

  Hope this helps!
• Matteo

  almost 4 years ago

  Awesome time saver!

• Somayeh Ashtari

  almost 4 years ago

  Great addon! highly recommend

• Mitch Hughes

  almost 4 years ago

  Works great, just installed and started using, very straightforward to use, such a time saver well worth the price.

• Ian Dainton

  almost 4 years ago

  Really good potential but the saving conventions they use are really un-flexible The interface for setting up renders is great and setting different resolutions, worlds, etc is super easy. But the way the plugin saves the renders makes it not worth using... :(

• jChristophe Levet

  almost 4 years ago

  Very useful !

• Rafael Teruel

  about 4 years ago

  excellent!

• MinyeopChoi

  about 4 years ago

  Good!!

• Displaying ratings 11-18 of 18 in total

Purchase this item to leave a review!