The superSize parameter in Application.CaptureScreenshot() would need some documentation love. I just tried it out in our project, where we have a custom MRT setup with some custom post processing, and as it turns out, supersizing the screenshot does more than just increase the output resolution. (The resulting screenshot has the desired resolution, but suffers from weird sampling artefacts).
From the little documentation I expected the following: The frame is rendered as usual but with upped screen dimensions. I expect all stages of the pipeline to be triggered and all the callbacks fired. Pretty much just like rendering a regular frame.
Neither happened, so there must be some magic be going one behind the scenes. Documentation wise, its not so much important as to what that magic is, but at least, that there is magic involved and that it does more/less than just rendering the frame to a lager screen.
Happy to provide more context/info on this.
PS: Where should we post documentation issues? Here or submit them as a doc bug? We did that in the past, but it seams that nobody cared most of the time.
