(I'm making this issue so I don't forget about it)
When Localization Fixes edited mituru.bf in field\pack\dng_init.pac multiple people reported random crashes when loading Tartarus, either by actually entering it or finishing a battle (discord thread). The crash reportedly would only happen after an hour or so of gameplay so is hard to replicate.
The mod was editing a single message using BF Emulator however I encountered the crash once using a whole BF file so I believe this is unrelated to BF Emulator.
Reference msg file:
[msg MSG0810_0820_MITURU_DUNG [Mitsuru]]
[s][bup 4 204 0 0]"Strega," hm...[n][w][e]
[s]I didn't know there were other [n]Persona-users out there...[n][w][e]
The error occurs as P3P tries to access some memory it shouldn't when loading the file as can be seen in a crashdump. I'm unsure what the actual cause of the problem is however I suspect it's some minor problem with PAK Emulator, perhaps some small part of the format has been misunderstood.
I don't have the time or motivation to fix this since the files are fairly insignificant, however, hopefully I will properly investigate this when PAK Emulator is eventually ported to Rust.
This has now also been reported on Reloaded's page, fun.
Auto heal causes the same problem as it also edits dng_init.pac, I don't think I'll be able to just leave this problem unsolved :(
(I'm making this issue so I don't forget about it)
When Localization Fixes edited
mituru.bf
infield\pack\dng_init.pac
multiple people reported random crashes when loading Tartarus, either by actually entering it or finishing a battle (discord thread). The crash reportedly would only happen after an hour or so of gameplay so is hard to replicate.The mod was editing a single message using BF Emulator however I encountered the crash once using a whole BF file so I believe this is unrelated to BF Emulator.
Reference msg file:
The error occurs as P3P tries to access some memory it shouldn't when loading the file as can be seen in a crashdump. I'm unsure what the actual cause of the problem is however I suspect it's some minor problem with PAK Emulator, perhaps some small part of the format has been misunderstood.
I don't have the time or motivation to fix this since the files are fairly insignificant, however, hopefully I will properly investigate this when PAK Emulator is eventually ported to Rust.