Bug - Hard Drive Crashing

Farthest Frontier Bug Reporting
1

I have recently downloaded the update and now have a bug which I will try my best to describe. I have the game installed on an hdd (G:), the save file is in my documents folder which is on a different hdd (E:). Finally, I have Windows installed on an M.2 (C:).

I keep running into a problem where I play for about 5 minutes (on a save I had previously been playing on before the update), and then when it attempts to auto-save or I manually do it, it informs me that the drive cannot be found and so cannot save - it is referring to drive (E:). I am then unable to access my drive (it doesn’t show up in file explorer and all data installed on it becomes unavailable - inc. my desktop etc…), although it is still registering that it is there in partition manager but not correctly. To fix it, sometimes restarting my PC works, otherwise I have to unplug and then plug the drive back in and it then works. There are no errors coming up on the drive and it is interesting that it is the drive with the save on it that is having issues - not the one with the game installed on it which is operating completely fine. The (E:) drive has plenty of space available and I have never had an issue with it before, and it only happens when I am playing the game. I believe I am able to save successfully for a short while when I first launch the game, as I can hit save and it doesn’t produce an error and my drive is fine.

Happy to send any error logs or any other details if you want them and hope this is useful. :slight_smile:

2

That is a pretty bad sign if Windows cannot access the drive. The game is only able to access what the system tells it exists. To my knowledge, a piece of software cannot fundamentally make a drive disappear from your system.

You want to consider replacing that drive. Or checking power draws…difficult to say what’s going on here, but the game may be exposing something wrong.

We have members of the team that have the exact setup you have (windows on C, game on another drive, and saves on yet another), without issue.

3

I have been in a similar situation and, as far as I can remember, the problem was related with some security settings about the protection of some folders, specially those located at the user set of folders. Again, as far as I remember, I fixed it giving FF (the app) the permission to write on this protected folder. It could be done through the security control panel, can’t remember where exactly. Without this permissions the apps can’t even see the folders…

The fact that it can happen after an update can be caused because windows identifies the update as a new app, and removes the old permissions…

I hope this can help.

4

Change to a solid state drive?

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.