[Compute Shaders]

I'd like to try using these now.  Is this the way to use them? I found this here.

//Load compute shader
auto module = LoadShaderModule("Shaders/Compute/test.comp.spv");
auto shader = CreateShader();
shader->SetModule(module, SHADER_COMPUTE);

//Create work group
int workercount = 8;
auto workgroup = CreateWorkgroup(shader, workercount, workercount, workercount);

I couldn't find CreateWorkgroup() in the API though.

[Geometry Shader Lighting]

It's a bit slow using the geometry shader.  FPS drops from 800 to 300.  I think compute shaders might help here.

[Grass Shader]

Changing the material roughness made it look 10x better.  I'm happy with the lighting now.

[Grass Shader]

Better!

[Geometry Shader Lighting]

That seemed to have done the trick.

[Geometry Shader Lighting]

Hmm, actually I don't think my normals are right... I'm multiplying the local vertex positions by a local matrix to rotate the blades but the normals are unchanged.  Can I rotate normals by multiplying by the same matrix as I do the vertices?

[Geometry Shader Lighting]

Just thought I'd check.

If I turn off Image Based Lighting I get a darker grass but no more artifacts.  Not sure if that's the cause or it's just hiding it. 

EDIT: I think IBL is the cause, though I have no idea why.

[Geometry Shader Lighting]

Oh, that reminds me.  Inside that function in Lighting.glsl, RenderLight() was using the input vertexWorldPosition rather than the argument "position".

RenderLight(lightIndex, material, materialInfo, vertexWorldPosition.xyz, normal, v, NdotV, f_diffuse, f_specular, renderprobes, ibldiffuse, iblspecular);

I thought it should use the argument 'position' seeing as it is passed to it but not sure... I don't know if it's something the user could end up editing in the UserFunction?

[Geometry Shader Lighting]

I'm getting mixed and seemingly random results with the lighting of my grass.  The line between light and dark moves with the camera.  This is what I'm passing out of my geometry shader to the default PBR fragment shader.  The grass is green as I'm setting the vertex color to green.  The fragment shader is just doing the lighting.  I've looked at the fragment shaders to see what it needed but might have missed something?

layout(location = 25 ) out uint outEntityID;
layout(location = 5 ) out flat uint outMaterialID;
layout(location = 8 ) out vec4 outVertexPosition;
layout(location = 1 ) out vec3 normal;
layout(location = 7 ) out vec4 worldPosition;
layout(location = 0 ) out vec4 vertexColor;

First it was this;

Now at random it is this;

 

[Grass Shader]

Half my grass was actually below the ground.   Now it looks better and I gave it some rough animation.  I've also made it that the root of the grass blades are darker.  Still needs a lot of work but I'm done for now I think.  I can fine tune it later.

[Grass Shader]

Thanks, I didn't think so.  I must be passing something wrong.

[Grass Shader]

I wonder what causes this in PBR lighting... my normals and world positions are passed to the fragment shader properly, but do I need tex_coords too? 

[Grass Shader]

That's better.

[Grass Shader]

Needs some better noise maps for position and rotation I think

[Grass Shader]

First attempt at grass in Ultra.  Lighting needs work still, but not too bad.

 

[.json auto appended to shader family]

Do you mean this?

I don't see how this takes into account making our own shaders though.

[.json auto appended to shader family]

It makes sense to make everything relative to the executable so we can just define a shader family as "Shaders\MyFamily.json" or "Materials\MyMaterial\MyFamily.json".

[.json auto appended to shader family]

Okay so I see now it's trying to load it from the shaders folder too... I see what your doing for the standard materials and the shader family's for Ultra but I don't think its a good idea.  Ultra needs to be flexible.  I want my shaders and textures in one folder.  I don't want to split the materials and textures into one and then my custom shaders into another.  I think we should be able to define a path because it is, after all, a file.

[.json auto appended to shader family]

I name my json files .mat and .fam so I can see the difference without having to open them, but it's no big deal.  I'll make it work.

[.json auto appended to shader family]

Hey @Josh just wondering if this is actually a bug or I should change my files to all use .json?  Thanks.

[Controller Component]

When it comes time to expand the character controller system, I was thinking it might be good to have it as an expandable system.  Like a component where if we wanted too, override key systems of the controller, like gravity, physics and anything else that makes it a controller.  I would find that very useful.  Just a thought. 

[DevLog Leadwerks Engine.]

Just tried it out, with the skybox removed it still happens on the far wall of the base.  It's just a lot harder to tell because the colour difference between the black background and the dark gray wall is very small.  If you remove the skybox and make the cameras clear color red or something else bright you will will be able to see it better.  I don't think it has anything to do with the terrain or skybox.  I think it's something to do with the CSG objects.

I can see in your video it is still occurring too.  A few work arounds might be - slowing the cameras rotation speed so that it's less noticeable; or, make a large enclosure for the base that has the same colour as the walls and enable it when the players is inside, so that when it happens it only reveals a similar colour behind the walls rather then the bright skybox / terrain.

[DevLog Leadwerks Engine.]

Yeah I don't think its the GPU.  I've got a GTX 980 TI.  Maybe it is the skybox.  If you remove it I can test on my PC to verify if that's the issue if you like.

[DevLog Leadwerks Engine.]

9 hours ago, Yue said:

No, I don't have anything in the scene, only the last image, the error only happens when I have fog, or a terrain, or the sky.

How many CSG objects are there in total?  I tried your demo again and saw that other CSG objects out side of the base took time to appear as well. (orange platform)  When the walls vanish they show not only the skybox but the other objects behind it too.  I tend to think it's just lots of CSG objects.  You might be better off making your base one large object in some modelling software.  But there might be something else at play, I'm not sure.

[DevLog Leadwerks Engine.]

That looks like the occlusion system to me.  I've never used CSG to model a level before.  I take it there are a lot of entities in your scene?