Skip to content

Weird Fatal Crash When Picking Up a Specific Book or Staff

BalkothBalkoth Member Posts: 165
edited June 13 in Builders - Scripting
Upon trying to pick up a generic book from the ground or a container, the game fatal crashes.

Upon trying to spawn in a creature with a specific custom staff (but not creatures with other custom staffs) or trying to pick up that staff, the game fatal crashes.

There is nothing in the crash report file related to that -- like if I boot up the game at 12:00 noon, do nothing for 30 minutes, and then pick up the staff or book at 12:30...the last line in the crash report is from 12:01 or something. The minidump might have more info but I can't easily read that.

Here's a video showing the situation:

https://www.youtube.com/watch?v=O8rsD8Qfp1E

Anyone have any idea these two items specifically may be crashing?

The resrefs/blueprints in question are fmxylemstaff and fmxylembook, but fmxylemrobe causes no issues.
Post edited by Balkoth on

Comments

  • MelkiorMelkior Member Posts: 263
    I'm not sure exactly where you are in the game. Is this part of one of the campaigns? Is it a custom module?
    Even if it's something from a HAK which is absent, it still shouldn't crash the game on pick-up but should instead just show an object of the appropriate size with a red cross on a black background.
    Off-hand, this sounds like corrupted files in your installation of the game.
  • BalkothBalkoth Member Posts: 165
    It's a custom module in development.

    I verified files and still crashing.

    It crashes in both the hak and hakless version of the module.

    Last night I decided to try making a copy of the staff/book and call them "fmnocrashstaff" and "fmnocrashbook" respectively and updated all references in creature blueprints/containers/scripts/etc to the copies...and it no longer crashes.

    I still have no idea why.
  • MelkiorMelkior Member Posts: 263
    I don't know either. I have only guesses based on knowledge.
    Maybe the originals clashed with either the item number or the name-space of something else? That's my best guess.
  • BalkothBalkoth Member Posts: 165
    Turns out the issue was a script to take an item during a conversation had the same blueprint of the item itself. Which meant it tried to trigger tag based scripting when the item was picked up. The script had an ActionPauseConversation, but trying to call that function when a conversation didn't exist crashed the game.
  • ForSeriousForSerious Member Posts: 536
    I'm glad you were able to find it! I figured it was a script when you picked up the items, but I also had no idea what would cause the total crash.
Sign In or Register to comment.