Cities of the Imagination

The different scenes in my thesis project were loosely inspired by cities in the book Invisible Cities by Italo Calvino. In the book, Marco Polo summarizes his travels to various different cities. The different cities are described in abstract ways, emphasizing aspects of each city. I chose some of the cities that spoke to me: Baucis, a city on stilts in the sky, and Armilla, a city full of pipes. I also created my own city, Ibislia, a lagoon of time.

Why the snail? In Ibislia, I wanted to draw attention to the way that time seems to move differently in cities and play with scale and speed in the imagery. Snails are small and slow, but what if they became big and fast? The fact that Marco can ride the snail and the fact that there is a Giant Ibis in the scene as well evokes a the question of: has marko shrunk or are the elements just really big?

Why the flying plant? In the chapter about Baucis, there is a moment where where Marco wonders why everyone in the city lives so high up. One of the hypotheses was that the people just hated dirt. My brother at the time was taking care of an air plant that just needed moisture and air to survive. I thought it would be interesting if the people in the city used the air plants as transportation, and so, the flying plant was born.

‍

The visitors to the exhibit would only be able to use a keyboard to navigate the three cities. In an effort to add variety I thought of different ways Marco would move around in each landscape and how the interaction would map to each key on a keyboard.

Armilla:He travels by foot in Armilla, so the controls mimicked those from 2D platformer game.

Baucis: In Baucis, all arrow keys can be used to move over a 2D plane.

Ibislia: To slide on the snail, I used the ragdoll runtime feature from Spine and had the user to apply force left and right with the arrow keys. This created a sliding effect. More on this later!

Menu: In the menu, I reused the movement mechanics in Armilla and had the user select which landscape they wanted to explore with the enter key when Marco was in the vicinity of the corresponding portal.

‍

‍

Throughout the development process in Unity, I playtested the application with friends and family and asked them to try to break the application while observing where they got confused and asked questions. As a result I implemented a few solutions:

Pop up instructions: I added instructions that would appear after a minute of inaction and when the visitor enters each landscape. That way, the instructions would hopefully appear between each gallery visitor's experience, and if not, if the user didn't understand how to move, would appear while they were trying to figure it out.

Boundaries and Restart Triggers: I implemented hard boundaries in Baucis and Ibislia that the player couldn't cross so they wouldn't get lost or go off the scene, and triggers in Armilla that allowed me to detect when the player object had fallen and restart the scene.

I had a hard time making the snail unbreakable as the code used the physics engine in Unity and there's a lot of unpredictability involved with how the ragdoll physics would interpret user input.

If the user put too much force on the snail, the snail would flip over and sometimes fly across the screen.

My solution: I decided to prepare for the inevitable and added ways to detect if the snail had flipped over so I could display a message to the visitor. After the message displayed, I sent the users back to the menu to try again.

An unexpected result is that the visitors found this to be one of their favorite moments of the display.