[INFO] Shader Stuff- HLSL instruction limits

[xenoargh]

OK, done testing it; the principle Idea works; now I just, uh, need to adjust about... every single specular    The problem is that all the existing speculars lack color shifts, which makes them look a little flat and lifeless now.  Oh well, that's a trade I can live with.

Maybe not today; gotta go do IRL in about 15 minutes.  Oh well, at least it's possible now; been wanting to do this since I looked at Narf's stuff in OpenBRF.

[Barabas]

Well, like I said, I tried that and it didn't work.

That's weird...

Cause thats all I did there, for as far as I can remember.

And I get this:

with a spec map like this:


We are talking about the ps_main_standart right?

From what I understand you use the spec coefficients in open brf to define the color right? Its much easier imo to use the specular texture.

[xenoargh]

Hmm.  I really didn't get that result over here, but I didn't try anything that saturated, either.  I'll have to play around with Rainbow Brite tomorrow night, see what's possible 

[Barabas]

Alright, well it is supposed to work :p
Everything multiplies there anyway, so.

If you have any other cool ideas for ways of using textures or anything. I'm all ears. I can't really think of anything 

[Computica]

Alright, well it is supposed to work :p
Everything multiplies there anyway, so.

If you have any other cool ideas for ways of using textures or anything. I'm all ears. I can't really think of anything 

I've been trying to figure out how to make the plant/tree shaders wobble. Does anyone know how to that in HLSL?

[Chaingun]

Conceptually you can just add an offset to vertex position modulated by sine functions of time + position. Now I have no idea for Warband whether you can edit vertex shader and if so whether there's a time parameter to modulate with.

[Barabas]

Conceptually you can just add an offset to vertex position modulated by sine functions of time + position. Now I have no idea for Warband whether you can edit vertex shader and if so whether there's a time parameter to modulate with.

There is. It's not easy to make them wobble realisticly though. And you have to find some way to wobble only the tips not the roots ^^
Using the position within the model coordinates doesn't work as automaticaly generated flora doesn't have those.

[Eiríkr Rauði]

Alright, well it is supposed to work :p
Everything multiplies there anyway, so.

If you have any other cool ideas for ways of using textures or anything. I'm all ears. I can't really think of anything 

I've been trying to figure out how to make the plant/tree shaders wobble. Does anyone know how to that in HLSL?

Shing a ding!

You'll probably want to talk to Slawomir or Tuls from the WFaS mod.

[Barabas]

I just managed to compile everything using vs_3_0 and ps_3_0 ^^
And it works in-game as well... apart from the fog, that somehow dissapeared 
Same for underwater effects 

!!This might not be the best idea if you don't know what you're doing!! (like me)

[xenoargh]

What should be done is to make it PS / VS 2 compliant; this can be done with vertex painting methods (VS 2 is not allowed to read pixels, but may read vertex colors).  The hard part is randomizing the system a bit so that the results exhibit some patterns of gross and tip motion that are dissimilar and feel natural.  I did this with another engine by generating per-object uniforms sent to the shader, but there are probably ways to achieve a similar sense of randomness via using the world-space coordinates of the thing.

[Barabas]

Does anyone know why compiling with vs and ps 3 would break the fog?
If we can fix that you would be able to actually read textures in the vertex shader =)

[xenoargh]

Fog may be using FFP; I don't have a better answer yet until I've had a chance to look at some things.  I'm not entirely sure that using VS 3.0 is as trouble-free as VS 2, though; you may run into fairly severe ATI / nVidia issues, and I don't think the engine returns a lot of details if a shader crashes.

[Barabas]

Ahh.. alright. I already wondered where the Out.Fog went after the vertex shader. Never comes back into the pixel shaders.
It's not very important anyway.

[xenoargh]

You can re-implement fog, though, I think; you'd have to get world-space coordinates for the vertex and compare to the camera's position; I *think* that is possible without having to send it a uniform... maybe get the length of the eye vector?  Should be possible to get the fog's strength, attenuation etc. from the existing inputs; it's probably just not getting along with the pixel shader. 

Might get into a fair amount of math on the pixel shader, though. 

I should prolly shut up, I will have to look at various things before my competence with HLSL and the DX rendering system is vaguely useful, so this may all be wrongo; sorry if it causes any wasted time

[Barabas]

What it does is this:

Code: [Select]

float3 P = mul(matWorldView, vPosition); //position in view space
//apply fog
float d = length(P);
float4 vWorldPos = (float4)mul(matWorld,vPosition);
Out.Fog = get_fog_amount_new(d, vWorldPos.z);
And get_fog_amount_new does nothing else then call get_fog_amount(d) which is:

Code: [Select]

return 1.0f / exp2(d * fFogDensity);
So it could be fairly easy to add that in the pixel shader.