This page is only visible to admin users. Sorry!

This page is only visible to signed in users.

Contact <link>support@cycling74.com</link> if you believe you're seeing this page in error.

You don't have permission to view this page.

Activity

Billing History for { name }

Licenses

There was a problem removing the addon. Please try again.

Are you sure you would like to remove the <name>{addonName}</name> addon from your Max subscription? Your {addonName} addon license will remain active until the end of your current billing cycle.

{name} was successfully removed from your Max subscription.

Remove Addon

There was a problem resuming your subscription. Please try again.

Are you sure you would like to resume <name>{addonName}</name>? Your billing cycle will be reactivated and you will be billed as normal on {renewalDate}.

Your subscription has been successfully resumed.

Resume Subscription

There was a problem cancelling your subscription.

Are you sure you would like to cancel <name>{licenseName}</name>? Your license will remain active until <expiry>{expiryDate}</expiry>, at which point your subscription will expire and the license will be deactivated.

Your subscription has been successfully canceled.

Cancel Subscription

Next, start up the Max application and sign into your account (Help > User Account and Licenses).

Max has been successfully activated.

You must be signed into your account to activate Max.

Activate Max

Create a New Post

Edit Article

The list of what we're discovering about Max and our users grows each day. We tackle everything from hardware reviews to re-reading books from decades past.

Get the Latest on Max and our Community

Articles

Sign Out

Sign in to authorize License

Authorize Max

Filter by Format

Filter by Language

Find books related to learning Max.

Books About Max

Here are the artists and educators helping people get creative in Max

Meet Our Max Certified Trainers

Certified Trainers

{ firstName } { lastName } - Certified Trainer

There are no open positions at this time.

Please check your inbox for further instructions.

Forgot Password

Error

Success

Actions

Create Forum Topic

Edit Forum Topic

{category} Forum

There was an error submitting your details. Please try again.

Thank you for your submission! Someone will be in touch with you soon.

NFR / Industry Accomodations

Please make sure you use the link you received by email.

There was a problem retrieving your invitation.

Your account has been successfully created. To manage your institutional licenses, please go to <authLink>https://auth.cycling74.com</authLink> and sign in with your newly created account.

You must be signed out to view this page.

Create an Account

Find more details on our <link>Status Page</link>.

Under Maintenance

We are currently carrying out a scheduled maintenance of our website. Some functionality is temporarily unavailable. We appreciate your patience.

Name

Sort By

{ category } Packages

Share a Max Project

Edit Project

Image Notes

Important Notes

Max Projects come in all shapes and forms. Over the years, our users have shared over a thousand ideas and projects with us. We're proud to showcase them here.

Find Inspiration from other Max Users

Cycling '74 will review it within a week and may make minor edits before publishing it, so your project looks best and reads well in our project gallery.

Thank you for your submission! Your project is currently pending.

Account Recovery

Bundled

{ name } { version } Release Notes

There was a problem changing your password. Please try again.

You can now <link>log in</link> with your updated credentials.

Your password was changed successfully.

Reset Password

Your purchase has now been linked to this account. Next, start up the Max application and sign into your account (Help > User Account and Licenses).

Retrieve License

Type

Search the Cycling '74 forums and website

Search {query}

Please enter your educational details

Your Max for Live or Live Suite serial number is required for this purchase. <link>Need help finding your serial number?</link>

There was a problem updating your subscription. Please try again, or contact support@cycling74.com if the problem persists.

Cannot add RNBO

Confirm Subscription Addon

Thank you for your purchase

Thank you

Retrieving your order details, please wait...

Contact <link>support@cycling74.com</link> if you have questions/issues.

Couldn't sign in. Please check that your username/email and password are correct.

Sign in with your Cycling '74 account

There was a problem creating an account. Please try again.

Successfully created your user account! Please check your email for one last verification step.

Create a Cycling '74 account

Select a Product

Thank you! Your request has been successfully submitted to our support team. Please check your email.

There was an error sending your application. Please try again.

There was an error sending your request. Please try again.

By submitting this iLok request, you understand that you will be notified when an asset is deposited to your iLok.com account. After receiving that notification, you can transfer the asset to your iLok USB stick. Please be aware that all iLok requests are manually processed so it can take up to 48 hours to fulfill your request during normal business hours (Monday-Friday, 9am-5pm Pacific Time).

Important Information

Thank you! Your request has been successfully submitted.

