I am happy to accept change if change is required, but this has been cited as a documentation error, whereas it actually appears to be a decision made to longer operate surfaces in this manner. I think this needs a bit more attention in the forums as afaik for years the community had done this outside draw events, some recent examples including:
Icuurds tiling surface example often cited in other posts. I was myself pointed to this by Nocturne as an example of how to better manage large surfaces. This draws objects on their collision event before destroying them.
This one posted in March is an example where performing this in draw event specifically used to not work (GM8 i will presume).
It would seem having to call this inside draw events is going to make it more difficult to do a lot of the things people do with surfaces, such as acting as catchers for splats, scars etc. So perhaps some people could get together some examples of nice tidy ways to do this in the future? If this is changing the community has just lost a lot of best practice knowledge about how to use surfaces, and we will need some new examples on how to acheive certain things so new users arent confused by the conflicting information.
As a note to be fair, Mike had indicated a while ago he DID intend to change this in GM9 http://gmc.yoyogames...howtopic=522345, following a period where it wasnt supported in HTML5 either.
All I am saying is that I think it needs some attention here as a significant change, rather than a error in the documentation, so as people realise they shouldn't follow any of the examples on the forums any more regarding surfaces, and ensure they are implementing any projects in GMS with this in mind at the outset.
EDIT: the bug tracker ticket http://bugs.yoyogame...iew.php?id=3485
Edited by vann, 18 May 2012 - 03:11 AM.