tmhglnd

Hey! I created this small package of objectmappings that allow you to just type: [jit.gl.kaleido], and it will be replaced by: [jit.gl.slab @file td.kaleido.jxs] (using the correct prefix! cc, co, td, etc.). Works for all the shaderfiles included in the Max installation. Some shaders like the materials (eg. [jit.gl.glass]) will be converted to [jit.gl.shader @file mat.glass.jxs]. Also all the shaderfiles are now visible in the autocomplete field when typing jit.gl. This will surely save some time when patching.

https://github.com/tmhglnd/gl.shadermappings

Suggestions for improvements or bugfixes are of course welcome ^^

screenshot.png

Hey! I created this small package of objectmappings that allow you to just type: [jit.gl.kaleido], and it will be replaced by: [jit.gl.slab @file td.kaleido.jxs] (using the correct prefix! cc, co, td, etc.). Works for all the shaderfiles included in the Max installation. Some shaders like the materials (eg. [jit.gl.glass]) will be converted to [jit.gl.shader @file mat.glass.jxs]. Also all the shaderfiles are now visible in the autocomplete field when typing jit.gl. This will surely save some time when patching. 

https://github.com/tmhglnd/gl.shadermappings 

Hey all!
Hey! I created this small package of objectmappings that allow you to just type: [jit.gl.kaleido], and it will be replaced by: [jit

-sharing-shader-object-mappings

hm, i would maybe include one special character at one point, you know why.

Yes I see what you mean. But there are no clashes with objects at the moment (as far as I could tell) and really for me personally I like it to be in the jit.gl. list. But if it will ever clash in the future it can be easily changed, and since the object will be replaced with the actual [jit.gl.slab @file <name>] there will be no problems with patches having used it up till now.

and those with concerns can copy yours but change it right away in their own install. all clear.

[sharing] shader object mappings