Page 1 of 1
[StrangePan][2.0.17] Crash with invalid strong type value: -256
Posted: Thu Nov 14, 2024 5:50 pm
by WhiteFang
The game crashed with the following error:
```
8703.191 Error Util.cpp:81: invalid strong type value: -256
```
I wasn't doing anything at all (standing around at Gleba while eating dinner)
System has issues: 121566
Re: [2.0.17] Crash with invalid strong type value: -256
Posted: Sun Nov 17, 2024 3:40 pm
by Somtuk
I've encountered the same bug (different value, same error) however I know how to reproduce my situation.
Requirements (for my crash):
Use the Explosive Termites mod (
https://mods.factorio.com/mod/Explosive%20Termites)
Steps to reproduce:
- Start a game
- Open the Factoriopedia
- Go to the "Environment" tab
- At the bottom, there are 2 clickable boxes with no icon. Click either box. The crash should occur with
- Strong Type crash.png (6.36 KiB) Viewed 865 times
Re: [2.0.17] Crash with invalid strong type value: -256
Posted: Mon Nov 18, 2024 7:53 am
by WhiteFang
Great find! Especially if it happens every time.
To clarify, I am also using mods, but not the one mentioned in the post above though.
One of the mofs I use is blueprint lab, which also adds some new icons/items specifically for the lab. They might cause a similar issue (can't test right now).
Re: [StrangePan][2.0.17] Crash with invalid strong type value: -256
Posted: Fri Dec 06, 2024 10:57 am
by StrangePan
Thanks for the report! I reproduced the issue using the Explosive Termites mod and verified the fix. This should be fixed in 2.0.25.
Re: [StrangePan][2.0.17] Crash with invalid strong type value: -256
Posted: Fri Dec 06, 2024 1:32 pm
by StrangePan
WhiteFang wrote: Thu Nov 14, 2024 5:50 pm
The game crashed with the following error:
```
8703.191 Error Util.cpp:81: invalid strong type value: -256
```
I wasn't doing anything at all (standing around at Gleba while eating dinner)
System has issues: 121566
Looking over your installed mods, I'm not convinced that your original report is the same as the one with the Explosive Termites mod. But there isn't really anything actionable in the log. 2.0.25 will improve logging around this error, but we'll need to wait until it is released to look into this further. I'll move this topic back to "pending" for now while we wait.
If you do manage to reproduce this, please let me know.