5
on: September 01, 2017, 07:03:48 pm
This might be totally wrong as I've not used specialization for a while and I'm going from memory, but ...
I think why this happens is because the Transform2D node resolution is set relative to the output size of your graph, and the output size of the graph is set to 256x256 by default. When you use sbsrender to render the outputs of the graph, the graph size is set to the resolution you use in the sbsrender commandline, and then the Transform2D nodes inherit that. So try just ignoring this issue, and use sbsrender.exe with the resolution you want and I think it should do what you want.
And if that doesn't work, you can do this the hard way -> the sbs are only XML format, so you can parse it yourself and find all the image input nodes, then find the Transform2D nodes that are connected to them and directly change them to be the absolute resolution you want directly in the sbs.