fsaa issue max 7.01 os 10.10.1


    Dec 11 2014 | 7:49 am
    I've got five new mac mini with os 10.10.1 and Intel Iris 1536 MB graphic card for an installation. I want to report a very annoying issue with fsaa which is not working on this configuration and max 7.01. If you try to set on the fsaa from an attrui object connected to a jit.window or a jit.gl.render, the box doesn't want to be checked. In the same way, if you try to send a "1" in a "fsaa $1" message box the numbox doesn't respond. In any case, even with a "@fsaa 1" argument, fsaa is not working.
    With a jit.world object, the fsaa can be checked but still not working.
    With max 6.1, everything is working fine.

    • Dec 11 2014 | 12:23 pm
      Yep! same problem here... but at least now you can use [jit.gl.pass @fxname fxaa]
    • Dec 11 2014 | 4:12 pm
      I was having this issue as well, but it is addressed here: https://cycling74.com/wiki/index.php?title=Anti-aliasing_with_FXAA
    • Dec 11 2014 | 6:41 pm
      Those solutions are ok when you have to render an GL scene in a texture. In my case, i have not any necessity to make a rendering, so it's too bad to lost my framerate to get the antialiasing... I prefer to switch back on max 6.1... I hope it will be repaired soon.
    • Dec 13 2014 | 1:10 am
      fsaa rendering is broken in 10.10. hopefully apple will fix this, but in the meantime, rendering to a texture with gl.node @fsaa 1 is your best bet, and should give similar fps.
    • Dec 27 2014 | 10:42 pm
      fsaa rendering is broken in 10.10. hopefully apple will fix this, but in the meantime, rendering to a texture with gl.node @fsaa 1 is your best bet, and should give similar fps.
      Can you explain this for someone who has never used gl.node before?
      I have a fairly simple patch that is using jit.gl.sketch to draw a 3D scene. The complex part of this is the 3D data is coming from a proprietary file format - which I am successfully reading in using js... but I really want to get fsaa rendering enabled.
      Here is my patch - minus all of the js...
      p.s. my 3D scene is made up purely of vector commands... there are no solid objects... only points and lines. Are there any settings which could optimize a scene like this?
    • Dec 29 2014 | 7:26 pm
      here are 3 additional ways to handle aliasing: jit.gl.render @high_res 1 (only available on Mac retina machines) jit.gl.node @capture 1 @fsaa 1 jit.gl.pass @fxname fxaa
    • Feb 18 2015 | 5:24 pm
      Hello, if I do [jit.world @capture 1 @fsaa 1] it seems to work. Is it ok to do like that ? What could be the problem ?
    • Feb 18 2015 | 6:34 pm
      this is the same as jit.gl.node @capture 1 @fsaa 1, so works fine.
      by the way, this issue is now fixed for the next update.
    • Feb 21 2015 | 6:01 am
      Just to clarify... next update of Mac OS or next update of Max?
    • Feb 23 2015 | 9:19 pm
      max