Shader tests

[CTZn]

It sure looks great !

[Borgleader]

It sure looks great !

+1

And...how do you....map a procedural? I mean, in the 3d editor, how do you map the fbm?

[Grimm]

And...how do you....map a procedural? I mean, in the 3d editor, how do you map the fbm?

I'm not exactly sure what you mean by "map" the fbm, but I will take a stab at it. Fbm's are just random noise so you don't really know what you are getting until you render an image. You can adjust the texture by either scaling or translating the terms you feed into the fbm. This has the effect of resizing or moving the fbm and the resultant textures on the mesh. I hope this helps.

[Big Fan]

that brushed look is very nice ono

I think I will build that shader and vector direction into the specular reflectivity exporter settings just for that - very handy for Solidworks materials...

the previous egg shell/dimpled look is nice too - might borrow that as well

keep the examples coming

EDIT:ok done that now when is 1.1.8 coming so I can try it?

[eman7613]

i do belive the syntax would benifit greatly from operators

for anyone used to coding in java's horrid bigdecimal *raises hand*, this looks very familure

That's what you get for using a language without operator overloading (Java)

its my one complaint, but its okay, i made my own*

*j/k its just a math parser

[Kram1032]

@Kram - Thanks, this has been a challenge that's for sure. Is this test more to your liking?

Yeah, those two last ones are great
First is pretty boneish and second pretty marblish


Anisotrophy Cool!

[fused]

ok,,, its hard to compete with such impressive shaders,,,

here are two very simple (you see, very very simple) gradient shaders, hope someone will find them useful:

Code: Select all

<albedo>
	<shader>
		<shader>
			<![CDATA[	
					
			# 2D gradient shader U
						
			def eval(vec3 pos) vec3 :
				vec3(
					doti(getTexCoords(0))
				)
			]]>
		</shader>
	</shader>
</albedo>

<albedo>
	<shader>
		<shader>
			<![CDATA[	
					
			# 2D gradient shader V
						
			def eval(vec3 pos) vec3 :
				vec3(
					dotj(getTexCoords(0))
				)
			]]>
		</shader>
	</shader>
</albedo>

thnaks to zomb for rendering!

[fused]

3d gradient in z direction this time. a tiny bit more complex.

guess this can be quite useful

Code: Select all

<albedo>
	<shader>
		<shader>
			<![CDATA[	
					
			# 3D gradient shader Z (up)
						
			def eval(vec3 pos) vec3 :
				vec3(
					div(mod(dotk(pos),0.6),0.6)
				)
			]]>
		</shader>
	</shader>
</albedo>

<albedo>
	<shader>
		<shader>
			<![CDATA[	
					
			# 3D gradient shader Z (up) with center = 0.5
						
			def eval(vec3 pos) vec3 :
				vec3(
					div(mod(add(dotk(pos),div(0.6,2.0)),0.6),0.6)
				)
			]]>
		</shader>
	</shader>
</albedo>

again, thanks to zomb for rendering.

[CTZn]

Still cryptic but very usefull, fused, plz keep them coming !

[cpfresh]

the z up gradient is awesome, thanks for sharing fused!

[Whaat]

thanks for sharing this. It is useful to know what works. I have had lots of problems getting shaders to work.

[Deus]

To be honest its pretty simple (if you can program to start with)

Anyone know if you can declare variables yet? I mean performance AND readability would increase tremendously

Compare:

Code: Select all

<albedo>
   <shader>
      <shader>
         <![CDATA[   
               
         # 3D gradient shader Z (up) with center = 0.5
                  
         def eval(vec3 pos) vec3 :
            vec3(
               div(mod(add(dotk(pos),div(0.6,2.0)),0.6),0.6),
               div(mod(add(dotk(pos),div(0.6,2.0)),0.6),0.6),
               div(mod(add(dotk(pos),div(0.6,2.0)),0.6),0.6)
            )
         ]]>
      </shader>
   </shader>
</albedo>

to:

Code: Select all

<albedo>
   <shader>
      <shader>
         <![CDATA[   
               
         # 3D gradient shader Z (up) with center = 0.5
                  
         def eval(vec3 pos) vec3 :
            float color = div(mod(add(dotk(pos),div(0.6,2.0)),0.6),0.6)
            vec3( color, color, color )
         ]]>
      </shader>
   </shader>
</albedo>

And why the Double shader tags? Nesting gone nuts tbh

[OnoSendai]

No, you can't declare variables.
However you could factor out the colour computation into another procedure.
Actually, in this case, you can use the scalar vec3 constructor vec3(real x) vec3.

The double shader tags are there to draw a distinction between the type, and value of the albedo material parameter.

[CTZn]

it would be cool to declare textures and shaders globally (keeping using the index thing) instead into a material, so they can be called by any of them while delared once only. Maybe this could apply for constant definitions too ?

This idea comes along with the one of a database for constant maybe, and shaders, and with manual coding of shaders. It does not make much sense in regard with the generic scene exporting process.

[fused]

Actually, in this case, you can use the scalar vec3 constructor vec3(real x) vec3.

i have completely overlooked it! (edited the shaders now using this)

To be honest its pretty simple (if you can program to start with)

ahhh thanks? i told you so


@ono:
can you give me a quick example on how if() works? how can i, for example check if a value is > 1?