Please note that we are no longer taking submissions for Tools and no longer supporting the Tools section, so you may run into broken files and URLs. You can contribute to the Cycling '74 Community by submitting a Package or using the forums instead.

Max Tools Archive

Edit Tutorial

Tutorials are an ideal way to accomplish a task, learn a new strategy or brush up on your skills. In addition to our in-app Examples, Tutorials and Help Files, you can find new ones here.

Explore the Online Tutorials

Tutorials

Thank you. Please start Max and sign in to use your license

Upgrade

Sign In

Your account requires verification. Please check your inbox, or <link>click here to send the verification email again</link> if you didn't receive it.

Unverified Account

Do you have an activation code?

Already own Max 8 and ready to authorize?

Trouble? Please email <link>support@cycling74.com</link> for help.

If you're new to Max, this is just for you.

Thanks for verifying your account!

You're one step closer to being part of the Cycling '74 Community.

Verify Your Cycling '74 Account

Failed to request a new verification e-mail: {message}

A verification email has been sent to { email }. Please check your inbox.

Can't find your verification e-mail or only have an expired one?

There was a problem verifying your email change. Please try again.

There was an error verifying your email address.

Your email address has been successfully verified. Thank you!

Verify Your Email Address

A user token is required to verify your email address. Please follow the link you received via email.

Matteo Marson

I don't know about you, but when I get syntax errors in shaders, they're mainly in the XML tags. This happens because syntax problems in this part of the shader aren't well reported in the Max console, and thus, it's very easy to misspell some words and get crazy trying to find where the mistake is (at least for me...).

I edit my shaders in Sublime Text, and for the reasons above, I decided to put together and share a package that highlights jitter-specific syntax in Sublime Text.

 (if you haven't already). You can find the software at 

. Just download the correct version for your OS and install it.

Open Sublime Text, then go to "Tools" -> "Command Palette..." in the menu.

This message should confirm the success of the installation.

. Open again the Command Palette, type: "Package Control: Install package", and press Enter

, then  type "GLSL" and click on "OpenGL Shading Language (GLSL)."

4) Editing the default GLSL syntax highlighting. 

Once again, open the command palette, type "Package Control: Install package", press Enter, then type "packageResourceViewer", and press Enter.

For the last time, open the Command palette again,  type: "packageResourceViewer: Open Resource", and press enter.

Then scroll down and select "OpenGL Shading Language (GLSL)."

and finally, select "GLSL.sublime-syntax."

This should open a document. Leave it open and go to the next step.

As the title suggests, unzip, open the file, select everything, and copy. Then, go back to the file GLSL.sublime-syntax, still open in Sublime Text, select and delete everything, and paste. Finally, save this modified version, overwriting the original.

If everything works correctly, whenever you open a .jxs, .jxp, or .glsl file, it should look something like this:

Note: If you must return to the original GLSL syntax package, download it again.

I hope this package can be helpful for you as it is for me. 

No longer stupid syntax errors in the XML tags! 

[EDIT: updated to Max 9.0.5]

Hello, Jitterheads!

I don't know about you, but when I get syntax errors in shaders, they're mainly in the...

sharing-jitter-shader-highlighted-syntax-for-sublime-text

[SHARING] Jitter shader syntax highlighting for Sublime Text

This is a list of the built-in uniforms available in Jitter shaders in Max 9

type="mat4" state="MODELVIEW_PROJECTION_MATRIX" 

type="mat4" state="PREV_MODELVIEW_PROJECTION_MATRIX"

== the previous frames modelview-projection matrix

type="mat4" state="VIEW_PROJECTION_MATRIX == 

type="mat4" state="CAM_PROJECTION_MATRIX"

 == (gl3 only) Provides the current rendering camera projection matrix; in most cases is equivalent to PROJECTION_MATRIX except in cases where a full-screen quad is rendering, e.g. in a jit.gl.slab/pix (or jit.gl.pass)

== Transforms normalized texture coordinates into rect coordinates

== the spotlight cutoff in degrees (=spotlight angle)

== exponent implied in the reflected light calculation

== gives the values from the @mat_X attributes of the 3Dobj to which the shader is attached.

== (where "n" is an integer number) Nth custom vertex attribute

== time elapsed since the shader has been compiled

== time elapsed since the rendering context has been activated

== time elapsed between successive frames

== view-space normals (rgb) + normalized depth (a)

== The currently active environment map, accessible as cubemap

