Skip to content

Update README.md #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Gavin-Sears wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update README.md #22

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
50d7844
Update README.md
Gavin-Sears Sep 17, 2025
31df226
Clean up README by removing setup section
Gavin-Sears Oct 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 10 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,17 @@
# lab02-debugging

# Setup
Stephen Gavin Sears

Create a [Shadertoy account](https://www.shadertoy.com/). Either fork this shadertoy, or create a new shadertoy and copy the code from the [Debugging Puzzle](https://www.shadertoy.com/view/flGfRc).
worked with Rebecca Feng

Let's practice debugging! We have a broken shader. It should produce output that looks like this:
[Unbelievably beautiful shader](https://user-images.githubusercontent.com/1758825/200729570-8e10a37a-345d-4aff-8eff-6baf54a32a40.webm)
[link](https://www.shadertoy.com/view/WcffDl) to solution

It don't do that. Correct THREE of the FIVE bugs that are messing up the output. You are STRONGLY ENCOURAGED to work with a partner and pair program to force you to talk about your debugging thought process out loud.
- first bug: line 97 missing 2 in 'vec2' - found by compiler

Extra credit if you can find all FIVE bugs.
- second bug: line 100 use uv2 with screen offset instead of uv - result of uv2 was never used, so tried plugging it in. Also screen was not centered.

# Submission
- Create a pull request to this repository
- In the README, include the names of both your team members
- In the README, create a link to your shader toy solution with the bugs corrected
- In the README, describe each bug you found and include a sentence about HOW you found it.
- Make sure all three of your shadertoys are set to UNLISTED or PUBLIC (so we can see them!)
- third bug: line 14 used x instead of y for perspective division - spheres were squished, culprit was view to world calculation (uses screen dimensions)

- fourth bug: line 78 used eye vector for reflection, instead use dir - no lighting was present, so looked at shading calculation. Since eye was used, all shading will return same color, and also doesn't fit equation.

- fifth bug: line 18 num march steps too low, doubled to fix problem - with strange warped shapes being rendered, the raymarcher was the first suspect (plus all other parts had been looked at by this point). Optimized raymarching has more steps at edges of objects, so changing number of steps was worth a shot.