Recently, Star Conflict fails to run. The launcher gives a message about a lot of files being corrupted and tries to repair and then gives this message. Nothing has been changed on my end. I removed the game and reinsrtalled the launcer and this still occurs.
Once I tried it a dozen times in the morning and got the error every time, so I just left the launcher there and went to work. Eight hours later, I come home to find it had “fixed” itself and could be run. The next time I tried to run it, got the errors again.
At the lower left of the launcher, it says “Can’t download”. The “Repair” button at the top can’t be selected because it is not active.
Suppose it might help if you posted some of the most recent log files from the \Star Conflict.launcher_log folder.
But I just wanted to point out that if you have recurring file corruption on your system then you might be looking at the harddrive failure shortly. Might also be another hardware issue.
Indeed, upload the log files in which the incidents took place since you say you have already deleted and re-installed the program. Might also want to try to run a defrag program on your harddrive to see if the game might be being installed into corrupt sectors of your hard drive.
Indeed, upload the log files in which the incidents took place since you say you have already deleted and re-installed the program. Might also want to try to run a defrag program on your harddrive to see if the game might be being installed into corrupt sectors of your hard drive.
I’ll look for the logs but the drive is pretty new and an SSD so there is no defragging.
Well, good news: No need. I completely removed the game again and downloaded the bit torrent. I put it in the “Program Files” folder because I read a thread somewhere that it wasn’t good sometimes at the default “Program Files (x86)” folder. Funny, it didn’t even have to be installed. Started the EXE and game started right up.
Oh, I did scan through the logs first and noticed a whole lot of lines about the target rejecting a lot of connections from various IP’s. Not sure if that had something to do with it.