Fish Butchery Bug in 0.D

I attempted to butcher a smallmouth bass in the latest build (8621) only for my game to crash. It’s not like the crash that I used to get sometimes before 0.D, though.

I figured it might be because I was using Aftershock, Bright Nights, Ascension and Cataclysm++ all at once (a bad decision I know :p) but it seemed a bit weird that that would result in a crash from a smallmouth bass of all things.

It says I don’t have a butchery tool in the image, but I spawned in a steak knife after that as I was testing if it would crash again (I had taken the fish back to base before and it had crashed then).

Crash Log

CRASH LOG FILE: config/crash.log
VERSION: 0.D-572-gc62f18a
TYPE: Signal
MESSAGE: SIGFPE: Arithmetical error
STACK TRACE:
@0x554FB5[cataclysm-tiles.exe+0x154FB5]
@0x555B62[cataclysm-tiles.exe+0x155B62]
SMPEG_error+0x4B0B1@0xE1BEFD[cataclysm-tiles.exe+0xA1BEFD]
_C_specific_handler+0x98@0x7FF8F1D07C58[msvcrt.dll+0x27C58]
_chkstk+0x11D@0x7FF8F3EFF7DD[ntdll.dll+0x9F7DD]
RtlWalkFrameChain+0x13F6@0x7FF8F3E6D856[ntdll.dll+0xD856]
KiUserExceptionDispatcher+0x2E@0x7FF8F3EFE70E[ntdll.dll+0x9E70E]
@0x41D4AF[cataclysm-tiles.exe+0x1D4AF]
@0x42365E[cataclysm-tiles.exe+0x2365E]
@0x432D0C[cataclysm-tiles.exe+0x32D0C]
@0xB81040[cataclysm-tiles.exe+0x781040]
@0x646F94[cataclysm-tiles.exe+0x246F94]
@0x685E6C[cataclysm-tiles.exe+0x285E6C]
IMG_LoadWEBP_RW+0x4D3219@0x13E0F09[cataclysm-tiles.exe+0xFE0F09]
@0x4013ED[cataclysm-tiles.exe+0x13ED]
@0x4014FB[cataclysm-tiles.exe+0x14FB]
BaseThreadInitThunk+0x14@0x7FF8F36C3DC4[KERNEL32.DLL+0x13DC4]
RtlUserThreadStart+0x21@0x7FF8F3ED3691[ntdll.dll+0x73691]

Does it crash when you butcher anything, or just the bass?

Just the bass. I haven’t found anything else it does this with yet. I can test it out if it helps.

This issue may be related

First thing try to reproduce the issue without mods, then enable mods one by one and find out which one causes the issue.

Yeah @anothersimulacrum I took out PK’s and I no longer get the bug. @dissociativity tagging you here as this looks like it’s related to an existing issue.

That bug was already fixed in the latest PK days ago mate

I downloaded the latest version today and the bug was still present. I’ll redownload and try again tomorrow just in case, though.


This should have fixed it