{"id":80,"date":"2025-09-05T20:14:00","date_gmt":"2025-09-05T20:14:00","guid":{"rendered":"https:\/\/projects.etc.cmu.edu\/ascent\/?p=80"},"modified":"2025-09-22T22:01:34","modified_gmt":"2025-09-22T22:01:34","slug":"week2-prepping-for-1-4s","status":"publish","type":"post","link":"https:\/\/projects.etc.cmu.edu\/ascent\/week2-prepping-for-1-4s\/","title":{"rendered":"Week2: Prepping for 1\/4s"},"content":{"rendered":"\n

Design Meeting<\/h3>\n\n\n\n

After our brainstorming and workshop in Week 1, we started shaping a clearer idea of the kind of experience we want to create for our guests. Since we are still exploring different technologies and haven\u2019t settled on an engine yet, we agreed that the experience needs to be simple while still captivating.<\/p>\n\n\n\n

Through several discussions, we narrowed our ideas down to two possible directions. The first is a narrative-driven \u201cstory of life,\u201d where we guide guests through a hiking journey enriched with storytelling. The second is a meditative \u201cpath of scenery,\u201d which focuses more on the environment, views, and reflective moments.<\/p>\n\n\n\n

To support these ideas, we created a rough map and user journey. This will help the art team start visualizing the space and dive deeper into researching what kind of landscapes we want to bring into the project.<\/p>\n\n\n\n

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

Map & User Journey<\/p>\n\n\n\n

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

Dynamic moments art references <\/p>\n\n\n\n

Prepping for 1\/4s<\/h3>\n\n\n\n
\"\"<\/figure>\n\n\n\n

With our core experience defined, we shifted our focus this week toward preparing for our upcoming Quarters presentation. This presentation is a key milestone for us, as it not only allows us to share our progress with faculty and peers but also helps us clarify our goals, identify challenges, and gather valuable feedback that will guide the rest of the semester.<\/p>\n\n\n\n

On the technical side, our team carried out several rounds of testing with different tools and devices. Some of the technologies we explored were only compatible with Unreal Engine, while others seemed to work better with Unity. This has been a challenge, since the choice of engine will affect nearly every part of development. For now, we are keeping both options open while we continue testing. To avoid being locked into a single direction too early, we also made sure that our early work, including prototypes and art assets, can migrate between engines if we eventually need to switch. This flexibility has been important for us, as our project heavily depends on foot-tracking technology and we want to ensure that our final decision is based on stability and performance rather than convenience.<\/p>\n\n\n\n

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

The art team took a deeper dive into visual research this week. We explored different art styles that could match the tone of the experience and also tested small prototypes in engine to see how these styles might feel in VR. Beyond just the aesthetic appeal, we also studied the production pipeline, understanding what steps, tools, and workflows are required to achieve certain looks, and how feasible they are within the scope of our semester project. The goal is to land on a style that is both beautiful and achievable, while also supporting the type of emotional experience we want to deliver.<\/p>\n\n\n\n

At the same time, we began refining our design documentation. Although we have a general direction, a VR hiking experience, we recognized that we were still a little lost when it came to focus. Without a fully confirmed technology pipeline, it can be difficult to anchor design decisions. To address this, we revisited our two main design directions: one leaning into a narrative-driven journey that tells a \u201cstory of life\u201d as the guest hikes, and the other focusing on a meditative \u201cpath of scenery\u201d that emphasizes the beauty of the environment. We created a rough map and user journey for each version, which not only gave the art team a starting point for visual research but also helped us clarify what kinds of interactions and pacing might be required.<\/p>\n\n\n\n

Preparing for Quarters has been as much about refining our message as it has been about refining our work. We want to communicate clearly what we have achieved in these first few weeks, what decisions are still in progress, and what risks we are facing. Even though we don\u2019t yet have our ideal tech solution in hand, we see this presentation as an opportunity to be transparent about where we are, what we\u2019ve learned, and how we plan to move forward.<\/p>\n\n\n\n

\n
\n

Tech Test<\/h3>\n\n\n\n

Good news:<\/strong><\/p>\n\n\n\n

    \n
  • Worked.<\/li>\n\n\n\n
  • Implementation is not very difficult.
    <\/li>\n<\/ul>\n\n\n\n

    Bad news:<\/strong><\/p>\n\n\n\n

      \n
    • Barely any documentation for this model.<\/li>\n\n\n\n
    • Only one function (moving forward) worked. Other functions didn\u2019t.<\/li>\n\n\n\n
    • Loco S (the model we have) is NOT listed as supported in the SDK.<\/li>\n\n\n\n
    • The plugin for engine is not ready-to-use. May need a lot of efforts getting it to work.<\/li>\n<\/ul>\n\n\n\n

      Our Main Challenge<\/h3>\n\n\n\n

      No ideal tech at hand. <\/strong><\/p>\n\n\n\n

      Tech to be expected:<\/p>\n\n\n\n

        \n
      • Brilliant Sole: before halves?<\/li>\n\n\n\n
      • Omni-directional treadmill: within a month?<\/li>\n\n\n\n
      • OptiTrack: large space & long setup<\/li>\n<\/ul>\n\n\n\n

        How will we design for current tech to make it transferable to later tech?<\/p>\n<\/div>\n\n\n\n

        \n