martenscedric / comp371-project Goto Github PK

The application should handle the following input:

• The user can incrementally size up the model by pressing ‘U’ to scale-up and ‘J’
  to scale-down. Each key press should result in a small size change.

• The user can control the model position and orientation using keyboard input,
  i.e., A → move left, D → move right, W → move up, S → move down, a → rotate
  left 5 degrees about Y axis, d → rotate right 5 degrees about Y axis. You may
  add other rotations about other axis, if you want.
  2– The world orientation is changed by using keyboard input i.e. left arrow → Rx,
  right arrow → R-x, up arrow → Ry, down arrow → R-y. (Rx denotes a small anti-
  clockwise rotation about positive x axis, R-x about negative x axis, etc.) Pressing
  “Home” button should reset to the initial world position and orientation.
  – The user can change rendering mode for the model, i.e. points, lines, triangles
  based on keyboard input, namely, key ‘P’ for points, key ‘L’ for lines, key ‘T’ for
  triangles.
  – The user can pan and tilt the camera as follows:
  ∗ While right button is pressed → use mouse movement in x direction to pan;
  and
  ∗ While middle button is pressed → use mouse movement in y direction to tilt.
  – The user can zoom in and out of the scene - while left button is pressed → use
  mouse movement to move into/out of the scene.

We should be able to load those nasty float arrays from files.

We need a cubemap https://learnopengl.com/Advanced-Lighting/Shadows/Point-Shadows

The application must use OpenGL 3.1 and onwards and must include brief comments
explaining each step.

The user can incrementally size up the model by pressing ‘U’ to scale-up and ‘J’
to scale-down. Each key press should result in a small size change.

Add shaders from a file

Enclose the entire model in a big sphere (like bubble soccer and use triangle mesh
representations. You should have lower half of the model outside the bubble.)

The user can incrementally size up the Model by pressing ‘U’ for scale-up and ‘J’for scale-down. Each key press should result in a small size change (define deltachange in a variable)

Window resize handling: The application should handle window resize events and correctly adjust the aspect ratio accordingly. This means, the meshes should not be distorted in anyway.

If you pan the camera maybe around 45 degrees and then try to do a small Tilt, it will home it, looking at 0,0,0

For blending to work we need to draw far children first (otherwise transparent objects can hide others behind them).
We have to reorder children based on distance from camera before drawing.

One issue we currently have is that we can't easily add a new shader because how viewmatrix is unaccessible from the camera.

We need to reinvent the way we set the view matrix on the camera so each model can have a shader.

(Perhaps we should pass the camera to the models?)

The user can zoom in and out of the scene - while left button is pressed → use
mouse movement to move into/out of the scene.

A mesh is a set of polygons that share vertices and edges which describe the shape of
a geometric object. In this assignment you have to first create a unit cube in 3D at the
origin, then using appropriate modeling transformations create the third alphabet from your
first name and fourth digit from your student ID. (see Figure 1 – an illustration of a sample
output for a student name SAURIN SHAW with student ID 27391432) (U9)

Make the model move by moving the segments touching the ground (lower half
of the model), while also providing either lateral/vertical movement to the upper
half of the model. (One key of your choice for one small forward movement, and
other key for continuous forward movement. Same for reverse movement).

Illuminate the scene by adding a point light source (white) 30 units above the
model using the Phong model

The user can control the model position using keyboard input,
i.e., A → move left, D → move right, W → move up, S → move down.

The user can control the model orientation using keyboard input, a → rotate
left 5 degrees about Y axis, d → rotate right 5 degrees about Y axis. You may
add other rotations about other axis, if you want.

The user can pan and tilt the camera as follows:
∗ While right button is pressed → use mouse movement in x direction to pan;
and
∗ While middle button is pressed → use mouse movement in y direction to tilt.

Render the scene with tiled texture on the ground mesh, box texture on the
alphabet and shiny metal finish (color of your choice) for the digit (set key ‘X’
for toggling texture on/off).

The world orientation is changed by using keyboard input i.e. left arrow → Rx,
right arrow → R-x, up arrow → Ry, down arrow → R-y. (Rx denotes a small anti-
clockwise rotation about positive x axis, R-x about negative x axis, etc.) Pressing
“Home” button should reset to the initial world position and orientation.

All repeating items, like the trees in the virtual forest or the buildings in the virtual city, should be procedurally created, using a few user specified parameters,if necessary.

Render the scene with shadows using the two-pass shadow algorithm (set key ‘B’
to toggle).

Home button to reset world orientation

Different camera... You should have simple interaction mechanisms to navigate through the virtual world and view it from different angles.

The user can change rendering mode for the model, i.e. points, lines, triangles
based on keyboard input, namely, key ‘P’ for points, key ‘L’ for lines, key ‘T’ for
triangles.

We are currently on the XY one

The model should consist of independent parts so they can be rotated/moved on their
own. We recommend that you use hierarchical modelling, so that a single transforma-
tion applied to a model’s origin will apply it to a complete model.

Let's just do it green-ish and yellow like in the pic

Place a virtual camera with the world space origin as the point of focus. For display
and animation:

• Create a GLFW window of size 1024x768 with double buffering support.
• Render the coordinate axis, ground and all the models in the window.
• The application should use a perspective view to display all the objects and enable hidden surface removal.

Let's use blue, green and red like in here