Reason Generator Inc has released a Wayward Terran Frontier: Zero Falls Update 0.9.3.02 today with its changes as we have listed here. In today’s update, the developer has fixed a bug problem that has been defiant in previous fixes. And now, let’s identify the official Wayward Terran Frontier: Zero Falls Update patch notes.

Wayward Terran Frontier: Zero Falls Update 0.9.3.02 Patch Notes

Earlier Fixes Today

  • Following the current update, the game had a few rendering-based crashes. Therefore, the developer has fixed the crashes.
  • There is also an additional crash logging for those exceptions, so it will be easier to find them in the future.

Later Fixes Today

The game developer has explained the reason for the multiple updates. In an attempt to solve the bug making the monsters invisible at times, the code would crash.

The developer has been writing codes to improve the rendering capacity of the monsters while in the corrupted state. However, the new codes have been crashing and failing to show crash logs from the previous version, 0.9.3.01.

Therefore update 0.9.3.02 should identify and solve the crashes from yesterday’s update. Fortunately, after another crash, the developer traced the problem’s source.

The bug effect on monsters has been on their pathfinding. The monster pathfinding error would return a NaN value (not a number), thus affecting the rendering progress of the monsters. For this reason, the monsters would then become invisible.

  • While solving the pathfinding error, there will be other fixes for bugs receiving the same issue.
  • For instance, there has been a bug causing crew members to do strange things when following you. This error has been solved using the pathfinding logic.

Wayward Terran Frontier: Zero Falls Update 0.9.3.02 has finally found and solved the bug making the monsters invisible, as in the official patch notes. You can download the update and the game on PCs via steam.

  • For instance, there has been a bug causing crew members to do strange things when following you. This error has been solved using the pathfinding logic.