V 1.0 CTD before map loads

Farthest Frontier Bug Reporting
1

DxDiag Farthest Frontier Crash Oct 23.txt (93.8 KB)

Crashes every time after progress bar reaches end (or almost end). Prior early access versions worked fine. Drivers are updated.
See attached DxDiag & one of the crash dumps.

crash.dmp.txt (411.7 KB)

2

Does this happen with a saved game, new settlement, or both?

3

I never get far enough to actually save a game, but when I restart I do have a “Continue” option. Clicking that also causes the game to crash. When I click “Load Game” I only see saves from back in 2023 & 2024. For what it’s worth, there is a single save file with a recent timestamp. It’s just not visible from within the app. See attached

steam_autocloud.vdf.txt (51 Bytes)

4

Me too have crashes after load playtest load. During fight with invanders.

5

So you’re start a new town and the load bar never finishes and you crash?

Did you verify game files? Are you running any mods?

6

Yes. I start a new town. The load bar gets to about 80%. Then the game crashes.

Yes I verified the game files. Have also uninstalled & reinstalled the game.

No I am not running any mods.

I’ve started getting an application error popup. See attached
IMG_1654

7

Can you share your dxdiag please?

image

image

8

Isn’t that the very first file attached to my initial bug report? Are you having trouble opening it or something?

10

Ah sorry, missed it earlier.

So looking at your dxdiag and the crash dump, it is not just the game that is crashing, but a number of nvidia apps (NVIDIA Overlay.exe, nvapi64.dll (drivers), etc) as well.

I wonder if you may need to do a clean reinstall of your drivers. A more long shot could be issues with your memory (RAM) being faulty.

Something you can also try, though I don’t like recommending this, is whether the mono build (one of the launch options intended for playing with mods), has the same issue for you.

Finally, you can try the debug build to see if anything changes:
In your Steam library:

  • Right click Farthest Frontier.
  • Choose “Properties”.
  • Select the “Betas” tab.
  • Enter the access code “42HPFe7duhHN”.
  • Hit the “Check Code” button.
  • Select the debug branch in the dropdown box.
11
  1. No worries on overlooking the DXDiag file. I can only imagine how busy you guys are the day after launch.
  2. Did a clean install of graphic drivers. Same crash at 80%
  3. With mono build I get a stack overflow error at 80% load
  4. Turned off virus scanner - got an exception breakpoint error at 80% load
  5. Tried debug build. This one only got to 20% load before crashing

I’m not expecting you guys to work on this anymore. Since nobody else has chimed in with same error this is clearly some kind of one off thing involving my particular computer & this particular version of the app. I’ve been playing since 2023 so looking forward to playing this game. I’ll try again after your first post-launch patch. If I still can’t get the game to run I’ll ask for a refund, but I sincerely hope it doesn’t come to that. Best of luck.

12

It is entirely possible the issue is system end (as I said, it is possible the RAM is faulty), but we’re going to push another debug build that includes more logging. Will let you know when it’s up for you to try.

13

That build is up, you will need to restart steam for it to download if you are still in the debug branch.

Note, it will run slower than what you are used to due to the additional debugging running.

Give that a go and see what happens, if you get any red errors. You can share the log afterwards.

Thanks!

14

Make sure the version says “v1.0.0d2” so you know you have the updated version.

15
  1. I ran MDSCHED to check the memory. It didn’t report any errors
  2. Downloaded new debug v1.0.0d2 (20592M). It stopped twice with “Content Unavailable” but retrying got it all the way downloaded & installed. Launched & got to about 20% and crashed. Here are 2 files from the crash directory.
    crash.dmp.txt (734.5 KB)
    Player.log.txt (63.3 KB)
16

Thanks for sending those in. I’m still not sure what’s going on yet. It appears that you are running in Exclusive Fullscreen, is that correct?

image

If so, can you try with Windowed Fullscreen?

image

or

image

… and let us know if that helps?

17

I turned off Vsync to match the screenshots above. Tried Fullscreen & Fullscreen + Windowed Fullscreen. Those hung at 80% (killed the task after 20 minutes & 40 minutes respectively). I don’t see a way to do the third screenshot where Windowed Fullscreen is selected without Fullscreen, however I did try it with neither Fullscreen or Windowed Fullscreen selected. That crashed. No crash files were generated in any of the cases.

18

Have you tried using runtime libraries or DirectX repair tools to fix this error?

01

02

03

19

Hmm. This seems like a promising path. Is this Game Runtime Libraries Package automatically distributed & installed when installing Farthest Frontier on Steam? Or are these components expected to already be installed on the PC (or installed separately)?

20

Sorry, I am not sure which runtime libraries Steam will install on my computer. Usually, common runtime libraries are pre-installed on the computer system, but a computer capable of running games may require additional runtime libraries.When I encounter game errors on a new computer, I will first try to update or install the runtime libraries.