WEEK6

Introduction

Goals

I have been assigned work on the enemy AI system.

Advanced AI system prototype:

• a test enemy made of Cube object in the new navmesh scene to better test the single take cover behavior

The following is the primary author and any secondary authors who assisted in completing the tasks this week. 

• Primary - Serena
• Secondary -  

Technologies, Tools, and Resources used

The following are the technologies, tools, and resources to assist in completing the set goals this week.

[Unity AI TAKE COVER or HIDE dynamically // 3D]-

[Enemy Shoot, Run and Hide | Unity AI Tutorial]-

Key Tasks Undertaken

The following are the key tasks that were taken to help a developer/reader understand how the tasks were completed.

1.  Pull all the new updates from the source tree.
2. delete non-working player prefab in Enemy AI scene
3. using my test scene which is a new navmesh scene, create a new platform and bake navigation
4. doing research, to find the best and achievable methods 
5. go to unity and start learning the codes according to the research
6. figure out the "take cover" behavior how it works, also what would be the triggers to switch the behaviors
7. testing the methods I learned, and find out where is the problem that didn't make it work as same as the tutorials.
8. write done the logical I thought and make a simulation on papers to make a clear list
9. following my logic and make a new script to start over to write codes
10. extract status change codes to the new script as a base
11. write all the base codes there following the logic
12. filling the function codes to the right part
13. debug log each time to test if the last step is executing
14. setting layers for the player and obstacles that AI will seek hiding spots automatically 
15. the test player has been set player layer, all the building have been set as an obstacle layer
16. set the appropriate value to fill in 
17.  test several times making sure it won't be crashed
18. Save everything and push to the server

What I Found Out

Include any particular lessons learned, especially if this Spike was designed to cover knowledge gaps. Use Graphs, ScreenShots, Outcome Lists, or other Notes.

1.  Tutorials didn't always tell you the right answers
2. Value sets can straight affect the effects
3. Decision making is important to limit each function to be called at a proper time

Solution Justification

1. start over
2. write in my ways

Open Issues/Risks

List the issues and risks that you have been unable to resolve at the end of the spike. You may have uncovered a whole range of new risks as well.

• can not test it with the exact player I wanted to

Recommendations

• add the prototype To Enemy AI script
• thinking of if it is better to call the Take Cover function from cone view volume or just code a range in the script