diff --git a/INSTRUCTION.md b/INSTRUCTION.md
new file mode 100644
index 0000000..a744a2e
--- /dev/null
+++ b/INSTRUCTION.md
@@ -0,0 +1,297 @@
+Instructions - Vulkan Grass Rendering
+========================
+
+This is due **Sunday 11/5, evening at midnight**.
+
+**Summary:**
+In this project, you will use Vulkan to implement a grass simulator and renderer. You will
+use compute shaders to perform physics calculations on Bezier curves that represent individual
+grass blades in your application. Since rendering every grass blade on every frame will is fairly
+inefficient, you will also use compute shaders to cull grass blades that don't contribute to a given frame.
+The remaining blades will be passed to a graphics pipeline, in which you will write several shaders.
+You will write a vertex shader to transform Bezier control points, tessellation shaders to dynamically create
+the grass geometry from the Bezier curves, and a fragment shader to shade the grass blades.
+
+The base code provided includes all of the basic Vulkan setup, including a compute pipeline that will run your compute
+shaders and two graphics pipelines, one for rendering the geometry that grass will be placed on and the other for 
+rendering the grass itself. Your job will be to write the shaders for the grass graphics pipeline and the compute pipeline, 
+as well as binding any resources (descriptors) you may need to accomplish the tasks described in this assignment.
+
+![](img/grass.gif)
+
+You are not required to use this base code if you don't want
+to. You may also change any part of the base code as you please.
+**This is YOUR project.** The above .gif is just a simple example that you
+can use as a reference to compare to.
+
+**Important:**
+- If you are not in CGGT/DMD, you may replace this project with a GPU compute
+project. You MUST get this pre-approved by Austin Eng before continuing!
+
+### Contents
+
+* `src/` C++/Vulkan source files.
+  * `shaders/` glsl shader source files
+  * `images/` images used as textures within graphics pipelines
+* `external/` Includes and static libraries for 3rd party libraries.
+* `img/` Screenshots and images to use in your READMEs
+
+### Installing Vulkan
+
+In order to run a Vulkan project, you first need to download and install the [Vulkan SDK](https://vulkan.lunarg.com/).
+Make sure to run the downloaded installed as administrator so that the installer can set the appropriate environment
+variables for you.
+
+Once you have done this, you need to make sure your GPU driver supports Vulkan. Download and install a 
+[Vulkan driver](https://developer.nvidia.com/vulkan-driver) from NVIDIA's website.
+
+Finally, to check that Vulkan is ready for use, go to your Vulkan SDK directory (`C:/VulkanSDK/` unless otherwise specified)
+and run the `cube.exe` example within the `Bin` directory. IF you see a rotating gray cube with the LunarG logo, then you
+are all set!
+
+### Running the code
+
+While developing your grass renderer, you will want to keep validation layers enabled so that error checking is turned on. 
+The project is set up such that when you are in `debug` mode, validation layers are enabled, and when you are in `release` mode,
+validation layers are disabled. After building the code, you should be able to run the project without any errors. You will see 
+a plane with a grass texture on it to begin with.
+
+![](img/cube_demo.png)
+
+## Requirements
+
+**Ask on the mailing list for any clarifications.**
+
+In this project, you are given the following code:
+
+* The basic setup for a Vulkan project, including the swapchain, physical device, logical device, and the pipelines described above.
+* Structs for some of the uniform buffers you will be using.
+* Some buffer creation utility functions.
+* A simple interactive camera using the mouse. 
+
+You need to implement the following features/pipeline stages:
+
+* Compute shader (`shaders/compute.comp`)
+* Grass pipeline stages
+  * Vertex shader (`shaders/grass.vert')
+  * Tessellation control shader (`shaders/grass.tesc`)
+  * Tessellation evaluation shader (`shaders/grass.tese`)
+  * Fragment shader (`shaders/grass.frag`)
+* Binding of any extra descriptors you may need
+
+See below for more guidance.
+
+## Base Code Tour
+
+Areas that you need to complete are
+marked with a `TODO` comment. Functions that are useful
+for reference are marked with the comment `CHECKITOUT`.
+
+* `src/main.cpp` is the entry point of our application.
+* `src/Instance.cpp` sets up the application state, initializes the Vulkan library, and contains functions that will create our
+physical and logical device handles.
+* `src/Device.cpp` manages the logical device and sets up the queues that our command buffers will be submitted to.
+* `src/Renderer.cpp` contains most of the rendering implementation, including Vulkan setup and resource creation. You will 
+likely have to make changes to this file in order to support changes to your pipelines.
+* `src/Camera.cpp` manages the camera state.
+* `src/Model.cpp` manages the state of the model that grass will be created on. Currently a plane is hardcoded, but feel free to 
+update this with arbitrary model loading!
+* `src/Blades.cpp` creates the control points corresponding to the grass blades. There are many parameters that you can play with
+here that will change the behavior of your rendered grass blades.
+* `src/Scene.cpp` manages the scene state, including the model, blades, and simualtion time.
+* `src/BufferUtils.cpp` provides helper functions for creating buffers to be used as descriptors.
+
+We left out descriptions for a couple files that you likely won't have to modify. Feel free to investigate them to understand their 
+importance within the scope of the project.
+
+## Grass Rendering
+
+This project is an implementation of the paper, [Responsive Real-Time Grass Rendering for General 3D Scenes](https://www.cg.tuwien.ac.at/research/publications/2017/JAHRMANN-2017-RRTG/JAHRMANN-2017-RRTG-draft.pdf).
+Please make sure to use this paper as a primary resource while implementing your grass renderers. It does a great job of explaining
+the key algorithms and math you will be using. Below is a brief description of the different components in chronological order of how your renderer will
+execute, but feel free to develop the components in whatever order you prefer.
+
+### Representing Grass as Bezier Curves
+
+In this project, grass blades will be represented as Bezier curves while performing physics calculations and culling operations. 
+Each Bezier curve has three control points.
+* `v0`: the position of the grass blade on the geomtry
+* `v1`: a Bezier curve guide that is always "above" `v0` with respect to the grass blade's up vector (explained soon)
+* `v2`: a physical guide for which we simulate forces on
+
+We also need to store per-blade characteristics that will help us simulate and tessellate our grass blades correctly.
+* `up`: the blade's up vector, which corresponds to the normal of the geometry that the grass blade resides on at `v0`
+* Orientation: the orientation of the grass blade's face
+* Height: the height of the grass blade
+* Width: the width of the grass blade's face
+* Stiffness coefficient: the stiffness of our grass blade, which will affect the force computations on our blade
+
+We can pack all this data into four `vec4`s, such that `v0.w` holds orientation, `v1.w` holds height, `v2.w` holds width, and 
+`up.w` holds the stiffness coefficient.
+
+![](img/blade_model.jpg)
+
+### Simulating Forces
+
+In this project, you will be simulating forces on grass blades while they are still Bezier curves. This will be done in a compute
+shader using the compute pipeline that has been created for you. Remember that `v2` is our physical guide, so we will be
+applying transformations to `v2` initially, then correcting for potential errors. We will finally update `v1` to maintain the appropriate
+length of our grass blade.
+
+#### Binding Resources
+
+In order to update the state of your grass blades on every frame, you will need to create a storage buffer to maintain the grass data.
+You will also need to pass information about how much time has passed in the simulation and the time since the last frame. To do this,
+you can extend or create descriptor sets that will be bound to the compute pipeline.
+
+#### Gravity
+
+Given a gravity direction, `D.xyz`, and the magnitude of acceleration, `D.w`, we can compute the environmental gravity in
+our scene as `gE = normalize(D.xyz) * D.w`.
+
+We then determine the contribution of the gravity with respect to the front facing direction of the blade, `f`, 
+as a term called the "front gravity". Front gravity is computed as `gF = (1/4) * ||gE|| * f`.
+
+We can then determine the total gravity on the grass blade as `g = gE + gF`.
+
+#### Recovery
+
+Recovery corresponds to the counter-force that brings our grass blade back into equilibrium. This is derived in the paper using Hooke's law.
+In order to determine the recovery force, we need to compare the current position of `v2` to its original position before
+simulation started, `iv2`. At the beginning of our simulation, `v1` and `v2` are initialized to be a distance of the blade height along the `up` vector.
+
+Once we have `iv2`, we can compute the recovery forces as `r = (iv2 - v2) * stiffness`.
+
+#### Wind
+
+In order to simulate wind, you are at liberty to create any wind function you want! In order to have something interesting,
+you can make the function depend on the position of `v0` and a function that changes with time. Consider using some combination
+of sine or cosine functions.
+
+Your wind function will determine a wind direction that is affecting the blade, but it is also worth noting that wind has a larger impact on
+grass blades whose forward directions are parallel to the wind direction. The paper describes this as a "wind alignment" term. We won't go 
+over the exact math here, but use the paper as a reference when implementing this. It does a great job of explaining this!
+
+Once you have a wind direction and a wind alignment term, your total wind force (`w`) will be `windDirection * windAlignment`.
+
+#### Total force
+
+We can then determine a translation for `v2` based on the forces as `tv2 = (gravity + recovery + wind) * deltaTime`. However, we can't simply
+apply this translation and expect the simulation to be robust. Our forces might push `v2` under the ground! Similarly, moving `v2` but leaving
+`v1` in the same position will cause our grass blade to change length, which doesn't make sense.
+
+Read section 5.2 of the paper in order to learn how to determine the corrected final positions for `v1` and `v2`. 
+
+### Culling tests
+
+Although we need to simulate forces on every grass blade at every frame, there are many blades that we won't need to render
+due to a variety of reasons. Here are some heuristics we can use to cull blades that won't contribute positively to a given frame.
+
+#### Orientation culling
+
+Consider the scenario in which the front face direction of the grass blade is perpendicular to the view vector. Since our grass blades
+won't have width, we will end up trying to render parts of the grass that are actually smaller than the size of a pixel. This could
+lead to aliasing artifacts.
+
+In order to remedy this, we can cull these blades! Simply do a dot product test to see if the view vector and front face direction of
+the blade are perpendicular. The paper uses a threshold value of `0.9` to cull, but feel free to use what you think looks best.
+
+#### View-frustum culling
+
+We also want to cull blades that are outside of the view-frustum, considering they won't show up in the frame anyway. To determine if
+a grass blade is in the view-frustum, we want to compare the visibility of three points: `v0, v2, and m`, where `m = (1/4)v0 * (1/2)v1 * (1/4)v2`.
+Notice that we aren't using `v1` for the visibility test. This is because the `v1` is a Bezier guide that doesn't represent a position on the grass blade.
+We instead use `m` to approximate the midpoint of our Bezier curve.
+
+If all three points are outside of the view-frustum, we will cull the grass blade. The paper uses a tolerance value for this test so that we are culling
+blades a little more conservatively. This can help with cases in which the Bezier curve is technically not visible, but we might be able to see the blade
+if we consider its width.
+
+#### Distance culling
+
+Similarly to orientation culling, we can end up with grass blades that at large distances are smaller than the size of a pixel. This could lead to additional
+artifacts in our renders. In this case, we can cull grass blades as a function of their distance from the camera.
+
+You are free to define two parameters here.
+* A max distance afterwhich all grass blades will be culled.
+* A number of buckets to place grass blades between the camera and max distance into.
+
+Define a function such that the grass blades in the bucket closest to the camera are kept while an increasing number of grass blades
+are culled with each farther bucket.
+
+#### Occlusion culling (extra credit)
+
+This type of culling only makes sense if our scene has additional objects aside from the plane and the grass blades. We want to cull grass blades that
+are occluded by other geometry. Think about how you can use a depth map to accomplish this!
+
+### Tessellating Bezier curves into grass blades
+
+In this project, you should pass in each Bezier curve as a single patch to be processed by your grass graphics pipeline. You will tessellate this patch into 
+a quad with a shape of your choosing (as long as it looks sufficiently like grass of course). The paper has some examples of grass shapes you can use as inspiration.
+
+In the tessellation control shader, specify the amount of tessellation you want to occur. Remember that you need to provide enough detail to create the curvature of a grass blade.
+
+The generated vertices will be passed to the tessellation evaluation shader, where you will place the vertices in world space, respecting the width, height, and orientation information
+of each blade. Once you have determined the world space position of each vector, make sure to set the output `gl_Position` in clip space!
+
+** Extra Credit**: Tessellate to varying levels of detail as a function of how far the grass blade is from the camera. For example, if the blade is very far, only generate four vertices in the tessellation control shader.
+
+To build more intuition on how tessellation works, I highly recommend playing with the [helloTessellation sample](https://github.com/CIS565-Fall-2017/Vulkan-Samples/tree/master/samples/5_helloTessellation)
+and reading this [tutorial on tessellation](http://in2gpu.com/2014/07/12/tessellation-tutorial-opengl-4-3/).
+
+## Resources
+
+### Links
+
+The following resources may be useful for this project.
+
+* [Responsive Real-Time Grass Grass Rendering for General 3D Scenes](https://www.cg.tuwien.ac.at/research/publications/2017/JAHRMANN-2017-RRTG/JAHRMANN-2017-RRTG-draft.pdf)
+* [CIS565 Vulkan samples](https://github.com/CIS565-Fall-2017/Vulkan-Samples)
+* [Official Vulkan documentation](https://www.khronos.org/registry/vulkan/)
+* [Vulkan tutorial](https://vulkan-tutorial.com/)
+* [RenderDoc blog on Vulkan](https://renderdoc.org/vulkan-in-30-minutes.html)
+* [Tessellation tutorial](http://in2gpu.com/2014/07/12/tessellation-tutorial-opengl-4-3/)
+
+
+## Third-Party Code Policy
+
+* Use of any third-party code must be approved by asking on our Google Group.
+* If it is approved, all students are welcome to use it. Generally, we approve
+  use of third-party code that is not a core part of the project. For example,
+  for the path tracer, we would approve using a third-party library for loading
+  models, but would not approve copying and pasting a CUDA function for doing
+  refraction.
+* Third-party code **MUST** be credited in README.md.
+* Using third-party code without its approval, including using another
+  student's code, is an academic integrity violation, and will, at minimum,
+  result in you receiving an F for the semester.
+
+
+## README
+
+* A brief description of the project and the specific features you implemented.
+* At least one screenshot of your project running.
+* A performance analysis (described below).
+
+### Performance Analysis
+
+The performance analysis is where you will investigate how...
+* Your renderer handles varying numbers of grass blades
+* The improvement you get by culling using each of the three culling tests
+
+## Submit
+
+If you have modified any of the `CMakeLists.txt` files at all (aside from the
+list of `SOURCE_FILES`), mentions it explicity.
+Beware of any build issues discussed on the Google Group.
+
+Open a GitHub pull request so that we can see that you have finished.
+The title should be "Project 6: YOUR NAME".
+The template of the comment section of your pull request is attached below, you can do some copy and paste:  
+
+* [Repo Link](https://link-to-your-repo)
+* (Briefly) Mentions features that you've completed. Especially those bells and whistles you want to highlight
+    * Feature 0
+    * Feature 1
+    * ...
+* Feedback on the project itself, if any.
diff --git a/README.md b/README.md
index a744a2e..f265476 100644
--- a/README.md
+++ b/README.md
@@ -1,115 +1,43 @@
-Instructions - Vulkan Grass Rendering
+Vulkan Grass Rendering
 ========================
 
-This is due **Sunday 11/5, evening at midnight**.
+**University of Pennsylvania, CIS 565: GPU Programming and Architecture, Project 6**
 
-**Summary:**
-In this project, you will use Vulkan to implement a grass simulator and renderer. You will
-use compute shaders to perform physics calculations on Bezier curves that represent individual
-grass blades in your application. Since rendering every grass blade on every frame will is fairly
-inefficient, you will also use compute shaders to cull grass blades that don't contribute to a given frame.
-The remaining blades will be passed to a graphics pipeline, in which you will write several shaders.
-You will write a vertex shader to transform Bezier control points, tessellation shaders to dynamically create
-the grass geometry from the Bezier curves, and a fragment shader to shade the grass blades.
-
-The base code provided includes all of the basic Vulkan setup, including a compute pipeline that will run your compute
-shaders and two graphics pipelines, one for rendering the geometry that grass will be placed on and the other for 
-rendering the grass itself. Your job will be to write the shaders for the grass graphics pipeline and the compute pipeline, 
-as well as binding any resources (descriptors) you may need to accomplish the tasks described in this assignment.
-
-![](img/grass.gif)
-
-You are not required to use this base code if you don't want
-to. You may also change any part of the base code as you please.
-**This is YOUR project.** The above .gif is just a simple example that you
-can use as a reference to compare to.
-
-**Important:**
-- If you are not in CGGT/DMD, you may replace this project with a GPU compute
-project. You MUST get this pre-approved by Austin Eng before continuing!
-
-### Contents
-
-* `src/` C++/Vulkan source files.
-  * `shaders/` glsl shader source files
-  * `images/` images used as textures within graphics pipelines
-* `external/` Includes and static libraries for 3rd party libraries.
-* `img/` Screenshots and images to use in your READMEs
-
-### Installing Vulkan
-
-In order to run a Vulkan project, you first need to download and install the [Vulkan SDK](https://vulkan.lunarg.com/).
-Make sure to run the downloaded installed as administrator so that the installer can set the appropriate environment
-variables for you.
-
-Once you have done this, you need to make sure your GPU driver supports Vulkan. Download and install a 
-[Vulkan driver](https://developer.nvidia.com/vulkan-driver) from NVIDIA's website.
-
-Finally, to check that Vulkan is ready for use, go to your Vulkan SDK directory (`C:/VulkanSDK/` unless otherwise specified)
-and run the `cube.exe` example within the `Bin` directory. IF you see a rotating gray cube with the LunarG logo, then you
-are all set!
-
-### Running the code
+* LINSHEN XIAO
+* Tested on: Windows 10, Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 16.0GB, NVIDIA GeForce GTX 970M (Personal computer)
 
-While developing your grass renderer, you will want to keep validation layers enabled so that error checking is turned on. 
-The project is set up such that when you are in `debug` mode, validation layers are enabled, and when you are in `release` mode,
-validation layers are disabled. After building the code, you should be able to run the project without any errors. You will see 
-a plane with a grass texture on it to begin with.
+## Overview
 
-![](img/cube_demo.png)
-
-## Requirements
-
-**Ask on the mailing list for any clarifications.**
-
-In this project, you are given the following code:
-
-* The basic setup for a Vulkan project, including the swapchain, physical device, logical device, and the pipelines described above.
-* Structs for some of the uniform buffers you will be using.
-* Some buffer creation utility functions.
-* A simple interactive camera using the mouse. 
+In this project, I used Vulkan to implement a grass simulator and renderer. I
+used compute shaders to perform physics calculations on Bezier curves that represent individual grass blades. Since rendering every grass blade on every frame will is fairly inefficient, I also use compute shaders to cull grass blades that don't contribute to a given frame. The remaining blades will be passed to a graphics pipeline, in which I wrote several shaders. I wrote a vertex shader to transform Bezier control points, tessellation shaders to dynamically create
+the grass geometry from the Bezier curves, and a fragment shader to shade the grass blades.
 
-You need to implement the following features/pipeline stages:
+## Features
 
-* Compute shader (`shaders/compute.comp`)
+* Compute shader 
 * Grass pipeline stages
-  * Vertex shader (`shaders/grass.vert')
-  * Tessellation control shader (`shaders/grass.tesc`)
-  * Tessellation evaluation shader (`shaders/grass.tese`)
-  * Fragment shader (`shaders/grass.frag`)
-* Binding of any extra descriptors you may need
-
-See below for more guidance.
-
-## Base Code Tour
-
-Areas that you need to complete are
-marked with a `TODO` comment. Functions that are useful
-for reference are marked with the comment `CHECKITOUT`.
-
-* `src/main.cpp` is the entry point of our application.
-* `src/Instance.cpp` sets up the application state, initializes the Vulkan library, and contains functions that will create our
-physical and logical device handles.
-* `src/Device.cpp` manages the logical device and sets up the queues that our command buffers will be submitted to.
-* `src/Renderer.cpp` contains most of the rendering implementation, including Vulkan setup and resource creation. You will 
-likely have to make changes to this file in order to support changes to your pipelines.
-* `src/Camera.cpp` manages the camera state.
-* `src/Model.cpp` manages the state of the model that grass will be created on. Currently a plane is hardcoded, but feel free to 
-update this with arbitrary model loading!
-* `src/Blades.cpp` creates the control points corresponding to the grass blades. There are many parameters that you can play with
-here that will change the behavior of your rendered grass blades.
-* `src/Scene.cpp` manages the scene state, including the model, blades, and simualtion time.
-* `src/BufferUtils.cpp` provides helper functions for creating buffers to be used as descriptors.
-
-We left out descriptions for a couple files that you likely won't have to modify. Feel free to investigate them to understand their 
-importance within the scope of the project.
-
-## Grass Rendering
+	* Vertex shader
+	* Tessellation control shader
+	* Tessellation evaluation shader
+	* Fragment shader
+* Simulating Forces
+	* Gravity
+	* Recovery
+	* Wind
+	* State Validation
+* Culling tests
+	* Orientation
+	* View-frustum
+	* Distance
+
+## Result
+
+![](img/grass2.gif)
+
+## Implementation
 
 This project is an implementation of the paper, [Responsive Real-Time Grass Rendering for General 3D Scenes](https://www.cg.tuwien.ac.at/research/publications/2017/JAHRMANN-2017-RRTG/JAHRMANN-2017-RRTG-draft.pdf).
-Please make sure to use this paper as a primary resource while implementing your grass renderers. It does a great job of explaining
-the key algorithms and math you will be using. Below is a brief description of the different components in chronological order of how your renderer will
-execute, but feel free to develop the components in whatever order you prefer.
+The paper does a great job of explaining the key algorithms and math I used. Below is a brief description of the different components in chronological order of how your renderer will execute, but feel free to develop the components in whatever order you prefer.
 
 ### Representing Grass as Bezier Curves
 
@@ -118,180 +46,66 @@ Each Bezier curve has three control points.
 * `v0`: the position of the grass blade on the geomtry
 * `v1`: a Bezier curve guide that is always "above" `v0` with respect to the grass blade's up vector (explained soon)
 * `v2`: a physical guide for which we simulate forces on
-
-We also need to store per-blade characteristics that will help us simulate and tessellate our grass blades correctly.
 * `up`: the blade's up vector, which corresponds to the normal of the geometry that the grass blade resides on at `v0`
 * Orientation: the orientation of the grass blade's face
 * Height: the height of the grass blade
 * Width: the width of the grass blade's face
 * Stiffness coefficient: the stiffness of our grass blade, which will affect the force computations on our blade
 
-We can pack all this data into four `vec4`s, such that `v0.w` holds orientation, `v1.w` holds height, `v2.w` holds width, and 
-`up.w` holds the stiffness coefficient.
-
 ![](img/blade_model.jpg)
 
 ### Simulating Forces
 
-In this project, you will be simulating forces on grass blades while they are still Bezier curves. This will be done in a compute
-shader using the compute pipeline that has been created for you. Remember that `v2` is our physical guide, so we will be
-applying transformations to `v2` initially, then correcting for potential errors. We will finally update `v1` to maintain the appropriate
-length of our grass blade.
-
-#### Binding Resources
-
-In order to update the state of your grass blades on every frame, you will need to create a storage buffer to maintain the grass data.
-You will also need to pass information about how much time has passed in the simulation and the time since the last frame. To do this,
-you can extend or create descriptor sets that will be bound to the compute pipeline.
-
 #### Gravity
-
-Given a gravity direction, `D.xyz`, and the magnitude of acceleration, `D.w`, we can compute the environmental gravity in
-our scene as `gE = normalize(D.xyz) * D.w`.
-
-We then determine the contribution of the gravity with respect to the front facing direction of the blade, `f`, 
-as a term called the "front gravity". Front gravity is computed as `gF = (1/4) * ||gE|| * f`.
-
-We can then determine the total gravity on the grass blade as `g = gE + gF`.
+Total gravity on the grass blade: environmental gravity + front gravity, which is the contribution of the gravity with respect to the front facing direction of the blade.
 
 #### Recovery
 
 Recovery corresponds to the counter-force that brings our grass blade back into equilibrium. This is derived in the paper using Hooke's law.
-In order to determine the recovery force, we need to compare the current position of `v2` to its original position before
-simulation started, `iv2`. At the beginning of our simulation, `v1` and `v2` are initialized to be a distance of the blade height along the `up` vector.
-
-Once we have `iv2`, we can compute the recovery forces as `r = (iv2 - v2) * stiffness`.
+Compare the current position of `v2` to its original position before
+simulation started, `iv2`, and compute the recovery forces as `r = (iv2 - v2) * stiffness`.
 
 #### Wind
 
-In order to simulate wind, you are at liberty to create any wind function you want! In order to have something interesting,
-you can make the function depend on the position of `v0` and a function that changes with time. Consider using some combination
-of sine or cosine functions.
-
-Your wind function will determine a wind direction that is affecting the blade, but it is also worth noting that wind has a larger impact on
-grass blades whose forward directions are parallel to the wind direction. The paper describes this as a "wind alignment" term. We won't go 
-over the exact math here, but use the paper as a reference when implementing this. It does a great job of explaining this!
-
-Once you have a wind direction and a wind alignment term, your total wind force (`w`) will be `windDirection * windAlignment`.
-
-#### Total force
-
-We can then determine a translation for `v2` based on the forces as `tv2 = (gravity + recovery + wind) * deltaTime`. However, we can't simply
-apply this translation and expect the simulation to be robust. Our forces might push `v2` under the ground! Similarly, moving `v2` but leaving
-`v1` in the same position will cause our grass blade to change length, which doesn't make sense.
-
-Read section 5.2 of the paper in order to learn how to determine the corrected final positions for `v1` and `v2`. 
+The wind function depends on the position of `v0` and a function that changes with time, combined with cosine function, which will determine a wind direction that is affecting the blade, and the wind has a larger impact on grass blades whose forward directions are parallel to the wind direction.
 
 ### Culling tests
 
-Although we need to simulate forces on every grass blade at every frame, there are many blades that we won't need to render
-due to a variety of reasons. Here are some heuristics we can use to cull blades that won't contribute positively to a given frame.
+Ingore blades that we won't need to render due to a variety of reasons.
 
 #### Orientation culling
 
-Consider the scenario in which the front face direction of the grass blade is perpendicular to the view vector. Since our grass blades
-won't have width, we will end up trying to render parts of the grass that are actually smaller than the size of a pixel. This could
-lead to aliasing artifacts.
-
-In order to remedy this, we can cull these blades! Simply do a dot product test to see if the view vector and front face direction of
-the blade are perpendicular. The paper uses a threshold value of `0.9` to cull, but feel free to use what you think looks best.
+When Front face direction of the grass blade is perpendicular to the view vector, as our grass blades won't have width, we will end up trying to render parts of the grass that are actually smaller than the size of a pixel, which could lead to aliasing artifacts. We can cull these blades.
 
 #### View-frustum culling
 
-We also want to cull blades that are outside of the view-frustum, considering they won't show up in the frame anyway. To determine if
-a grass blade is in the view-frustum, we want to compare the visibility of three points: `v0, v2, and m`, where `m = (1/4)v0 * (1/2)v1 * (1/4)v2`.
-Notice that we aren't using `v1` for the visibility test. This is because the `v1` is a Bezier guide that doesn't represent a position on the grass blade.
-We instead use `m` to approximate the midpoint of our Bezier curve.
-
-If all three points are outside of the view-frustum, we will cull the grass blade. The paper uses a tolerance value for this test so that we are culling
-blades a little more conservatively. This can help with cases in which the Bezier curve is technically not visible, but we might be able to see the blade
-if we consider its width.
+We can also cull blades that are outside of the view-frustum, 
 
 #### Distance culling
 
-Similarly to orientation culling, we can end up with grass blades that at large distances are smaller than the size of a pixel. This could lead to additional
-artifacts in our renders. In this case, we can cull grass blades as a function of their distance from the camera.
-
-You are free to define two parameters here.
-* A max distance afterwhich all grass blades will be culled.
-* A number of buckets to place grass blades between the camera and max distance into.
-
-Define a function such that the grass blades in the bucket closest to the camera are kept while an increasing number of grass blades
-are culled with each farther bucket.
-
-#### Occlusion culling (extra credit)
-
-This type of culling only makes sense if our scene has additional objects aside from the plane and the grass blades. We want to cull grass blades that
-are occluded by other geometry. Think about how you can use a depth map to accomplish this!
-
-### Tessellating Bezier curves into grass blades
-
-In this project, you should pass in each Bezier curve as a single patch to be processed by your grass graphics pipeline. You will tessellate this patch into 
-a quad with a shape of your choosing (as long as it looks sufficiently like grass of course). The paper has some examples of grass shapes you can use as inspiration.
-
-In the tessellation control shader, specify the amount of tessellation you want to occur. Remember that you need to provide enough detail to create the curvature of a grass blade.
-
-The generated vertices will be passed to the tessellation evaluation shader, where you will place the vertices in world space, respecting the width, height, and orientation information
-of each blade. Once you have determined the world space position of each vector, make sure to set the output `gl_Position` in clip space!
-
-** Extra Credit**: Tessellate to varying levels of detail as a function of how far the grass blade is from the camera. For example, if the blade is very far, only generate four vertices in the tessellation control shader.
-
-To build more intuition on how tessellation works, I highly recommend playing with the [helloTessellation sample](https://github.com/CIS565-Fall-2017/Vulkan-Samples/tree/master/samples/5_helloTessellation)
-and reading this [tutorial on tessellation](http://in2gpu.com/2014/07/12/tessellation-tutorial-opengl-4-3/).
-
-## Resources
-
-### Links
-
-The following resources may be useful for this project.
+Similarly to orientation culling, we can end up with grass blades that at large distances are smaller than the size of a pixel. This could lead to additional artifacts in our renders. We can cull grass blades as a function of their distance from the camera.
 
-* [Responsive Real-Time Grass Grass Rendering for General 3D Scenes](https://www.cg.tuwien.ac.at/research/publications/2017/JAHRMANN-2017-RRTG/JAHRMANN-2017-RRTG-draft.pdf)
-* [CIS565 Vulkan samples](https://github.com/CIS565-Fall-2017/Vulkan-Samples)
-* [Official Vulkan documentation](https://www.khronos.org/registry/vulkan/)
-* [Vulkan tutorial](https://vulkan-tutorial.com/)
-* [RenderDoc blog on Vulkan](https://renderdoc.org/vulkan-in-30-minutes.html)
-* [Tessellation tutorial](http://in2gpu.com/2014/07/12/tessellation-tutorial-opengl-4-3/)
+Here is a simple demonstration:
 
+![](img/grass4.gif)
 
-## Third-Party Code Policy
+## Performance Analysis
 
-* Use of any third-party code must be approved by asking on our Google Group.
-* If it is approved, all students are welcome to use it. Generally, we approve
-  use of third-party code that is not a core part of the project. For example,
-  for the path tracer, we would approve using a third-party library for loading
-  models, but would not approve copying and pasting a CUDA function for doing
-  refraction.
-* Third-party code **MUST** be credited in README.md.
-* Using third-party code without its approval, including using another
-  student's code, is an academic integrity violation, and will, at minimum,
-  result in you receiving an F for the semester.
+![](img/chart.png)
 
+| NUM_BLADES | None | Orientation | View-frustum | Distance | All  |
+|------------|------|-------------|--------------|----------|------|
+| 1 << 16    | 4.8  | 3.8         | 4.0          | 4.1      | 2.7  |
+| 1 << 17    | 8.7  | 6.7         | 7.2          | 7.5      | 4.5  |
+| 1 << 18    | 16.9 | 12.5        | 13.5         | 13.8     | 8.3  |
+| 1 << 19    | 31.2 | 22.0        | 25.0         | 25.6     | 14.9 |
 
-## README
+Test window size: Width: 1129; Height: 701;
 
-* A brief description of the project and the specific features you implemented.
-* At least one screenshot of your project running.
-* A performance analysis (described below).
+Though the result shows that among 3 different methods, orientation one is better than view-frustum one, view-frustum one is better than distance one, the efficiency of these culling methods strongly depends on the camera. For example, if the camera is close enough, then lots of grass will be outside the view-frustum. However, if the camera is too far, then all the grass will be inside the view-frustum, so it won't be as good as other methods under such circumstance.
 
-### Performance Analysis
 
-The performance analysis is where you will investigate how...
-* Your renderer handles varying numbers of grass blades
-* The improvement you get by culling using each of the three culling tests
 
-## Submit
 
-If you have modified any of the `CMakeLists.txt` files at all (aside from the
-list of `SOURCE_FILES`), mentions it explicity.
-Beware of any build issues discussed on the Google Group.
 
-Open a GitHub pull request so that we can see that you have finished.
-The title should be "Project 6: YOUR NAME".
-The template of the comment section of your pull request is attached below, you can do some copy and paste:  
 
-* [Repo Link](https://link-to-your-repo)
-* (Briefly) Mentions features that you've completed. Especially those bells and whistles you want to highlight
-    * Feature 0
-    * Feature 1
-    * ...
-* Feedback on the project itself, if any.
diff --git a/bin/Debug/vulkan_grass_rendering.exe b/bin/Debug/vulkan_grass_rendering.exe
new file mode 100644
index 0000000..be0c641
Binary files /dev/null and b/bin/Debug/vulkan_grass_rendering.exe differ
diff --git a/bin/Debug/vulkan_grass_rendering.ilk b/bin/Debug/vulkan_grass_rendering.ilk
new file mode 100644
index 0000000..12cefa7
Binary files /dev/null and b/bin/Debug/vulkan_grass_rendering.ilk differ
diff --git a/bin/Debug/vulkan_grass_rendering.pdb b/bin/Debug/vulkan_grass_rendering.pdb
new file mode 100644
index 0000000..922f2ee
Binary files /dev/null and b/bin/Debug/vulkan_grass_rendering.pdb differ
diff --git a/bin/Release/vulkan_grass_rendering.exe b/bin/Release/vulkan_grass_rendering.exe
new file mode 100644
index 0000000..755667f
Binary files /dev/null and b/bin/Release/vulkan_grass_rendering.exe differ
diff --git a/img/chart.png b/img/chart.png
new file mode 100644
index 0000000..b548d3c
Binary files /dev/null and b/img/chart.png differ
diff --git a/img/grass2.gif b/img/grass2.gif
new file mode 100644
index 0000000..46977a3
Binary files /dev/null and b/img/grass2.gif differ
diff --git a/img/grass4.gif b/img/grass4.gif
new file mode 100644
index 0000000..c0ca258
Binary files /dev/null and b/img/grass4.gif differ
diff --git a/src/Blades.h b/src/Blades.h
index 9bd1eed..6b97bfd 100644
--- a/src/Blades.h
+++ b/src/Blades.h
@@ -4,7 +4,7 @@
 #include <array>
 #include "Model.h"
 
-constexpr static unsigned int NUM_BLADES = 1 << 13;
+constexpr static unsigned int NUM_BLADES = 1 << 18;
 constexpr static float MIN_HEIGHT = 1.3f;
 constexpr static float MAX_HEIGHT = 2.5f;
 constexpr static float MIN_WIDTH = 0.1f;
diff --git a/src/Renderer.cpp b/src/Renderer.cpp
index b445d04..76492ca 100644
--- a/src/Renderer.cpp
+++ b/src/Renderer.cpp
@@ -198,6 +198,42 @@ void Renderer::CreateComputeDescriptorSetLayout() {
     // TODO: Create the descriptor set layout for the compute pipeline
     // Remember this is like a class definition stating why types of information
     // will be stored at each binding
+
+	// Describe the binding of the descriptor set layout
+	VkDescriptorSetLayoutBinding bladesLayoutBinding = {};
+	bladesLayoutBinding.binding = 0;
+	bladesLayoutBinding.descriptorType = VK_DESCRIPTOR_TYPE_STORAGE_BUFFER;
+	bladesLayoutBinding.descriptorCount = 1;
+	bladesLayoutBinding.stageFlags = VK_SHADER_STAGE_COMPUTE_BIT;
+	bladesLayoutBinding.pImmutableSamplers = nullptr;
+
+	// Describe the binding of the descriptor set layout
+	VkDescriptorSetLayoutBinding culledBladesLayoutBinding = {};
+	culledBladesLayoutBinding.binding = 1;
+	culledBladesLayoutBinding.descriptorType = VK_DESCRIPTOR_TYPE_STORAGE_BUFFER;
+	culledBladesLayoutBinding.descriptorCount = 1;
+	culledBladesLayoutBinding.stageFlags = VK_SHADER_STAGE_COMPUTE_BIT;
+	culledBladesLayoutBinding.pImmutableSamplers = nullptr;
+
+	// Describe the binding of the descriptor set layout
+	VkDescriptorSetLayoutBinding numBladesLayoutBinding = {};
+	numBladesLayoutBinding.binding = 2;
+	numBladesLayoutBinding.descriptorType = VK_DESCRIPTOR_TYPE_STORAGE_BUFFER;
+	numBladesLayoutBinding.descriptorCount = 1;
+	numBladesLayoutBinding.stageFlags = VK_SHADER_STAGE_COMPUTE_BIT;
+	numBladesLayoutBinding.pImmutableSamplers = nullptr;
+
+	std::vector<VkDescriptorSetLayoutBinding> bindings = { bladesLayoutBinding, culledBladesLayoutBinding, numBladesLayoutBinding };
+
+	// Create the descriptor set layout
+	VkDescriptorSetLayoutCreateInfo layoutInfo = {};
+	layoutInfo.sType = VK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_CREATE_INFO;
+	layoutInfo.bindingCount = static_cast<uint32_t>(bindings.size());
+	layoutInfo.pBindings = bindings.data();
+
+	if (vkCreateDescriptorSetLayout(logicalDevice, &layoutInfo, nullptr, &computeDescriptorSetLayout) != VK_SUCCESS) {
+		throw std::runtime_error("Failed to create descriptor set layout");
+	}
 }
 
 void Renderer::CreateDescriptorPool() {
@@ -216,6 +252,8 @@ void Renderer::CreateDescriptorPool() {
         { VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER , 1 },
 
         // TODO: Add any additional types and counts of descriptors you will need to allocate
+		// Blades (compute)
+		{ VK_DESCRIPTOR_TYPE_STORAGE_BUFFER , static_cast<uint32_t>(scene->GetBlades().size() * 3) },
     };
 
     VkDescriptorPoolCreateInfo poolInfo = {};
@@ -320,6 +358,43 @@ void Renderer::CreateModelDescriptorSets() {
 void Renderer::CreateGrassDescriptorSets() {
     // TODO: Create Descriptor sets for the grass.
     // This should involve creating descriptor sets which point to the model matrix of each group of grass blades
+
+	grassDescriptorSets.resize(scene->GetBlades().size());
+
+	// Describe the desciptor set
+	VkDescriptorSetLayout layouts[] = { modelDescriptorSetLayout };
+	VkDescriptorSetAllocateInfo allocInfo = {};
+	allocInfo.sType = VK_STRUCTURE_TYPE_DESCRIPTOR_SET_ALLOCATE_INFO;
+	allocInfo.descriptorPool = descriptorPool;
+	allocInfo.descriptorSetCount = static_cast<uint32_t>(grassDescriptorSets.size());
+	allocInfo.pSetLayouts = layouts;
+
+	// Allocate descriptor sets
+	if (vkAllocateDescriptorSets(logicalDevice, &allocInfo, grassDescriptorSets.data()) != VK_SUCCESS) {
+		throw std::runtime_error("Failed to allocate descriptor set");
+	}
+
+	std::vector<VkWriteDescriptorSet> descriptorWrites(grassDescriptorSets.size());
+
+	for (uint32_t i = 0; i < scene->GetBlades().size(); ++i) {
+		VkDescriptorBufferInfo modelBufferInfo = {};
+		modelBufferInfo.buffer = scene->GetBlades()[i]->GetModelBuffer();
+		modelBufferInfo.offset = 0;
+		modelBufferInfo.range = sizeof(ModelBufferObject);
+
+		descriptorWrites[i].sType = VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET;
+		descriptorWrites[i].dstSet = grassDescriptorSets[i];
+		descriptorWrites[i].dstBinding = 0;
+		descriptorWrites[i].dstArrayElement = 0;
+		descriptorWrites[i].descriptorType = VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER;
+		descriptorWrites[i].descriptorCount = 1;
+		descriptorWrites[i].pBufferInfo = &modelBufferInfo;
+		descriptorWrites[i].pImageInfo = nullptr;
+		descriptorWrites[i].pTexelBufferView = nullptr;
+	}
+
+	// Update descriptor sets
+	vkUpdateDescriptorSets(logicalDevice, static_cast<uint32_t>(descriptorWrites.size()), descriptorWrites.data(), 0, nullptr);
 }
 
 void Renderer::CreateTimeDescriptorSet() {
@@ -360,6 +435,74 @@ void Renderer::CreateTimeDescriptorSet() {
 void Renderer::CreateComputeDescriptorSets() {
     // TODO: Create Descriptor sets for the compute pipeline
     // The descriptors should point to Storage buffers which will hold the grass blades, the culled grass blades, and the output number of grass blades 
+
+	computeDescriptorSets.resize(scene->GetBlades().size());
+
+	// Describe the desciptor set
+	VkDescriptorSetLayout layouts[] = { computeDescriptorSetLayout };
+	VkDescriptorSetAllocateInfo allocInfo = {};
+	allocInfo.sType = VK_STRUCTURE_TYPE_DESCRIPTOR_SET_ALLOCATE_INFO;
+	allocInfo.descriptorPool = descriptorPool;
+	allocInfo.descriptorSetCount = static_cast<uint32_t>(computeDescriptorSets.size());
+	allocInfo.pSetLayouts = layouts;
+
+	// Allocate descriptor sets
+	if (vkAllocateDescriptorSets(logicalDevice, &allocInfo, computeDescriptorSets.data()) != VK_SUCCESS) {
+		throw std::runtime_error("Failed to allocate descriptor set");
+	}
+
+	std::vector<VkWriteDescriptorSet> descriptorWrites(3 * computeDescriptorSets.size());
+
+	for (uint32_t i = 0; i < scene->GetBlades().size(); ++i) {
+
+		VkDescriptorBufferInfo baldesBufferInfo = {};
+		baldesBufferInfo.buffer = scene->GetBlades()[i]->GetBladesBuffer();
+		baldesBufferInfo.offset = 0;
+		baldesBufferInfo.range = NUM_BLADES * sizeof(Blade);
+
+		descriptorWrites[3 * i + 0].sType = VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET;
+		descriptorWrites[3 * i + 0].dstSet = computeDescriptorSets[i];
+		descriptorWrites[3 * i + 0].dstBinding = 0;
+		descriptorWrites[3 * i + 0].dstArrayElement = 0;
+		descriptorWrites[3 * i + 0].descriptorType = VK_DESCRIPTOR_TYPE_STORAGE_BUFFER;
+		descriptorWrites[3 * i + 0].descriptorCount = 1;
+		descriptorWrites[3 * i + 0].pBufferInfo = &baldesBufferInfo;
+		descriptorWrites[3 * i + 0].pImageInfo = nullptr;
+		descriptorWrites[3 * i + 0].pTexelBufferView = nullptr;
+
+		VkDescriptorBufferInfo culledBladesBufferInfo = {};
+		culledBladesBufferInfo.buffer = scene->GetBlades()[i]->GetCulledBladesBuffer();
+		culledBladesBufferInfo.offset = 0;
+		culledBladesBufferInfo.range = NUM_BLADES * sizeof(Blade);
+
+		descriptorWrites[3 * i + 1].sType = VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET;
+		descriptorWrites[3 * i + 1].dstSet = computeDescriptorSets[i];
+		descriptorWrites[3 * i + 1].dstBinding = 1;
+		descriptorWrites[3 * i + 1].dstArrayElement = 0;
+		descriptorWrites[3 * i + 1].descriptorType = VK_DESCRIPTOR_TYPE_STORAGE_BUFFER;
+		descriptorWrites[3 * i + 1].descriptorCount = 1;
+		descriptorWrites[3 * i + 1].pBufferInfo = &culledBladesBufferInfo;
+		descriptorWrites[3 * i + 1].pImageInfo = nullptr;
+		descriptorWrites[3 * i + 1].pTexelBufferView = nullptr;
+
+		VkDescriptorBufferInfo numBaldesBufferInfo = {};
+		numBaldesBufferInfo.buffer = scene->GetBlades()[i]->GetNumBladesBuffer();
+		numBaldesBufferInfo.offset = 0;
+		numBaldesBufferInfo.range = sizeof(BladeDrawIndirect);
+
+		descriptorWrites[3 * i + 2].sType = VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET;
+		descriptorWrites[3 * i + 2].dstSet = computeDescriptorSets[i];
+		descriptorWrites[3 * i + 2].dstBinding = 2;
+		descriptorWrites[3 * i + 2].dstArrayElement = 0;
+		descriptorWrites[3 * i + 2].descriptorType = VK_DESCRIPTOR_TYPE_STORAGE_BUFFER;
+		descriptorWrites[3 * i + 2].descriptorCount = 1;
+		descriptorWrites[3 * i + 2].pBufferInfo = &numBaldesBufferInfo;
+		descriptorWrites[3 * i + 2].pImageInfo = nullptr;
+		descriptorWrites[3 * i + 2].pTexelBufferView = nullptr;
+	}
+
+	// Update descriptor sets
+	vkUpdateDescriptorSets(logicalDevice, static_cast<uint32_t>(descriptorWrites.size()), descriptorWrites.data(), 0, nullptr);
 }
 
 void Renderer::CreateGraphicsPipeline() {
@@ -480,7 +623,7 @@ void Renderer::CreateGraphicsPipeline() {
     colorBlending.blendConstants[2] = 0.0f;
     colorBlending.blendConstants[3] = 0.0f;
 
-    std::vector<VkDescriptorSetLayout> descriptorSetLayouts = { cameraDescriptorSetLayout, modelDescriptorSetLayout };
+    std::vector<VkDescriptorSetLayout> descriptorSetLayouts = { cameraDescriptorSetLayout, modelDescriptorSetLayout, computeDescriptorSetLayout };
 
     // Pipeline layout: used to specify uniform values
     VkPipelineLayoutCreateInfo pipelineLayoutInfo = {};
@@ -717,7 +860,7 @@ void Renderer::CreateComputePipeline() {
     computeShaderStageInfo.pName = "main";
 
     // TODO: Add the compute dsecriptor set layout you create to this list
-    std::vector<VkDescriptorSetLayout> descriptorSetLayouts = { cameraDescriptorSetLayout, timeDescriptorSetLayout };
+    std::vector<VkDescriptorSetLayout> descriptorSetLayouts = { cameraDescriptorSetLayout, timeDescriptorSetLayout, computeDescriptorSetLayout };
 
     // Create pipeline layout
     VkPipelineLayoutCreateInfo pipelineLayoutInfo = {};
@@ -884,6 +1027,10 @@ void Renderer::RecordComputeCommandBuffer() {
     vkCmdBindDescriptorSets(computeCommandBuffer, VK_PIPELINE_BIND_POINT_COMPUTE, computePipelineLayout, 1, 1, &timeDescriptorSet, 0, nullptr);
 
     // TODO: For each group of blades bind its descriptor set and dispatch
+	for (uint32_t i = 0; i < scene->GetBlades().size(); ++i) {
+		vkCmdBindDescriptorSets(computeCommandBuffer, VK_PIPELINE_BIND_POINT_COMPUTE, computePipelineLayout, 2, 1, &computeDescriptorSets[i], 0, nullptr);
+		vkCmdDispatch(computeCommandBuffer, (int)ceil(NUM_BLADES / WORKGROUP_SIZE), 1, 1);
+	}
 
     // ~ End recording ~
     if (vkEndCommandBuffer(computeCommandBuffer) != VK_SUCCESS) {
@@ -976,13 +1123,14 @@ void Renderer::RecordCommandBuffers() {
             VkBuffer vertexBuffers[] = { scene->GetBlades()[j]->GetCulledBladesBuffer() };
             VkDeviceSize offsets[] = { 0 };
             // TODO: Uncomment this when the buffers are populated
-            // vkCmdBindVertexBuffers(commandBuffers[i], 0, 1, vertexBuffers, offsets);
+            vkCmdBindVertexBuffers(commandBuffers[i], 0, 1, vertexBuffers, offsets);
 
             // TODO: Bind the descriptor set for each grass blades model
+			vkCmdBindDescriptorSets(commandBuffers[i], VK_PIPELINE_BIND_POINT_GRAPHICS, grassPipelineLayout, 1, 1, &grassDescriptorSets[j], 0, nullptr);
 
             // Draw
             // TODO: Uncomment this when the buffers are populated
-            // vkCmdDrawIndirect(commandBuffers[i], scene->GetBlades()[j]->GetNumBladesBuffer(), 0, 1, sizeof(BladeDrawIndirect));
+            vkCmdDrawIndirect(commandBuffers[i], scene->GetBlades()[j]->GetNumBladesBuffer(), 0, 1, sizeof(BladeDrawIndirect));
         }
 
         // End render pass
@@ -1057,6 +1205,7 @@ Renderer::~Renderer() {
     vkDestroyDescriptorSetLayout(logicalDevice, cameraDescriptorSetLayout, nullptr);
     vkDestroyDescriptorSetLayout(logicalDevice, modelDescriptorSetLayout, nullptr);
     vkDestroyDescriptorSetLayout(logicalDevice, timeDescriptorSetLayout, nullptr);
+	vkDestroyDescriptorSetLayout(logicalDevice, computeDescriptorSetLayout, nullptr);
 
     vkDestroyDescriptorPool(logicalDevice, descriptorPool, nullptr);
 
diff --git a/src/Renderer.h b/src/Renderer.h
index 95e025f..644872e 100644
--- a/src/Renderer.h
+++ b/src/Renderer.h
@@ -56,12 +56,15 @@ class Renderer {
     VkDescriptorSetLayout cameraDescriptorSetLayout;
     VkDescriptorSetLayout modelDescriptorSetLayout;
     VkDescriptorSetLayout timeDescriptorSetLayout;
+	VkDescriptorSetLayout computeDescriptorSetLayout;
     
     VkDescriptorPool descriptorPool;
 
     VkDescriptorSet cameraDescriptorSet;
     std::vector<VkDescriptorSet> modelDescriptorSets;
     VkDescriptorSet timeDescriptorSet;
+	std::vector<VkDescriptorSet> computeDescriptorSets;
+	std::vector<VkDescriptorSet> grassDescriptorSets;
 
     VkPipelineLayout graphicsPipelineLayout;
     VkPipelineLayout grassPipelineLayout;
diff --git a/src/main.cpp b/src/main.cpp
index 8bf822b..da482df 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -66,8 +66,13 @@ namespace {
 }
 
 int main() {
+
+	double seconds = time(NULL);
+	int fpstracker = 0;
+	int fps = 0;
+
     static constexpr char* applicationName = "Vulkan Grass Rendering";
-    InitializeWindow(640, 480, applicationName);
+    InitializeWindow(1366, 768, applicationName);
 
     unsigned int glfwExtensionCount = 0;
     const char** glfwExtensions = glfwGetRequiredInstanceExtensions(&glfwExtensionCount);
@@ -145,6 +150,15 @@ int main() {
 
     while (!ShouldQuit()) {
         glfwPollEvents();
+		time_t seconds2 = time(NULL);
+		fpstracker++;
+		if (seconds2 - seconds >= 1) {
+			fps = fpstracker / (seconds2 - seconds);
+			fpstracker = 0;
+			seconds = seconds2;
+			std::string title = "Vulkan Grass Rendering | " + std::to_string((int)fps) + " FPS | " + std::to_string(1000.f / (float)fps) + " ms";
+			glfwSetWindowTitle(GetGLFWWindow(), title.c_str());
+		}
         scene->UpdateTime();
         renderer->Frame();
     }
diff --git a/src/shaders/compute.comp b/src/shaders/compute.comp
index 0fd0224..1b1568c 100644
--- a/src/shaders/compute.comp
+++ b/src/shaders/compute.comp
@@ -36,6 +36,21 @@ struct Blade {
 // 	  uint firstInstance; // = 0
 // } numBlades;
 
+layout(set = 2, binding = 0) buffer Blades {
+	Blade blades[];
+};
+
+layout(set = 2, binding = 1) buffer CulledBlades {
+	Blade culledBlades[];
+};
+
+layout(set = 2, binding = 2) buffer NumBlades {
+	uint vertexCount;   // Write the number of blades remaining here
+	uint instanceCount; // = 1
+	uint firstVertex;   // = 0
+	uint firstInstance; // = 0
+} numBlades;
+
 bool inBounds(float value, float bounds) {
     return (value >= -bounds) && (value <= bounds);
 }
@@ -43,14 +58,101 @@ bool inBounds(float value, float bounds) {
 void main() {
 	// Reset the number of blades to 0
 	if (gl_GlobalInvocationID.x == 0) {
-		// numBlades.vertexCount = 0;
+		numBlades.vertexCount = 0;
 	}
+	uint index = gl_GlobalInvocationID.x;
 	barrier(); // Wait till all threads reach this point
+	Blade blade = blades[index];
 
     // TODO: Apply forces on every blade and update the vertices in the buffer
 
+	vec3 v0 = blade.v0.xyz;
+	vec3 v1 = blade.v1.xyz;
+	vec3 v2 = blade.v2.xyz;
+	vec3 up = blade.up.xyz;
+	float theta = blade.v0.w;
+	float height = blade.v1.w;
+	float stiffness = blade.up.w;
+
+	// Gravity
+	vec3 gE = vec3(0.0, -9.8, 0.0);
+	vec3 f = normalize(cross(up, vec3(sin(theta), 0.0, cos(theta))));
+	vec3 gF = 0.25 * 9.8 * f;
+	vec3 gravity = gE + gF;
+
+	// Recovery
+	vec3 iv2 = v0 + height * up;
+	vec3 recovery =  (iv2 - v2) * stiffness;
+
+	// Wind
+	vec3 wi = normalize(vec3(1.0, 0.0, 1.0));
+	float s = cos((dot(vec3(v0.x, 0.0, v0.z), wi) + totalTime * 5.0));
+	float fd = 1 -  abs(dot(normalize(wi * v0), normalize(v2 - v0)));
+	float fr = dot((v2 - v0) , up) / height;	
+	vec3 wind = wi * v0 * fd * fr * s; 
+
+	// State Validation
+	v2 += (gravity + recovery + wind) * deltaTime;
+	v2 = v2 - up * min(dot(up, v2 - v0), 0.0);
+
+	float lproj = length(v2 - v0 - up * dot( v2 - v1, up));
+	v1 = v0 + height * up * max(1 - (lproj / height), 0.05 * max(lproj / height, 1));
+
+	float L0 = length(v2 - v0);
+	float L1 = length(v2 - v1) + length(v1 - v0);
+	float L = (2.0 * L0 + (3.0 - 1.0) * L1) / (3.0 + 1.0);
+	float r = height / L;
+
+	blade.v1.xyz = v0 + r * (v1 - v0);
+	blade.v2.xyz = v1 + r * (v2 - v1);
+	blades[index] = blade;
+
 	// TODO: Cull blades that are too far away or not in the camera frustum and write them
 	// to the culled blades buffer
 	// Note: to do this, you will need to use an atomic operation to read and update numBlades.vertexCount
 	// You want to write the visible blades to the buffer without write conflicts between threads
+
+	bool culled = false;
+
+	//Orientation test
+	mat4 inverseView = inverse(camera.view);
+	vec3 viewDir = (inverseView * vec4(0.0,0.0,1.0,0.0)).xyz;
+	if(abs(dot(f,viewDir)) > 0.9) {
+		culled = true;
+	}
+
+	//View-frustum test
+	if(!culled) {
+		vec3 m = 0.25 * v0 + 0.5 * v1 + 0.25 * v2;
+		mat4 viewproj = camera.proj * camera.view;
+		vec4 pv0 = viewproj * vec4(v0, 1.0);
+		vec4 pm = viewproj * vec4(m, 1.0);
+		vec4 pv2 = viewproj * vec4(v2, 1.0);
+		float t = 0.3;
+		float hv0 = pv0.w + t;
+		float hm = pm.w + t;
+		float hv2 = pv2.w + t;
+		if(!(inBounds(pv0.x, hv0) && inBounds(pv0.y, hv0) && inBounds(pv0.z, hv0)
+		&& inBounds(pm.x, hm) && inBounds(pm.y, hm) && inBounds(pm.z, hm)
+		&& inBounds(pv2.x, hv2) && inBounds(pv2.y, hv2) && inBounds(pv2.z, hv2))) {
+			culled = true;
+		}
+	}
+
+	//Distance test
+	if(!culled) {
+		vec3 v0_c = (camera.view * vec4(v0, 1.0)).xyz;
+		vec3 upc = normalize((camera.view * vec4(up, 0.0)).xyz);
+		float dproj = length(v0_c - dot(v0_c , upc) * upc);
+		float dmax = 45.0;
+		uint n = 10;
+		if((index % n) > n * (1.0 - dproj / dmax)) {
+			culled = true;
+		}
+	}
+
+	if(!culled)
+	{
+		culledBlades[atomicAdd(numBlades.vertexCount, 1)] = blade;
+	}
 }
diff --git a/src/shaders/grass.frag b/src/shaders/grass.frag
index c7df157..d8db45d 100644
--- a/src/shaders/grass.frag
+++ b/src/shaders/grass.frag
@@ -8,10 +8,21 @@ layout(set = 0, binding = 0) uniform CameraBufferObject {
 
 // TODO: Declare fragment shader inputs
 
+//layout(location = 0) in vec3 fragColor;
+
+layout(location = 0) in vec3 nor;
+layout(location = 1) in vec2 uv;
+
 layout(location = 0) out vec4 outColor;
 
 void main() {
     // TODO: Compute fragment color
 
-    outColor = vec4(1.0);
+	vec3 upColor = vec3(0.4,0.9,0.3);
+	vec3 lowColor = vec3(0.3,0.7,0.0);
+	vec3 lightDir = normalize(vec3(1.0, 0.0, -1.0));
+	vec3 finalColor = mix(lowColor, upColor, uv.y);
+	outColor = vec4(finalColor * max(dot(lightDir, nor),0.0), 1.0);
+    //outColor = vec4(1.0);
+	
 }
diff --git a/src/shaders/grass.tesc b/src/shaders/grass.tesc
index f9ffd07..5632a1c 100644
--- a/src/shaders/grass.tesc
+++ b/src/shaders/grass.tesc
@@ -10,17 +10,31 @@ layout(set = 0, binding = 0) uniform CameraBufferObject {
 
 // TODO: Declare tessellation control shader inputs and outputs
 
+layout (location = 0) in vec4 tesc_v1[];
+layout (location = 1) in vec4 tesc_v2[];
+layout (location = 2) in vec4 tesc_up[];
+layout (location = 3) in vec4 tesc_dir[];
+
+layout(location = 0) patch out vec4 tese_v1;
+layout(location = 1) patch out vec4 tese_v2;
+layout(location = 2) patch out vec4 tese_up;
+layout(location = 3) patch out vec4 tese_dir;
+
 void main() {
 	// Don't move the origin location of the patch
     gl_out[gl_InvocationID].gl_Position = gl_in[gl_InvocationID].gl_Position;
 
 	// TODO: Write any shader outputs
+	tese_v1 = tesc_v1[0];
+	tese_v2 = tesc_v2[0];
+	tese_up = tesc_up[0];
+	tese_dir = tesc_dir[0];
 
 	// TODO: Set level of tesselation
-    // gl_TessLevelInner[0] = ???
-    // gl_TessLevelInner[1] = ???
-    // gl_TessLevelOuter[0] = ???
-    // gl_TessLevelOuter[1] = ???
-    // gl_TessLevelOuter[2] = ???
-    // gl_TessLevelOuter[3] = ???
+	gl_TessLevelInner[0] = 1.0;
+	gl_TessLevelInner[1] = 5.0;
+	gl_TessLevelOuter[0] = 5.0;
+	gl_TessLevelOuter[1] = 1.0;
+	gl_TessLevelOuter[2] = 5.0;
+	gl_TessLevelOuter[3] = 1.0;
 }
diff --git a/src/shaders/grass.tese b/src/shaders/grass.tese
index 751fff6..14877e7 100644
--- a/src/shaders/grass.tese
+++ b/src/shaders/grass.tese
@@ -10,9 +10,33 @@ layout(set = 0, binding = 0) uniform CameraBufferObject {
 
 // TODO: Declare tessellation evaluation shader inputs and outputs
 
+layout(location = 0) patch in vec4 tese_v1;
+layout(location = 1) patch in vec4 tese_v2;
+layout(location = 2) patch in vec4 tese_up;
+layout(location = 3) patch in vec4 tese_dir;
+
+layout(location = 0) out vec3 nor;
+layout(location = 1) out vec2 uv;
+
 void main() {
     float u = gl_TessCoord.x;
     float v = gl_TessCoord.y;
 
 	// TODO: Use u and v to parameterize along the grass blade and output positions for each vertex of the grass blade
+
+	vec3 v0 = gl_in[0].gl_Position.xyz;
+	vec3 a = v0 + v * (tese_v1.xyz - v0);
+	vec3 b = tese_v1.xyz + v * (tese_v2.xyz - tese_v1.xyz);
+	vec3 c = a + v * (b - a);
+	vec3 t1 = tese_dir.xyz;
+    vec3 c0 = c - t1 * tese_v2.w * 0.5;
+	vec3 c1 = c + t1 * tese_v2.w * 0.5;
+    vec3 t0 = normalize(b - a);
+	nor = normalize(cross(t0, t1));
+
+	float t = u + 0.5 * v - u * v;
+    vec3 p = (1.0 - t) * c0 + t * c1;
+	uv = vec2(u, v);
+
+    gl_Position = camera.proj * camera.view * vec4(p, 1.0);
 }
diff --git a/src/shaders/grass.vert b/src/shaders/grass.vert
index db9dfe9..c4ffb82 100644
--- a/src/shaders/grass.vert
+++ b/src/shaders/grass.vert
@@ -2,16 +2,37 @@
 #version 450
 #extension GL_ARB_separate_shader_objects : enable
 
+//gl_VertexIndex
+
 layout(set = 1, binding = 0) uniform ModelBufferObject {
     mat4 model;
 };
 
 // TODO: Declare vertex shader inputs and outputs
 
+layout (location = 0) in vec4 v0;
+layout (location = 1) in vec4 v1;
+layout (location = 2) in vec4 v2;
+layout (location = 3) in vec4 up;
+
+layout (location = 0) out vec4 tesc_v1;
+layout (location = 1) out vec4 tesc_v2;
+layout (location = 2) out vec4 tesc_up;
+layout (location = 3) out vec4 tesc_dir;
+
 out gl_PerVertex {
     vec4 gl_Position;
 };
 
 void main() {
 	// TODO: Write gl_Position and any other shader outputs
+
+	tesc_v1 = model * vec4(v1.xyz, 1.0);
+	tesc_v2 = model * vec4(v2.xyz, 1.0);
+	tesc_v1.w = v1.w;
+	tesc_v2.w = v2.w;
+	tesc_up = vec4(normalize(up.xyz), 0.0);
+	tesc_dir = vec4(normalize(vec3(sin(v0.w), 0.0, cos(v0.w))), 0.0);
+
+	gl_Position = model * vec4(v0.xyz, 1.0);
 }