== 4 layers of depth values (first front-face, first back-face, second front-face, second back-face). Depth is represented by the z coordinate of the view-space fragment's position (negative)

 == the roughness (r) and metalness (g) values. Works only when jit.gl.pbr is used for shading

once in a while, looking inside jitter shaders, I discover some new GL3 built-in uniforms never saw before. Sometimes, they provide the answer to problems I didn't know how to address before. I looked inside the jitter documetation, but I didn't find an exhaustive list of all the avaiables built-in uniforms. I know many of them can be found in the GLSL  documentation out there, but i'd love to have a comprehensive list of what Max and GLSL can offer to let the users build their own shaders. Here there are the uniforms i met so far and what i understood about them:

MATRICES:
type="mat4" state="MODELVIEW_PROJECTION_MATRIX" == P * V * M
type="mat4" state="PREV_MODELVIEW_PROJECTION_MATRIX" == the previous frames modelview-projection matrix
type="mat4" state="VIEW_PROJECTION_MATRIX == P * V
type="mat4" state="MODELVIEW_MATRIX" == V * M
type="mat4" state="VIEW_MATRIX" == V
type="mat4" state="WORLD_MATRIX" == transforms into world coordinates
type="mat4" state="PROJECTION_MATRIX" == P
type="mat4" state="CAM_PROJECTION_MATRIX" == (gl3 only) Provides the current rendering cameras projection matrix; in most cases is equivalent to PROJECTION_MATRIX except in cases where a full-screen quad is rendering, e.g. in a jit.gl.slab/pix (or jit.gl.pass)
type="mat3" state="NORMAL_MATRIX" == it orients the normals in eye space
type="mat4" state="TEXTURE0_MATRIX" == Transforms normalized texture coordinates into rect coordinates

CAMERA:
type="float" state="FAR_CLIP" == Camera far clipping distance
type="float" state="NEAR_CLIP" == Camera near clipping distance
type="vec3" state="FAR_CORNER" == far corner of the view frustum
type="vec3" state="CAMERA_POSITION" == camera position in world space
type="vec3" state="CAMERA_DIRECTION" == camera direction in world space
type="vec2" state="VIEWPORT" ==  the pixel size of rendering window
type="vec2" state="INVERSE_VIEWPORT" == the inverse of the viewport dims

LIGHT:
type="mat4" state="LIGHT_VIEWPROJ_MATRIX0-7" == scene seen from the light position???
type="float" state="LIGHT_RANGE0-7 " == distance reached by the light
type="vec3" state="LIGHT0-7_POSITION" == position on the light
type="vec3" state="LIGHT0-7_DIRECTION" == direction of the light
type="vec4" state="LIGHT0-7_AMBIENT" == ambient light color
type="vec4" state="LIGHT0-7_DIFFUSE" == diffuse light color
type="vec4" state="LIGHT0-7_SPECULAR" == specular reflection color
type="float" state="LIGHT0-7_CUTOFF" ==  the spotlight cutoff in degrees (=spotlight angle)
type="float" state="LIGHT0-7_EXPONENT" == exponent implied in the reflected light calculation

MATERIAL:
type="vec4" state="DIFFUSE" == material diffuse color
type="vec4" state="AMBIENT" == material ambient color
type="vec4" state="SPECULAR" == material specular color
type="vec4" state="EMISSION" == mterial emission color
state="FRONT_MATERIAL" == gives the values from the @mat_X attributes of the 3Dobj to which the shader is attached.

VERTEX:
type="vec3" state="POSITION" == XYZ Position
type="vec4" state="COLOR" == RGBA Color
type="vec3" state="NORMAL" == Normal vectors
type="vec3" state="TANGENT" == Tangent vectors
type="vec3" state="BITANGENT" == Bitangent vectors
type="vec3" state="VERTEX_ATTR" == Custom vertex attribute
type="vec3" state="VERTEX_ATTRn" == (where "n" is an integer number) Nth custom vertex attribute
type="float" state="EDGEFLAG" == unused, ignore

TEXTURES:
type="vec2" state="TEXDIM0" == XY Dimension of texture 0 type="vec2" state="TEXCOORD" == XY texture coordinates

These are the built-in uniforms i know. I ignore the meaning of some entries in this list and I guess I'm still missing some of them. Could you please integrate the list with the uniforms you know? I will edit this first post adding the entries you provide, so to keep everything compact.

It would be very usefull if an analogue list were done with built-it variables.

