G4U55

Untitled

Aug 11th, 2020
126
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.81 KB | None | 0 0
  1. WHAT WE FIXED:
  2.  
  3. GAMEPLAY
  4.  
  5. H4CK 4LL 7H3 7H1N95
  6. Ever messed around in Piazza and had a robot run off with your precious data? Well no more! You can now reset MINOS circuits in Piazza.
  7. No more lurking at the vending machine to get your data back!
  8.  
  9.  
  10. WAIT HOW DO YOU KNOW ALL THAT?
  11. Foster knew too much. He now knows less.
  12.  
  13.  
  14. HINT LOGIC IN APARTMENTS
  15. The engine now has a better understanding of what the player is thinking
  16.  
  17.  
  18. HUNTING FOR CLUES IN APARTMENTS
  19. ..or as its referred to internally: "Loz's Crazy Palace of Code"
  20. We realized the puzzle was a little strict, and the game now lets you discover things in more than just one order.
  21.  
  22.  
  23. WHAT COSTUME SHALL THE POOR BOY WEAR
  24. At some point during the game, Foster would just wear something completely different for no apparent reason.
  25. Unless of course someone had put a space at the end of the costume name the engine tried to reference.
  26. That would then lead to weird referencing issues. That would have been embarrassing :)
  27.  
  28.  
  29.  
  30. TECHNICAL
  31.  
  32. THE MINOS PUZZLE THAT LEFT YOU BAMBOOZLED & STUCK
  33. Do not untag this unless you know exactly what bug we're talking about here:
  34.  
  35. Why did this happen:
  36.  
  37. TL;DR: GG. We played ourselves.
  38.  
  39. How we fixed it:
  40. Huge shoutout to your fellow gamers over on Steam who shared their gamesaves with us, and walked us through what went wrong.
  41. Due to it being a loading issue that got you stuck we had to save the game in a very specific condition,
  42. in order to experience the loop people were stuck in.
  43.  
  44. Unfortunately we could not change this in existing gamesaves without risking people without this issue getting strange results,
  45. so we have to ask you to reload from your last gamesave.
  46.  
  47.  
  48. CAMERA IMPROVEMENTS
  49. When standing too close to walls or objects with your back, the camera could sometimes go inside a character model,
  50. or even yeet itself into the next room over, which in turn dulled the audio like you were eavesdropping on your own game! - Well no more!!!
  51. Cameras now understand that they are better than walls, and can, in fact, overrule them.
  52.  
  53.  
  54. RUNNING UP THAT RECYCLING CENTRE
  55. When walking to a very specific spot in Recycling Centre, you could wiggle into a spot that would make you fall through the world,
  56. resulting in many being able to walk around the city floor! One of the cooler bugs.
  57.  
  58. Why did this happen:
  59. Just collision bounds issues, you wouldn’t understand..
  60. What you visually see in games doesn’t necessarily exist as a solid object. The job of telling you which objects are solid,
  61. and what gives you resistance, and by how much, is down to a completely separate system.
  62. A lot of these resistance meshes keep a simple geometry (think hitbox). But yeah. In a shocking plot twist nothing is real in Unreal Engine.
  63. Does just what it says on the tin.
  64. Anyway, a small gap did not have enough resistance and it meant you could shimmy down where you should absolutely not!!!
  65.  
  66.  
  67. LITTERING
  68. Really, Foster?
  69.  
  70. Why did this happen:
  71. It’s not Foster’s fault really. While bin animations were standardised, the height of bins across Union City was not.
  72.  
  73. Additionally:
  74. When you interact with an object that has a specific animation attached to it, for example the Spankles vending machine,
  75. what is really happening is that you the Player, are travelling on a NavMesh:
  76. Imagine the map being covered in green blankets that AI can travel on and when you, the Player approach a location to interact with an object,
  77. it has an animation attached to it (like the Spankles vending machine).
  78. Now Imagine that NavMesh is not lining up correctly - that would lead to all kinds of nonsense.
  79.  
  80. In conclusion:
  81. Foster is blaming his terrible aim on incorrect bin heights, and standing too far off to be able to make the shot.. okay.
  82.  
  83.  
  84.  
  85. NPCS
  86.  
  87. EMBER
  88. This was a very rare occurrence, but for some players Ember would be impossible to interact with.
  89.  
  90. Why did this happen:
  91. This was due to the indicator; the little white circle.
  92. Unreal Engine knows when you, the Player, are looking at for example Ember, and will make the indicator appear, thanks to a timer.
  93. Now imagine someone was constantly resetting that timer because they told Unreal Engine that something moved when it was not looking.
  94.  
  95. Basically Ember was convinced she had to approach a particular spot that didn’t necessarily exist. She couldn’t cope with that failure and kept resetting.
  96.  
  97. Never being in one place long enough for you to look at her, and for the indicator to appear, Unreal Engine translated this to: no actions available..
  98.  
  99. It's like when you ask your dad for something he knows mum said no to. Well, we overruled them both.
  100.  
  101.  
  102. YOU CAN’T GET THE STAFF THESE DAYS
  103. The Apartment Cleaning robot was having trouble with a couple of things, including with how much water was currently in it.
  104. This alone is forgivable, but it made life really hard for poor
  105.  
  106.  
  107. THE FOSTER LEAN™?
  108. A little similar to the NavMesh issue, when Foster would approach an object, like a door, we would tell your character model to get
  109. "in position to THIS LOCATION " to start this animation.
  110. We set the approach location where Z is 0, but because it was relative to another in-engine approach arrow that was slightly moved,
  111. and set Z to (for example) -30, basically instructing Foster to limbo through the door.
  112. Foster is an obedient boy.
  113.  
  114.  
  115. 2 SLOW 4YR GUNS
  116. Foster is not a vehicle and is not allowed to enter Union City without one.
  117. When stepping into the entrance area 2 very helpful lasers will inform him to move his meaty butt out of the entrance zone in 10 seconds or less; or else.
  118.  
  119. While 4YR is a valued employee bot, and is welcome to shuttle through this zone.
  120.  
  121. BUT: If Foster interacts with 4YR while lasers are pointing at him counting down from 10, the countdown doesn’t just stop until you two are done talking!
  122. In fact Foster would be mercilessly taken out with a dramatic death scene.
  123.  
  124. Except, after dying… he’d just get back to chatting up 4YR?!
  125. We put an end to this nonsense!
  126.  
  127.  
  128. 4YRIDE INTO THE SUN
  129. In a horrific oversight, some of you figured out how to ride 4YR like a steed.
  130.  
  131. Why did this happen:
  132. “Step up” is enabled by default and we forgot to switch it off on the
  133. So while you can not “step up” on 4YR in general, you could totally do it while
  134. Lead to some truly amazing gifs though..
  135.  
  136.  
  137. LET GRETA REST
  138. You used to be able to catch another conversation with Greta the Hologram, just when she was about to fade out, making her invisible!
  139. We made sure she can shut herself off in peace now.
  140.  
  141.  
  142. PANIC! AT THE MUSEUM
  143. In the Museum the father & daughter duo were completely different AI to the generic museum NPCs,
  144. and therefore had the intelligence to avoid running into eachother, but did not have the faintest clue to walk AROUND these other, alien NPCs.
  145. No more traffic jams!
  146.  
  147.  
  148. DIVA ALONSO
  149. Basically there is a scene where Alonso should be leaving dramatically!
  150. But if you, the Player, left before him, Alonso would just stay there and pout, because you ruined his exit.
  151. It took a while but he should no longer throw a tantrum over the theft of his dramatic exit.
  152.  
  153.  
  154. MUSEUM INFO BOT
  155. The overbearing little guy used to be able to corner Foster, and make it unable for him to leave. We sorted that out.
  156.  
  157.  
  158.  
  159. ART
  160.  
  161. ORANA’S SKIRT: Much more comfortable now that it doesn’t clip into her.
  162.  
  163. ADS: The Advertisements around you now tie in with world building better.
  164.  
  165.  
  166.  
  167. ANIMATION
  168.  
  169. CHAIRS & DESKS: We had to re-explain to some NPCs how sitting works.
  170.  
  171. JIMMY: Used to be shy about talking in cutscenes. Gave him a little confidence boost.
  172.  
  173. CUTSCENES: Scrubbed, and now very polished!
  174.  
  175. FOSTER’S DEATH STARE:
  176. This one was interesting: It only happened after Foster changed into another outfit.
  177. No head or face animation would work anymore, except for lip sync which runs on a completely different system.
  178. We figured out that this was due to the blueprint of the animation being referenced by the outfit.
  179. So if Foster’s old outfit was gone this code wouldn’t replace the reference it was looking for until you either entered a transition scene,
  180. or reloaded manually.
  181. Foster now uses b e s p o k e live references
  182.  
  183.  
  184.  
  185. UI
  186.  
  187. HACKING ON GAMEPAD NOW MUCH SMOOTHER: weeeeeeeee
  188.  
  189. QDOS LOGIC: clearer flow of how Foster learns information
  190.  
  191. BONSAI: Displays as it should
  192.  
  193.  
  194.  
  195. AUDIO
  196.  
  197. NO MORE SELF INTERRUPTING:
  198. Sometimes a computer would take longer to load in and start dialogue lines, and that would mess with the timings as those delays were not accounted for,
  199. resulting in NPCs interrupting themselves when speaking. We now make sure that the audio finishes before the next one can queue.
  200.  
  201.  
  202.  
  203. PERFORMANCE
  204.  
  205. GAMEPAD CONTROLS: smoother, better, faster, less awkward
  206.  
  207. OPTIMIZED CITY SHADERS & GEOMETRY: shiny & pointy
  208.  
  209. OPTIMIZED TEXTURE COMPRESSION: smaller & snappier
  210.  
  211. GLOBAL MEMORY REDUCTIONS: less means more
  212.  
  213. LEVEL TRANSITIONS: more loading, less crashing
Advertisement
Add Comment
Please, Sign In to add comment