MagicBeanDev/Longshot

Watch

Fork 98

Install: Windows build fails during translation with corrupted chunks or TypeError #765

New issue

Open

opened 2026-11-15 10:50:22 +00:00 by BeanIssues · 4 comments

BeanIssues commented

2026-11-15 10:50:22 +00:00

Collaborator

Reported by Dσтт. Nєυтяσи on Discord

What they used

Longshot Launcher 1.0.0.

Version and channel

The reporter tried build nightly-145-543846eb (nightly) and v3.0.0-rc.3 (release candidate); both failed. A second user independently reported failure on v3.0.0-rc.3. The first reporter says it also happened on their first-ever build, so this was not limited to later builds or an overlap between builds.

Step where it stopped and error

During translation (lift.py), the first report stopped with ValueError: invalid literal for int() with base 16: '\x00\x00\x00... while reading chunk data. The second stopped with TypeError: 'cell' object is not callable in a64_lift.mark_groups; its log also reports an emit worker process stopped or could not start.

System

Both reports: Windows 10.0.26300. First: 31 GB RAM, 12 threads. Second: 32 GB RAM, 32 threads. The first reporter additionally reports an RTX 4060, Ryzen 5 9600X, and more than 1 TB free on an SSD.

Steps

Start a build from the Launcher; it fails during translation. The first reporter tried both nightly and release candidate builds and says the problem occurred on their first-ever build. Another user reproduced a translation failure on the release candidate.

Logs

First full build log attached as message.txt from Discord.
Second full build log attached as message.txt from Discord.

Missing

GPU driver version, and launcher/builder logs if available.

Reported by [Dσтт. Nєυтяσи on Discord](https://discord.com/channels/1569849200047427645/1571232928560713819/1571232928560713819) ## What they used Longshot Launcher 1.0.0. ## Version and channel The reporter tried build `nightly-145-543846eb` (nightly) and `v3.0.0-rc.3` (release candidate); both failed. A second user independently reported failure on `v3.0.0-rc.3`. The first reporter says it also happened on their first-ever build, so this was not limited to later builds or an overlap between builds. ## Step where it stopped and error During translation (`lift.py`), the first report stopped with `ValueError: invalid literal for int() with base 16: '\x00\x00\x00...` while reading chunk data. The second stopped with `TypeError: 'cell' object is not callable` in `a64_lift.mark_groups`; its log also reports an emit worker process stopped or could not start. ## System Both reports: Windows 10.0.26300. First: 31 GB RAM, 12 threads. Second: 32 GB RAM, 32 threads. The first reporter additionally reports an RTX 4060, Ryzen 5 9600X, and more than 1 TB free on an SSD. ## Steps Start a build from the Launcher; it fails during translation. The first reporter tried both nightly and release candidate builds and says the problem occurred on their first-ever build. Another user reproduced a translation failure on the release candidate. ## Logs - First full build log attached as `message.txt` from Discord. - Second full build log attached as `message.txt` from Discord. ## Missing GPU driver version, and launcher/builder logs if available.

message.txt

6.4 KiB

message.txt

8.3 KiB

BeanIssues added the

labels

2026-11-15 10:50:22 +00:00

BeanIssues commented

2026-11-15 10:50:23 +00:00

Author

Collaborator

Files from the Discord report:

Files from the Discord report: - [message.txt](https://git.magicbean.dev/attachments/77f739e3-32d1-4391-9aba-35cefdb7385c) - [message.txt](https://git.magicbean.dev/attachments/6caaeff9-846b-423c-b3a7-c1bef16877dc)

BeanIssues commented

2026-11-15 10:52:35 +00:00

Author

Collaborator

Updated with more from Dσтт. Nєυтяσи on Discord: Added the reporter's clarification that failure occurred on their first-ever build, so it was not caused by overlapping builds.

Updated with more from [Dσтт. Nєυтяσи on Discord](https://discord.com/channels/1569849200047427645/1571232928560713819/1571477875368923227): Added the reporter's clarification that failure occurred on their first-ever build, so it was not caused by overlapping builds.

BeanIssues commented

2026-11-15 10:56:18 +00:00

Author

Collaborator

Updated with more from Dσтт. Nєυтяσи on Discord: Added the first reporter's SSD free-space, RTX 4060, and Ryzen 5 9600X details; clarified that the merged concurrent-build fix may not address their first-build failure.

Updated with more from [Dσтт. Nєυтяσи on Discord](https://discord.com/channels/1569849200047427645/1571232928560713819/1571478832685518849): Added the first reporter's SSD free-space, RTX 4060, and Ryzen 5 9600X details; clarified that the merged concurrent-build fix may not address their first-build failure.

BeanIssues commented

2026-11-15 13:40:34 +00:00

Author

Collaborator

From Dσтт. Nєυтяσи on Discord:

Reporter later confirmed the build works with the latest nightly after deleting the work folder. Clearing the work folder resolved their failure; they did not specify the exact nightly version.

From [Dσтт. Nєυтяσи on Discord](https://discord.com/channels/1569849200047427645/1571232928560713819/1571232928560713819): Reporter later confirmed the build works with the latest nightly after deleting the work folder. Clearing the work folder resolved their failure; they did not specify the exact nightly version.