Hope this could be usefull to you as much as it is to me. 
Thank you very much!

This is a list of the built-in uniforms available in Jitter shaders in Max 9

MATRICES:
type="mat4" state="MODELVIEW_PROJECTION_MATRIX" ==...

exhausting-list-of-all-the-built-it-uniforms-avaiable-in-jitter-shaders

Thank you for this Matteo! 
You are right, the MODEL_MATRIX doesn't exist. The Model Space is just the position of the vertices as they come from inside the model, in which usually the 0,0,0 is the center of the model itself. 
If you need the coordinates in WORLD SPACE you can use the WORLD_MATRIX built-in.  

FRONT_MATERIAL will give you the values from the @mat_X attributes of the 3Dobj to which the shader is attached. 
layout (std140) uniform FrontMaterialParameters {
				MaterialParameters frontMaterial;
			};
Check the shader generated by the jit.gl.material object with the get_gl3_shader message to see how this works. 
You probably know this already but maybe can be useful for others: in the Max documentation "Appendix C: The JXS File Format" one can find all the built-in variables for the GLSL jxs shader format.  

Thank you very much Federico!
I honestly missed that appendix...I added the missing entries in the original post, but some are still a bit obscure to me:

type="mat4" state="PREV_MODELVIEW_PROJECTION_MATRIX" == ???
type="mat4" state="CAM_PROJECTION_MATRIX" == This one doesn't exist in the documentation, but i found it in mrt.ssao.render.gl3.jxs
type="vec3" state="FAR_CORNER" == far corner of the view frustum???
type="vec2" state="VIEWPORT" == ???
type="vec2" state="INVERSE_VIEWPORT" == ??? 
type="float" state="LIGHT0-7_CUTOFF" ==  spot light falloff???
type="float" state="EDGEFLAG" == ???

Ok so I think I can only add my contribution with VIEWPORT, which is simply the size in pixels of the rendering window. 
Keep it up Matteo! GLSL needs to be demystified

PREV_MODELVIEW_PROJECTION_MATRIX - the previous frames modelview-projection matrix, used for velocity based effects (e.g. jit.gl.pass @fxname motionblur)

CAM_PROJECTION_MATRIX - gl3 only, provides the current rendering cameras projection matrix, which in most cases is equivalent to PROJECTION_MATRIX except in cases where a full-screen quad is rendering, e.g. in a jit.gl.slab/pix (or jit.gl.pass). used in the gl3 engines ssao effect

FAR_CORNER == far corner of the view frustum??? - yup. used for depth rebuilding i think, can't quite remember. ssao shader maybe?

VIEWPORT - as federico says above, the pixel size of rendering window
INVERSE_VIEWPORT - just as it sounds, the inverse of the viewport dims

LIGHT0-7_CUTOFF - the spotlight cutoff in degrees, another name for the spotlight angle

Thank you so much, Federico and Rob!
I updated the list in the first post. 
I'll soon indicate for each built-it uniform a .jxs file in which it gets used, so that each variable can be seen in action in a reference patch.

btw, I wanted a "PREV_MODELVIEW_PROJECTION_MATRIX"-like variable so bad, and it was right under my nose...

cool, thanks much for taking the initiative here!

btw the PREV_MODELVIEW_PROJECTION_MATRIX is not yet implemented in gl3, but I hope to fix that sooner than later


Insane help here, and some example of code in action would indeed be of enormous value :o, I'm following you guys : )

Hi Riccardo, this tutorial I made today should be a fitting example of code in action:
https://youtu.be/gKIVuVCfBws 

Oww, I felt like being halfway to convert it and here you come. Thanks for the enlightening coding.

texture2D became texture... what about texture2DRect? If textureRect is the solution, this wasn't my real problem :o

I've been feeding a shader with two textures, the first for extrusion purpose, the second is the texture to be applied over the distorted shape. If i use "outColor = color" I can see my grey shape being distorted from the first texture, but when I'm trying to use my second texture, I'm getting this...

I'm hoping the problem lies here, if it is not, I can share the full code attached to a simple patcher as example.

Hi Riccardo, I think you get this error because you are using a vec4 as a second argument to the function "texture",  which takes a vec2 as a second argument. 
I think you mixed up multiplying the texcoord by the texture matrix, for which you need a vec4, and using the texcoord to read the texture with the "texture" function. 

It totally make sense. Still I'm playing with an invisible shape ohoh.
I'll give it some more tries.

Jitter Forum