top of page

Work Experience Journal - Day 15

  • Jan 28, 2019
  • 1 min read

I asked the lead developer about why the multiple AIs have a chance to walk to the locator another AI has claimed and her respond is that every time the locator is called upon it gives the blueprints a random locator causing a random locator to be claimed while the AI walk to a completely different locator. To fix this the lead developer suggested promoting the random locator to a variable so it is only called once so it doesn't change when the locator is called but alas it didn't work.

Locator Array Blueprint (First Edit)

She replied "you're allowing them to go to it before checking if it's claimed. The branch should always come first. So put the set value thing after the branch." After following her advice it was still broken so she said to recreate the AI simply as it is a good way to find any bugs.

Locator Array Blueprint (Second Edit)

Today I learned about what is the best way to arrange and debug blueprints. Since most of visual scripting in Unreal involves problem solving, this will help me solve lots of problems in the future. I can't tell you how much time past me spent trying to debug a problem. I'm also becoming more and more familiar with arrays which before this job was very unfamiliar with. Just knowing about what is stored in an array allows me to use it in ways I could before.

Harvard Referencing

Sarter, R (2019) All images; 28 January 2019

Wood, S. (2019) Unreal. Discord; 28 January 2019 [online]


 
 
 

Comments


bottom of page