thanks for great script!
But, to make it really useful production tool, it would be great to implement some changes:
1. The resolution of the baked image is the same as your current project resolution. This is quite limitation factor, if you could implement a function which would do this:
a. you select a layer and hit script button.
b. script changes your project settings resolution by factor 2 - e.g. from 1920x1080 to 3840x2160 and then do the same as now and after putting the PNG in to your project, scales the resolution to 1920x1080 (original one) back.
c. it will setup the high-quality rendering on the PNG layer settings.
2. It would be great if the script could remember the hidden and showed layers before doing the rendering. So you select for example only BG Folder and the script will save the current composition settings, then hide everything else except the BG Folder, then do his job and at the end put everything back in normal – as it was before.
I would provide you with any help if you could implement those changes, we can even make some paid ob from it. We have a lot of ideas for new scripts. We can pay you for development of these.
PS: I created the icon for the script, you can use it of you like it
hayasidist wrote:http://www.mediafire.com/file/fx8avrl92 ... akePNG.lua
I think this is a pretty robust and just about functionally complete version... but give it a thrashing and let me know!
much of the wish list is implemented - including layer comps; but not yet scale up
Installation: copy the .lua to your custom directory (sorry - still no icon...)
activate with just one unlocked (=default state) vector / group selected: the PNG is rendered; the source layer is locked
activate on a locked vector / group: the PNG is made invisible and the source layer is unlocked for editing.
activate with multiple layers selected: a layer comp is created containing the selected layers; the layercomp is SET (i.e. everything else is made invisible); a PNG is created and a NOTE layer is created as a surrogate for the layer comp. The note layer is locked; the layercomp is DEACTIVATED (i.e. only the PNG and "non-render" Note layer are visible)
activate on a locked NOTE layer - the Note layer is unlocked; the layercomp is SET; and layers are available for editing.
activate on an unlocked NOTE layer (i.e. you can put the name of a pre-existing layer comp as the note text) - this is the same as multiple selected layers - i.e.the layercomp is SET; PNG is created; note layer is locked; the layercomp is DEACTIVATED
activate on a PNG: the same as activating on whatever created it.
activate with an unlocked source on any frame - you'll get a PNG for the frame on which it's activated (e.g. run on frames 0, 6, 30 - you get 3 PNGs). All the PNGs from the source are hidden when the source is open for editing.
right now a lot of the "options" that a user might want are hardwired ... e.g. path names to save the png (defaulted to the same as the .moho -- you'll be prompted to save the .moho if necessary); png file names (moho file name .. layer name .. uuid); layer comp names (from the active selected layer)...
Let me know ....