Game crashes at launch

[Jerry]

After the latest patch (8.3), I can no longer start the game on my main PC (Windows 8.1). Checking on my secondary Windows 10 machine now, if it runs there. I can copy in the error message, if needed.
In any case, please fix that very soon.

[Holyday Chris]

Hello can you please try remove the installation files of the game and then verify in Steam and check if this fixes it?

[Jerry]

Might take a little while, I am on a very limited connection speed here. Still updating the other PC. More info to come soon.

[Jerry]

Running on my secondary, checking the new patch on my main, if it helps. Will be able to tell more in 20-30 minutes.

[Jerry]

Still broken. That's not good...


Here is the detailed error description (german OS, but I think you get the important parts out of it)

Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: Firestone.exe
Anwendungsversion: 6000.0.47.53741
Anwendungszeitstempel: 67f748cc
Fehlermodulname: ommon\Firestone\UnityPlayer.dll!SetThreadDescription
Fehlermodulversion: 6.3.9600.18821
Fehlermodulzeitstempel: 59ba86db
Ausnahmecode: c0000139
Ausnahmeoffset: 00000000000ece70
Betriebsystemversion: 6.3.9600.2.0.0.768.101
Gebietsschema-ID: 1031
Zusatzinformation 1: ac05
Zusatzinformation 2: ac0507478d1c5bd693cfc4fe3987e900
Zusatzinformation 3: ac05
Zusatzinformation 4: ac0507478d1c5bd693cfc4fe3987e900

[Jerry]

P.S.: Judging by the file adress, it might be an issue with unity. Did you update it to a new version, that may have compatibility issues? If so, can you downgrade it again?

[chaoslordsokar]

My issue seems connected to yours maybe even worse as I am not even getting a crash error. After hitting the Play button in Steam it changes to Launching as if the the game is starting, then just switches back to the Play button, not even a hint of the game doing anything at all. The only time I've seen a similar issue is with an old game called Rise Of Nations, that I used to play. Never found a fix for that though.
Yes I have uninstalled the game then restarted windows, reinstalled the game and verified it, still the same, no game start at all.

[Jerry]

I've had a similar thing happen in a different game (Idle Slayer) earlier this year, and that one was caused by a Unity update being incompatible with Windows versions older than 10. That's why I suspect it.

Just in case, if I wanted to switch onto a browser based version, how would I link my existing account?

[Raorkon]

Same issue here (Win 10). The small launching window pops up, then disappears and thats it. Both with shortcut on desktop and play button in Steam.

[Exhorder]

Same here, started happening today. I hope it's not because the game became W10+ only.

[sab]

javascript:Forum_ReplyToPost( '595148876446480457', '603030272975309129' );
+1

Win7-64SP1
Removing then checking game files and full reinstalling the game on new disk didn't help.

[Dandey]

A bit curious, on what update of windows 10 are the people with the issue? Maybe it's an older one as well and that's why it's not working. You can see it in winver, I am on 22H2 (OS build 19045.5737) and for me the game works. This might also help the devs to figure the root cause faster.

[fantasydragon]

Same here, Windows 7. I have a laptop with Windows 11 I can use, but I have an old desktop that I prefer to use sometimes, and I have a bunch of old clickers on here. All of them work except for Firestone now.

Also, I'm not getting any error messages or anything. I click start, it syncs cloud data, says running, then just stops. Nothing pops up at all.

[Jerry]

Folks, I am honestly happy to see, that I am not the only player, who is still running on an older system and therefor affected. Would have been awkward to be the single voice.

[jmojack]

I have MacOS 10.15, Firestone won't run on it. I have the message "Steam will stop running on MacOS 10.15 in 0 days." It's been displaying that fora few months.

[jmojack]

Application Specific Information:
application requires at least OS X version 11.0.0 (11.0), but is being run on 10.15.7 ( 10.15.7/19H2026), and so is exiting.
abort() called