charlieamat

1. Click anywhere in the CPU Usage graph
   • We can see that our Update method is taking up a much larger portion of the frame
2. Change the bottom section of the profiler from timeline to hierarchy view
   • The timeline view is a good visualization, but the hierarchy view provides more actionable information
3. Order the hierarchy view by “Time ms” and expand “PlayerLoop” all the way down to the script logic
   • By ordering the view by “Time ms” we can narrow down what is taking the CPU so long to execute
   • FindObjectsOfType is taking up some time, so let’s fix that
4. Switch to Visual Studio
5. Convert interactables to a private member variable
6. Initialize interactables in the Start method

charlieamat

// TODO

charlieamat

TODO

charlieamat

public class Combatant : MonoBehaviour
{
  public float Health;
  
  public void Damage(int damage)
  {
    Health = Math.Max(0, Health - damage);
  }
}

charlieamat

#TODO

charlieamat

using Interactions;
using NUnit.Framework;
using UnityEngine;
using UnityEngine.TestTools;

public class InteractionHandlerTests
{
    public class FadeOutTests
    {
        [UnityTest]

charlieamat

public class Interactable : MonoBehaviour
{
  private InteractionHandler[] _handlers;
  
  public void Awake()
  {
    _handlers = GetComponents<InteractionHandler>();
  }
  
  public void Interact()

charlieamat

public class FadingInteractable : Interactable
{
  [SerializeField] private float duration = 3;
  
  private Renderer _renderer;
  
  public void Interact()
  {
     StartCoroutine(FadeOut);
  }