Chris Schubert
Posts: 1 |
Hello,
I'd like to be able to disable preview generation at the tab level, to optimize for exporting. I'll call a tab with preview generation disabled a 'virtual tab'. Exporting PBR maps of a large number of textures/variations is very challenging, and can not be automated. When I've already prepared my presets and want to export PBR maps, it would be nice to set up virtual tabs, with no UI rendering, and select filters and presets/settings. Without rendering, it's possible that there would be little overhead per tab - allowing dozens or more of tabs to be prepared. Then, via File > Export you could kick off the virtual tabs to render for output as you would normally. I think this could serve as a very adequate 'batch' concept, especially if you combined it with some kind of "Saved Tab(s)" concept. If you were able to export/import a tab or tabs via XML then you could almost hook this into an automated pipeline. If that XML was also compatible with the command line renderer, and the CLR was extended to be able to specific render channels - you're really off to the races with automation without significantly challenging the existing application design. Would love to hear what anyone else thinks. The lack of automation was frustrating me so I figured a feature request was more productive than being salty. |
|||
Posted: August 22, 2019 9:51 am | ||||
GMM
Moderator
Posts: 3491 |
If I understand you right, this functionality has been in the CLR since version 1.0. Would you please check out the corresponding help section: https://filterforge.com/more/help/Misc...derer.html |
|||
Posted: August 26, 2019 5:06 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+19 new in 30 days!
153,534 Posts
+31 new in 30 days!
15,348 Topics
+72 new in year!
77 unregistered users.