I updated one of my Factorio instances to 1.1.103 today and after the update, (64-bit) Windows 10 is telling me that the executable is 16-bit. I attached a screenshot of the error message. There's nothing relevant in the Factorio log, but the sanitized version is attached, nonetheless.
Some more details:
The resulting factorio.exe is 5,108,678 bytes in length, and fileutils's file(1) says it's a "VCDIFF binary diff."
Some more, more details:
This is reproduceable by installing 1.1.102 from zip file and applying the 1.1.103 update.
[1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
[1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
- Attachments
-
- sanitized-pre-update-factorio.log
- (6.96 KiB) Downloaded 35 times
-
- 16 whole bits.png (8.34 KiB) Viewed 1864 times
-
- Filter Inserter
- Posts: 299
- Joined: Sun Jun 12, 2016 11:29 pm
- Contact:
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
The error here happens when Factorio automatically runs the "updated" program. On trying to run it manually, I get a blue window with "This app can't run on your PC".
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
It looks like I'm gonna have to get my legacy playstation running, thats 16 bit, no? ohh, or a saturn! (I wonder how Factorio would look with no transparencies?)
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
I would like to apologize for the continued problems with the update packages. The 1.1.103 update package has been pulled until it is fixed to cover the cases of updating from every release. In case you were affected by this problem I'm sorry but you will have to download a new full release of 1.1.103.
EDIT: I made and uploaded a new 1.1.102-1.1.103 Windows update package that, in my testing, appears to work even with a corrupted version of 1.1.102. But if you have already used the earlier update package and gotten this error, I'm afraid you will have to download a new full release of Factorio.
EDIT: I made and uploaded a new 1.1.102-1.1.103 Windows update package that, in my testing, appears to work even with a corrupted version of 1.1.102. But if you have already used the earlier update package and gotten this error, I'm afraid you will have to download a new full release of Factorio.
ovo
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
Quick response, and on a Friday evening, too! The fix was pretty straightforward (unzip the 1.1.103 full installer somewhere and copy the directories therein to the damaged 1.1.102 install).Sanqui wrote: ↑Fri Jan 19, 2024 8:04 pmI would like to apologize for the continued problems with the update packages. The 1.1.103 update package has been pulled until it is fixed to cover the cases of updating from every release. In case you were affected by this problem I'm sorry but you will have to download a new full release of 1.1.103.
EDIT: I made and uploaded a new 1.1.102-1.1.103 Windows update package that, in my testing, appears to work even with a corrupted version of 1.1.102. But if you have already used the earlier update package and gotten this error, I'm afraid you will have to download a new full release of Factorio.
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
Wonder if the game actually works with 16 bit wordsize. How did it even compile to that actually?
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
That's not what happened here. What happened is that an erroneous update package replaced the executable with a diff file, which the system doesn't recognize and cannot run. It only calls it a 16-bit application because it's in an unexpected format.
ovo
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
Oh so it's like git diff on some binary files is that it?
Re: [1.1.103] Updating from 1.1.102 (build 62103) results in a 16-bit executable?
Yes. Instead of downloading the 1GB+ whole game during patching, the game instead downloads the differences ("diff") between the old version and the new version -- in binary format -- and applies those differences locally; the diff is orders of magnitude smaller than the full game. This, of course, saves on bandwidth charges for Wube's hosting and saves time for players downloading (especially for players on slower network connections).guy-732 wrote: ↑Sat Jan 20, 2024 10:32 amOh so it's like git diff on some binary files is that it?