{"id":9,"date":"2025-04-13T17:44:13","date_gmt":"2025-04-13T17:44:13","guid":{"rendered":"https:\/\/blog.metu.edu.tr\/e264325\/?p=9"},"modified":"2025-04-13T17:44:15","modified_gmt":"2025-04-13T17:44:15","slug":"haunted-library-ceng469","status":"publish","type":"post","link":"https:\/\/blog.metu.edu.tr\/e264325\/2025\/04\/13\/haunted-library-ceng469\/","title":{"rendered":"Haunted Library – CENG469"},"content":{"rendered":"\n

Welcome, dear Computer Graphics enjoyers!<\/p>\n\n\n\n

In this blog, I will talk about some details of my implementation for CENG469 Computer Graphics II homework and the challenges I faced.<\/p>\n\n\n\n

Curved Path Generation<\/h1>\n\n\n\n

I decided to start with this part as it seemed to be the easiest one. I implemented BezierCurve<\/code> class. Throughout the whole program, I keep one global instance of BezierCurve<\/code> class, which is instantiated with hardcoded control points at the beginning of the program. Each frame the t<\/code> parameter of the curve is increased by a hardcoded delta value. When the end of the curve is reached, we update the control points of the BezierCurve <\/code>class instance with the newly generated random control points, ensuring that the path is C1 continuous and stays in the scene bounds. The range of x<\/code>, y<\/code> and z<\/code> coordinates, in which the control points are generated, was found experimentally.<\/p>\n\n\n\n

In the later stage of implementation – when I already aligned the model to the path – I faced the following problem: despite being C1 continuous, the path didn’t feel smooth. I minimized this by regenerating control points which are too close to each other.<\/p>\n\n\n\n

Alignment and Rolling<\/h1>\n\n\n\n

The part I continued with was making Armadillo follow the path.<\/p>\n\n\n\n

At each frame, Armadillo is translated by the current point of the curve. Then I aligned the gaze of Armadillo with the current tangent of the curve as described in the specification 11 of the homework text. However, I faced the following problem: while following the path, Armadillo gradually “falls” to one side:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The interesting part is that this issue wasn’t present when I was calculating right<\/code> vector as a cross-product of the tangent and the world’s up, in contrast with calculating right<\/code> as a cross-product of the tangent and the previous point’s up (the up vector calculated in the previous frame). Neither was this solution suitable as Armadillo was often flipping, while following the path.<\/p>\n\n\n\n

I decided to combine these two solutions: using world’s up by default and prevUp<\/code> when the tangent and the world’s up are close to being parallel. This approach seemed to resolve the issue. Nevertheless, the ghost didn’t have this problem, so I used only prevUp<\/code> in the final implementation.<\/p>\n\n\n\n

Alternating rolling motion was done using glm’s built-in quaternions.<\/p>\n\n\n\n

Ghost<\/h1>\n\n\n\n

I designed ghost using five surfaces: four identical rotated surfaces and one concave <\/strong>bottom-surface (no holes in the mesh). Here are screenshots from MATLAB:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Each surface was rendered separately using the pipeline implemented in the template code.<\/p>\n\n\n\n

s=t=1<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=2<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=3<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=5<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=10<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=25<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=50<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

s=t=100<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Here is the final video showing all keyboard interactions:<\/p>\n\n\n\n