Material Slots

[SpiderPig]

I'm writing my own shader and am wondering if I can use an integer to identify the texture slot in a material?

"slot":0

[Josh]

I don't think the JSON material format is very well nailed down right now. I have been sloppy with this.

[SpiderPig]

Ah okay.  I am curious though how to pass multiple textures to the shader for terrain... is there like a 2D texture array slot or something or we just set it just like Leadwerks;

Obviously I can manipulate the shader to read from the appropriate slots.

slot0 : DIFFUSE1
slot1 : NORMAL1
slot2 : DIFFUSE2
slot3 : NORMAL2
slot4 : DIFFUSE3
slot4 : NORMAL3
etc...

[reepblue]

Yeah, there was documentation on the material format but it was years ago. I recall there being features like texture scrolling and such in the default shaders too but I'm not sure if they still are implemented.

Hopefully this gets cleaned up and documented in the near future.

[Josh]

Let's keep it simple. Here is a valid material file:

{
	"material": {
		"color": [1.0, 1.0, 1.0, 1.0],
		"displacement": 0.1,
		"emission": [0.0, 0.0, 0.0],
		"metallic": 0.0,
		"roughness": 1.0,
		"shaderFamily": "Shaders/PBR.json",
		"shadow": true,
		"tessellation": false,
		"texture0": "./defaultmeshface.tex",
		"transparent": false
	}
}

For textures, a file in the same folder as the material file can use a relative path by adding ./ at the beginning of the path. Otherwise it will be considered a path relative to the project folder, i.e. "Materials/brick/brick01.dds".

[SpiderPig]

Simple is best.  Is MAX_TEXTURES_2D the limit for an individual material?  I think assigning textures in code can't go over 16.

[Josh]

16 is the limit.