Troubleshooting - FastTrek Docs

Sometimes things don’t go as smoothly as we all hope. Here are a couple of troubleshooting tips when FastTrek isn’t doing what you expect.

Use the Setup Wizard

The wizard shows solutions to common problems:

• Optimise game settings
• Automatically install the Community Mod for large game windows (usually on 4k).
• Automatically adjust mod scaling settings.
• Test screen reading and keyboard input.

Setup Wizard Checks

Check the 'Start' tab

FastTrek's Start tab may show a warning to alert you to certain issues:

• The game window can't be 'seen'.
• The game has been resized.

Start Tab

Re-run ship detection

Ship detection underpins all ship-related functionality.

• Fix 'unknown' ship status.
• Fix ships not doing anything.

Ship Detection

No License or unable to contact server

If you see this message, it usually means that your firewall or antivirus is blocking FastTrek from looking up the license server’s IP address via DNS. The log file will then show entries similar to:

Unable to resolve host login.fasttrek.space after 3 attempts

Normally, FastTrek’s installer will automatically add an exception to your firewall, but some antivirus software may block it anyway.

If you are using a firewall or antivirus, please check that FastTrek is allowed to access the internet. You may need to manually add an exception for FastTrek in the relevant settings.

If you still cannot get FastTrek to accept your activation code, you can bypass the DNS lookup as follows:

This tells Windows to try either 172.67.160.131 or 104.21.9.140 as the IP address for login.fasttrek.space, bypassing the DNS lookup entirely.

Hostiles targeted, but no attack, then ‘Out of bounds’

The ‘out of bounds’ click is not a mistake. It is a deliberate click to reliably de-select any and all targets, allowing us to immediately re-target without running the risk of accidentally clicking into a dialogue box.

The most common reason is that the target is not considered ‘eligible’ for attack. Level restrictions are the most common cause, because OCR may misread the level of a hostile.

Other genuine reasons include:

• A mining node was targeted instead of a hostile.
• A player ship was targeted instead of a hostile.
• A housing planet was targeted instead of a hostile.
• The click missed and went into empty space.
• If the community mod maps ‘recall’ to the same key as ‘scan’, a mining node needs to be deselected before recalling a miner.

Known Limitations

Navigation

When using Solo Armadas, Cerritos, Hunter Bait, or other automations that involve multiple ships, multi-ship navigation may fail and/or loop under the following circumstances:

• Mirror Universe. The Cerritos can’t currently follow into the MU, but you can theoretically start the automation with both ships already there (not sure why you would, but hey)..
• Token Systems. If the lead ship uses the last available warp token, support ships will not be able to follow. Make sure you have enough warp tokens for all ships.
• Out of range. There is no warp range check on support ships. Make sure they can reach.

More help needed? Just ask!

I’m only an email away. If something isn’t working, please don’t give up, I’m sure it can be resolved.
Let me know and I’ll do what I can to help or fix the problem.

Log Files

FastTrek keeps detailed log files of what it thinks it is seeing and what actions it is taking. I will usually ask for the log if you ask for support with any kinds of unexpected behaviour.

To find the log file you can usually use the link on the ‘Start’ tab, which should open Windows File Explorer or MacOS Finder pointing at the right location.

If that doesn’t work, you can find the logs manually:

Platform	Log file location
Windows	%LOCALAPPDATA%\FastTrek\logs
MacOS	~/Library/Application Support/FastTrek/logs