Reporting Farthest Frontier Bugs (Please Read)

Here at Crate Entertainment, we are always committed to MOAR, but most importantly we are always committed to ensuring you’re all having a smooth gaming experience and enjoying your time with our work.

As Farthest Frontier has now entered Early Access, we wish to reassure everyone that we are looking at bug reports and hard at work on not only new features and content, but also bug fixes and optimization!

To facilitate this process on both ends, we have prepared a handy list of steps to follow on your journey to bug report-hood.

Note: if you are using any mods, we highly recommend trying to see if the issue persists without them. Mods are not supported at this time and they can generate issues that don’t exist in the actual game.

1. Existing Bug Threads
Has your issue already been reported? Take a quick look around the bug report forum. It’s possible someone else may have already discovered this problem. If you find an existing thread but have additional information that may help us track the bug down and fix it, then please reply to that thread rather than creating a new one.

Also check the Known Issues List as we may already be aware of it. :slight_smile:

Please do not bump bug threads. We read everything.

2. Posting a New Bug
When posting a bug, please include the build number in your title. You will find the build number in the lower right of the main menu.

Please be descriptive in your title. “Some bugs” is not descriptive.

Ex: “Boars have learned to fly - Build 123456”

Whenever possible, please post separate bugs in separate threads. If it is a collection of minor/related issues, it is fine to post them together.

If you are experiencing graphical, hardware or crash related issues, please provide your dxdiag with the bug report (see below for how to generate this file).

If the game crashes, it will usually generate a Crash Log. These can be found in your temp folder and can be very helpful for tracking down an issue if you include it in your bug report.

If your issue can be reproduced reliably with your save file, including it with your bug report will be very helpful! Your save files are located in My Documents.

Include as much information as possible in your bug description. Where applicable, include screen captures and repro rates.

Note that we will not be able to respond to every bug report thread. We are a small team focused on resolving old issues while also bringing you new content to enjoy. Because of this, we generally only post when we require additional information or if we have important information that we need to share. Rest assured that we are checking bug reports and that pertinent info is forwarded to the person most capable of handling the problem. Please note however that not all issues are created equal and their priority will vary.

Note: off-topic discussion may be deleted. In some cases, we will close bug reports if they are not bugs or if they have been fixed. Periodically, outdated bug report threads may be purged.

Thank you for your help in making Farthest Frontier the best gaming experience it can be! :smiley:


Graphics Bugs/Glitches

If you are reporting graphical bugs or glitches then please post up a DXDiag log along with screenshots of the issue.

  • It’s okay to upload a screenshot to an image sharing service for the purpose of bug reporting.

To generate a DXDiag log, hit Start and type “dxdiag” in the search programs and files box, followed by enter. Hit the button that says “Save All Information…”, save the file and attach it to your post.

Game Crashes
If the game crashes, it will usually generate a Crash Log. These can be found in:

This folder may be set to hidden by default in your folder options, so make sure to enable hidden items. Inside this directory, you will find a folder called Crash_Date_Bunch of Numbers (ex. Crash_2022-08-02_171459771.

Sharing Saves
At times, it may be helpful to upload a save in order to reproduce an issue.

Saves are located in:
C:\Users\USERNAME\Documents\my games\Farthest Frontier\Save

You will need to zip up the entire TownName_###### folder along with the .map file and .sav that reproduces the issue.