Skip to content

Home

Jump to bottom
Yue Wu edited this page Jun 15, 2019 · 18 revisions

This is the home page for the documentation of Bodylogical AR iOS.

READ BEFORE YOU WRITE CODE

You should probably return to this after you finish reading the documentation. It is included here to raise awareness.

  1. Do NOT arbitrarily switch target. Sometimes, when Unity crashes and you reopen it, it would complain about unsupported target and asks to switch target to PC standalone. In this situation, try restarting your computer. It takes about half an hour (depending on your computer's configuration) to switch back to iOS after you switch to standalone, so please don't do this unless restarting does not work and it is the last resort.

  2. Whenever a new text component is added, change

  • Its font to Helvetica (or whatever font PwC agrees or we have experimented),
  • Its color to white (white looks clearer in multicolored backgrounds),
  • If this text requires localization, add LocalizedText script and set the key and parameters accordingly.
  • Even if the content is determined at runtime (e.g., the id is unknown until the user makes a decision), still put some placeholders to remind yourself what this text is for and to enable layout design.
  1. Whenever you want to replace a human model with another, in the prefab,
  • Add a capsule collider and a HumanInteract so that they can be selected by the user.
  • Add a PinModel to the model. This is because the animations we have will shift the human's position and rotation. To have better control of the model's Transform, we have to "freeze" their position and rotation, and then control their parent object's Transform.
  • Set the animator to Archetype.

Overview

This app is intended to demonstrate the functionalities of PwC's Bodylogical simulator. Bodylogical is a health data simulator where, given a person's lifestyle data (food intake, exercise/workload, sleep, prescription adherence), calculates different data to predict his/her future life. This app's users will be PwC's clients, and app will be used in meetings where PwC staff promote the simulator to the potential simulator buyers.

The main game logic is as follows: user finds a plane large enough to place a stage -- user chooses an archetype to simulate -- user reads the character's background story, and examines the lifestyle data -- user observes the archetype's activities -- user discovers "surprises", such as an inability to keep jogging -- user goes to Internals to see the problem with the organs -- user goes to Line Chart to see the numbers -- user changes paths to observe the changes to numbers -- user switches back to Activity/Internals to see how the archetype becomes.

Project Structure

All imported assets go to Assets/Imported, the only exception being modded assets, which goes into the regular directories. The main scene is Scenes/MainScene, and the others are for testing.

Assets/Resources store data to by dynamically loaded at runtime. However, some of those are expected to be downloaded from a remote server (so that PwC can modify archetype data easily, without us having to recompile the app each time) and should be removed from Resources once the server is set up.

Scripting Structure

Other Reference

Clone this wiki locally