On analysis, when checkFramebufferStatus returns with something other than FRAMEBUFFER_COMPLETE, an error is thrown.
If an error is not manually thrown, an error would still pop-up no? If the if-statement is removed, the only thing lost is a bit of clarity (occasionally, I haven't ever bumped into this issue) for a 40% gain of efficiency.
Simply removing this if-statement speeds things up:
Howdy!
The function call of
checkFramebufferStatusintexture.jstakes about 37% ofdrawTocalls on Chrome, by my profiling:with_checkFrameBufferStatus.json.zip
On analysis, when
checkFramebufferStatusreturns with something other thanFRAMEBUFFER_COMPLETE, an error is thrown.If an error is not manually thrown, an error would still pop-up no? If the if-statement is removed, the only thing lost is a bit of clarity (occasionally, I haven't ever bumped into this issue) for a 40% gain of efficiency.
Simply removing this if-statement speeds things up:
without_getFramebufferStatus.json.zip
Perhaps I am missing something that
checkFramebufferStatusdoes, and if this is the case please let me know!Cheers, I adore glfx.js!