Forums > Jitter

poly_mode 2 and antialias 1 – Cannot render points as circles?

February 21, 2013 | 11:15 pm

Hi all. I've been having an on-going issue with the GL 'poly_mode' attributes since upgrading to Max6. What I want to do is to use 'poly_mode 2' (points) to render *circular* points in conjunction with 'poly_mode 1' (lines). I had this working in Max5 just fine using 'antialias 1.' But now when I turn antialiasing on (either to mesh, gridshape, etc., or even using fsaa) I can no longer change 'point_size.'

I've been returning to this problem on & off for over a year and I just cannot figure it out. I'm guessing it's an easy fix and I'm just missing something obvious.

I've pasted a patch that exhibits the issue as fully as I know how. And here's a link to a screen shot I took back when I had it working (also attached): http://gumielectronic.net/c74/polymode-21.png It shows exactly what I want to accomplish with 'poly_mode 2 1' and 'antialias 1.' I understand 'matrixoutput' and 'blend_enable' might play a role in this issue, so all pertinent controls are included in the patch.

I've scoured the forum for info but have turned up nothing. But the following posts address the fact that 'poly_mode 2' used to render circular points instead of squares when 'antialias' and 'blend_enable' are both set to 1.
http://www.cycling74.com/forums/topic.php?id=19449

http://www.cycling74.com/forums/topic.php?id=19375

I'm running Max 6.0.8
MacBook Pro 2.5GHz Intel Core i7
OSX 10.7.5
AMD Radeon HD 6770M 1024 MB

Thanks for any help the community is able to provide.

– Pasted Max Patch, click to expand. –

[attachment=215532,5056]

Attachments:
  1. polymode21.png

February 25, 2013 | 8:04 pm

this might be a bug with jit.gl.mesh, so i will investigate.
in the meantime, i think your easiest solution is to use @draw_mode points, and create a duplicate jit.gl.mesh objects that draws the lines, and sync transformations between the two.

jit.gl.node or jit.anim.node might help with this.


March 3, 2013 | 10:15 pm

Thanks for the workaround Rob. Please let us know if this is indeed a bug. It might make more sense for me to wait for the fix rather than re-work all my patches that fell over between Max 5 and 6. Appreciate your help!


Viewing 3 posts - 1 through 3 (of 3 total)