Difference between revisions of "Lesson 5 - experimentation"
Bo3b admin (Talk | contribs) |
Bo3b admin (Talk | contribs) |
||
Line 21: | Line 21: | ||
---- | ---- | ||
− | + | After we've found a broken shader, we want to disable or fix them. We can't always do the easiest fix though, and this is where experimentation comes in. This is the puzzle aspect of fixing shaders, where it's not always clear how to fix a shader, even after having seen a lot of variants. | |
+ | |||
+ | The basic premise is to experiment on the shader by commenting out pieces of the code, and reloading it live with F10, and see any change. As you do these experiments, you can get a feel for what pieces of code affect what part of the image, which can lead you to the best fix. | ||
+ | |||
+ | It can be quite a bit of trial and error, but can allow you to figure out fixes that don't match common patterns, or to find the right spot for a common pattern. | ||
Revision as of 03:57, 12 September 2014
Summary
This lesson we will talk about the role of experimentation when trying to fix shaders.
Level of difficulty: Easy
Time required: 30 minutes
Video Walkthrough on YouTube
Video Walkthrough direct download link
Objective
Experiment on a broken shader to see how the pieces work together.
Fix the lava shader so it still works.
Quiz
Fix the entire game, and make a list of all shaders affected.
After we've found a broken shader, we want to disable or fix them. We can't always do the easiest fix though, and this is where experimentation comes in. This is the puzzle aspect of fixing shaders, where it's not always clear how to fix a shader, even after having seen a lot of variants.
The basic premise is to experiment on the shader by commenting out pieces of the code, and reloading it live with F10, and see any change. As you do these experiments, you can get a feel for what pieces of code affect what part of the image, which can lead you to the best fix.
It can be quite a bit of trial and error, but can allow you to figure out fixes that don't match common patterns, or to find the right spot for a common pattern.
Let's take a look at the basics of 3D graphics, so you can have a very rough idea of how the pieces fit together. This will give you some understanding of how the shaders work.
- Play with the Principles of Shading demo.
- Get the demo from here
- Run the demo and get an understanding of the wireframe vertexes versus the textures.
- Look at the Display menu in particular.
- Take a first look at the 0.5*D*T formula as a basic building block.
- Take a look at the graphics pipeline here
- Get a basic idea of the flow of graphics operations, especially noting VertexShaders run before PixelShaders.
After playing with this demo you should have a sense for how 3D graphics are built out of a list of vertices, that make up an array of triangles, that have textures applied to the triangles.
Sometimes we will run into an effect that really cannot be disabled without making the game a lot worse.
In this game, the Lava effect is an example. It's annoyingly broken, and makes those parts of the games unplayble. But, disabling it altogether removes the visual cue of the dangerous areas.
Let's experiment with it, to see if we can make something better.
- Experiment on lava shaders.
- Inspect and experiment on lava in both PS and VS.
- In pixel shader
- Fix lava by killing one texture instead of the entire shader.
Quiz: Go through the rest of the game, at least 3 full levels, and disable or fix all broken effects.
- Fix the entire game.
- Go through at least 3 levels, and find and mark all broken effects.
- Disable all broken effects.
- Fix the lava effect by disabling the texture.
- Save your list of modified shaders to your personal page.