DiGiTaLFX

The following works absolutely fine in Max 5.

What am I doing wrong for it to work in Max 6?

max-6-capture-to-texture

hi there. The jit.gl.render @capture technique has been superseded by jit.gl.node @capture in Max6. jit.gl.render @capture was removed since it's really not the appropriate place to set capturing up. In Max6, jit.gl.node, which operates similar to jit.gl.render in that it objects can attach to it through its name and the node controls whether objects get drawn and/or captured. I've updated your patch to use jit.gl.node. The nice part is that it simplifies things quite a bit and makes it clearer what's happening:

hi there.  The jit.gl.render @capture technique has been superseded by jit.gl.node @capture in Max6.  jit.gl.render @capture was removed since it's really not the appropriate place to set capturing up.  In Max6, jit.gl.node, which operates similar to jit.gl.render in that it objects can attach to it through its name and the node controls whether objects get drawn and/or captured.  I've updated your patch to use jit.gl.node.  The nice part is that it simplifies things quite a bit and makes it clearer what's happening:


Seeing as this has changed, do you think it would be worth removing the capture attribute from jit.gl.render or if there is some reason for keeping it, maybe just throwing up a warning in the Max window when a user tries to change it? Then at least it would save some confusion.

yes. It's worth throwing an error. thanks for the suggestion.

yes.  It's worth throwing an error.  thanks for the suggestion.


Just a quick thought on this, I believe that with the old method it was possible to set fsaa to 1 on the invisible context to get antialiasing applied to the captured texture. As I can't seem to find any way of doing that with jit.gl.node, is the best method to give the node a dim of 2x or 4x the dim of the destination texture? This seems to give the desired results but isn't necessarily the neatest way of doing it.

This is effectively what FSAA is doing. Are you on windows or OSX? If on OSX, I'm surprised that FSAA would come in to play.

This is effectively what FSAA is doing.  Are you on windows or OSX?  If on OSX, I'm surprised that FSAA would come in to play.


I'm split across both really. But yes, you're right! I have just had a look at a few patches on OS X and fsaa doesn't work in that situation anyway.

my max5 patch also got broken by the removal of @capture from jit.gl.render. i got a bit confused trying to find out what was happening 'cause capture is still listed in the jit.gl.render reference. perhaps that should be removed?

btw, jit.gl.node looks mighty handy! now off to update my patches...

Max 6 Capture to texture.