jit.gl.gridshape - gl_color not updating/modulating w/ [matrixoutput] enabled
This is probably something silly I'm overlooking, but I'm stumped.
In the attached patch, presets 1 & 3 are both functioning as expected. But presets 2 & 4 are giving me a hard time. [matrix output: 2, on with transform} is enabled, and the color modulation is not being passed through. The only way I can get the color to update is by toggling the shape, changing the dimensions, or toggling between presets 2 & 4.
I'm guessing there's maybe a bang or a trigger required somewhere that I'm not finding. I've tried connecting the 'render draw bang' to various inlets with no luck.
Any help is appreciated.
(Side note, possibly related... the cellblock attached to jit.gl.gridshape will frequently revert to displaying only one plane. I've hacked that by routing the 'render draw bang' to the (plane -1) message. Am I doing something wrong here?)
Hi, thanks for the report. I do see that colorplanes are not getting updated when matrixoutput is enabled and using glcore engine, whereas with gl2 engine they are. I'll make a ticket.
Curious what you're using this for, and why you can't send the 4 elements of color information directly to whatever you are coloring, as opposed to sending around a large matrix of duplicated cells of that same information.
Rob -
Thanks for confirming the behavior and filing the bug ticket.
Currently not trying to use this particular approach for anything specific. I'm just working through tutorials and trying to better understand what objects can/can't do, how they relate to each other, etc.. I do have a few specific ideas I'm working toward, but executing these ideas is going to require a much deeper understanding of MAX, Jitter, et al. Patience and baby steps...
Can you also confirm/deny the behavior of the [cellblock] connected to [jit.gl.gridshape] reverting to single plane display in that patch...? eg, by disconnecting the red patch cord between the jit.world bang outlet and (plane -1) message. Maybe that's related to the matrixoutput bug? Or a separate, additional bug?
Ok thanks for elaborating. Typically the matrixoutput data is uses as a geometry data source, e.g. for jit.gl.mesh, and you can color the mesh using the color attribute, or jit.gl.material.
The cellblock behavior is just a quirk of cellblock, something you'll get used to (or not).
"...matrixoutput data is uses as a geometry data source, e.g. for jit.gl.mesh..."
That's where I'm headed next. :)
"The cellblock behavior is just a quirk of cellblock..."
Good to know.
Thanks for the info and for your help.
Cheers!!