Conceptual
I had a really tough time locking down my idea for experiential. Even after the proposal, there were just nothing special in utilizing what Augmented Reality (AR) can do. I went back to mind mapping and still nothing that could spark my interest.
All the ideas I came up with sounded boring, so I had just shut down any new idea I had. Amongst the ideas are:
I had a really tough time locking down my idea for experiential. Even after the proposal, there were just nothing special in utilizing what Augmented Reality (AR) can do. I went back to mind mapping and still nothing that could spark my interest.
All the ideas I came up with sounded boring, so I had just shut down any new idea I had. Amongst the ideas are:
- Japan Guide Map
This was supposed to be a plain map of japan or a certain part of japan, vector illustrated. Then, once scanned, it would show what you can do in that certain part of japan. And when you click at those areas, it would reveal more information about that place. The reason why I didn't go with that idea is that it's not that interactive and you can easily find the information online instead of scanning. - Memory Card Game Color Theory
Memory with paired cards game was a way to teach people the color theories. Instead of pairing with the matching visuals, they pair it with a complementary color. For example, Red with Green, Blue with Orange and etc. - Postcards
Self-explanatory, a postcard artwork in motion. - Greeting Cards
People can give each other greeting cards and they can see animations on the characters and the text of the card depending on the occasion.
I think the main reason why I hadn't used any of these ideas is because it didn't sound efficient, fun or interactive. Even if some of them are, I had put too much expectations for it to be good before I executed it. But sadly, I made it get the best of me and spent too much time on it that affected the end product of my Experiential Design project. Yes, this is definitely a huge lesson learned, to not spend too much time figuring something out, if it doesn't work just do something else.
Technical
In the technical side, my learning process regarding AR has been through doing my initial idea for Personal Project 1 module. Since Week 6, I was just trying to get the camera texture to appear on a 3D plane and animate that camera texture. It had worked when I wanted to get the camera texture but not animating it.
When it animates, it doesn't repeat the texture, it becomes like this:
While if it's just a normal texture, it repeats:
Since my plan for Personal Project one didn't work. I had abandon that AR project. Then, I picked it back up and try to see whether I can do something with it for Experiential design. I had try to export it to Xcode, but there were too many errors, so then I didn't end up using the abandoned project.
Then, I tried out tutorials such as Markerless AR that show the GPS, Maze Game and Vuforia Button Hover.
The markerless AR tutorial was outdated since the guy wasn't using Vuforia AR Camera, so I had tried to translate that into by using the AR Camera. After doing so, the positioning of the ship moved along with the camera instead of just staying where it is. I continued on with the tutorial anyways but then there was a fault in the scripting and I couldn't figure out why. So I tried another tutorial.
 |
| This is the camera reflecting the camera view without the use of Vuforia AR Camera |
The other tutorial was the maze tutorial game. Once scanned, the ball kept going out of the maze and is on repeat and since I was running out of time, I couldn't figure out why it wasn't working. I did the UI elements for the app, but since it didn't work, I didn't use it.
I did the hover button with the help of Mr. Razif and of a friend. I made a runaway for the model to walk on. Once the press me is hovered, the model would walk.
 | ||||
the runaway
|
I wasn't happy with what I made, so I went to look back at the maze and tried to fix the problem. Turns out the problem was that the ball kept going out the maze on the z index and that's why it had appeared and kept going out of frame. So I had put a plane above it so that the ball won't go out of place like so:
Then, I attached all the UI scenes together. I wanted to have a UI indicating to scan the maze, but again I had to skip that part due to time constraints. When, I played it, every UI element seems to work fine until the part where the ball goes to the exit point, I set a trigger to go to the next scene, but it kept saying "Fatal error!Allocating memory when it is not allowed to allocate memory" every time the ball passes through the trigger. After looking up why it keeps coming up, most of the forums say it's because of the new updated Unity is not compatible with Vuforia, which makes sense since I had recently updated my Unity. So, it's just an error within Unity, so I had exported it to Xcode, and it worked just fine. The only thing I wish I could fix was the Scan the Maze UI. I also wished to add a timer and a background music but now I know I need to manage my time more wisely.
I would like to thank Mr. Razif, for supporting and trusting me with the problems I faced. Without him, I would've been a lost cause.
