Rather than working on the entire AR scene at once, I worked on individual elements separately. The original scene had become quite complex, and if something went wrong, troubleshooting would have been difficult. By developing and testing each component individually, I can make sure they function properly before integrating them into the main environment. This approach also minimizes the risk of having to redo large portions of the work, making the process more efficient.
The first major task I focused on was animating the character and creating a smooth sequence. This character is part of Yupu's installation, where he is seen sitting and typing on a CRT monitor. I used proximity-based interaction: when the viewer moves close to him, he stops typing, turns to face them, stands up, waves, and starts a dance sequence. After finishing, he sits back down, rotates back, and continues typing. To enhance this experience further, I will add a voiceover. I tested voiceovers in my last post, and implementing them is straightforward. I just need to finalize the script and anchor the audio to the character's animations.
I also resolved a previous issue where the video wasn't playing when the scene was running. The problem was due to the video format, and I fixed it by converting the file into an image sequence. Now, the video runs without any errors. Additionally, I incorporated more 3D objects that align with our theme and added a frame for Bato's video projection on the wall. This helps reinforce the blend between digital and physical realities.
Recording 2025-02-13 153734.mp4
Recording 2025-02-13 153853.mp4
One significant challenge I faced was that the scene kept crashing when I tried running it on my iPad. The last time this happened, I had to completely rebuild the scene from scratch. However, since I've been working on separate components this time, I can avoid that issue. My plan is to finalize all elements individually and then integrate them into a newly recreated scene this weekend before user testing begins.