Locked
19 posts • Page 1 of 1
So after updating to 1.2.2.1, I am now CTD'ing every time I attempt to access my secure chest.

It was not doing this on 1.2.2.0, so I was wondering if there was a list of *exactly* what records were changed in 1.2.2.1. While I am playing with a few mods (nothing too major), I haven't had any issues until now.

Also, is there a downgrade procedure so I can go back to 1.2.2.0? I'm at level 63 and about (I think) half way-ish through the story, so I would *really* prefer not to restart and lose everything.

As an addendum: Does anyone know how to get access to the contents of the Secure Chest via the console? I'm likely going to need to do that in order to fix this if I can't downgrade.
welcome to the forum :)

what mods do you have installed?
best would be deactivating them one after another:/
Changelog 1.2.2.1:

General:
Races and some books will be displayed properly.
is the only thing stated in the changelog. (maybe some armor? skeleton? bodymod?)

if that doesn't help, you might want to open a ticket in the Bugtracker
(no need to register)

if the crash is indeed only tied to the patch (regardless of mods)
there might be a rollback soon, so maybe stop playing for a while.

there are console commands for opening containers in general,
but I have absolutely no idea how they work with these chests :?:
would not recommend.

don't know about downgrading, sorry :(
The fact that only races and some books were updated and my game started to crash on me was what surprised me the most. As a means of first response I deactivated ALL my mods and tried it again, but the game still crashed.

Still though, here's a list: As far as working with inventories goes, I don't have much of a problem with it, I just can't seem to find the right RefID of the Secure Chest. The two that are listed via the help command are cited as "invalid" by the game, and when I click on a Secure Chest directly it's inventory is just some misc clutter like nails and spare parts. I've been doing other things for the day so far, but when I get back into troubleshooting this I guess I'll fire up the Creation Kit and try to hunt down the script/container from there.
Could you upload a savegame?
found in ..\Documents\My Games\Skyrim\Saves.
We'll need the skse and the ess of a manual (no quick- or auto-) save.
Pack them to a rar or zip archive and attach them to a post here :)
12.08.2017 22:28rux616 wrote:
So after updating to 1.2.2.1, I am now CTD'ing every time I attempt to access my secure chest.
I'm also getting CtD since update every time I loot chests and bodies or open character inventory, my characters wrists are also invisible since update!
Running completely vanilla skyrim and enderal.
13.08.2017 12:19MarkusParkus wrote:
I'm also getting CtD since update every time I loot chests and bodies or open character inventory, my characters wrists are also invisible since update!
Running completely vanilla skyrim and enderal.
This is your report, right? Did you encounter the crash with patch 1.2.0.7 or 1.2.2.0 before patching to 1.2.2.1?
I can reproduce your crash, but only with your save only on the english version.
You've cheated quite a lot, which cheats exactly?

I fixed the forearm issue (don't know why it popped up, nothing was changed on the model).

@rux616
Please attach your save.

Edit: And a question to both of you: Are all saves affected or only new ones? What happens when you start a new game?
stuemper, thanks for taking some time to look into this. I'm not sure if your first question was addressed to me, but I'll answer anyway: I was able to run fine on 1.2.2.0, and only started crashing on 1.2.2.1.

I think this is related to a specific item, because I have an older save from when I was level 53 where I can still access the secure chest, and then a few saves later I am unable to. I feel this is reinforced by the fact that the crashing doesn't happen on a new game. I am attaching both the good and bad save, and my most recent one (which is also bad).
  • Save 614 - Last convenient good save I have.
  • Save 618 - First convenient bad save I have.
  • Save 645 - Most recent (bad) save I have.
Edit: Also, if you need the mods to test just let me know and I'll upload the customized ones as needed.
Attachments
Saves.zip
(7.9 MiB) Downloaded 230 times
13.08.2017 14:08stuemper wrote:

This is your report, right? Did you encounter the crash with patch 1.2.0.7 or 1.2.2.0 before patching to 1.2.2.1?
I can reproduce your crash, but only with your save only on the english version.
You've cheated quite a lot, which cheats exactly?

I fixed the forearm issue (don't know why it popped up, nothing was changed on the model).

Edit: And a question to both of you: Are all saves affected or only new ones? What happens when you start a new game?
Hi stuemper, massive thanks for the reply!
The crash and forearm issue is only since 1.2.2.1, I think the forearm issue was caused by the 'order robes' I got through console commands, if I 'unequip all' through console the forearms return, but I still get the crash when I try open inventory or loot.

I have a save from around 6hours of gameplay ago that isn't affected by the crashes. Also starting a new game is bug free.
Sorry for cheating! its my second play and wanted to rush the early game.
I've used no clipping, god mode, additem, unlock, time advance, killall.
@stuemper Are there any details available that describe exactly which records were touched by 1.2.2.1? If there are then I can help and start hunting around for anything that looks suspect and test it.

Barring that, I ask again if there is any way for me to roll back to 1.2.2.0.
No records were touched with 1.1.2.1, it was only a string fix with a new update.esm. I assume that some mods or/and items added via the console probably caused this problem for you like it happened to @MarkusParkus. Have you recently added mods and/or items?
I would suggest to go back to a previous save and replay it. Does the crashes occur again? Between save 614 and 618 you've placed something in the secure chest which causes it to crash.
That's really weird as my mods have been stable for a while. (Since before the 1.2.2.0 update.)

Thankfully the mods I use don't add very many items to the game so testing shouldn't be a gargantuan task. I've got things to do tonight when I get home, but I will be able to work on this later in the evening.

I'll keep you posted.
Ok, I figured it out. For some reason the item "Staff of the Burning Call" (FormID: 00029B78, EditorID: _00E_StaffOfTheBurningCall) crashes my game now.

No clue why as the mods I have installed don't touch anything dealing with this weapon.

For others that end up dealing with this type of thing, I'm going to describe how I fixed it.

In my case because I was dealing with the Secure Storage chest, I needed a way to record the ridiculous amounts of items I had stored there. Enter: ConSkrybe. It's an amazing little SKSE plugin that records your console input (and output) to a log file (conveniently named "ConSkrybe.log") in the main Skyrim directory.

First, I dumped the inventory list of the secure storage chest (refid 5c132) to the console using the following commands:
prid 5c132
showinventory
Next I made a small python script to process the output of the ConSkrybe log file and turn it into Skyrim batch script to remove items:
[+] Python script
import re

# regex strings used for matching
regex_quantity = '^\d+'
regex_itemid = '[0-9A-F]{8}'

# declare variables as lists
linecontent = []
quantity = []
itemid = []

# read the conskrybe log into the script
with open('C:\\Program Files (x86)\\Steam\\steamapps\\common\\Skyrim\\ConSkrybe.log') as file:
    linecontent = file.readlines()

# script all whitespace off either end of each line
linecontent = [line.strip() for line in linecontent]

# check if an individual line should be parsed further and added to the itemid and quantity lists
for line in linecontent:
    if re.search(regex_quantity, line) is None:
        # if the line does not start with a number, move on to the next line
        continue
    else:
        # line starts with a number, so pull out said number (quantity) and the item id
        quantity.append(re.search(regex_quantity, line).group(0))
        itemid.append(re.search(regex_itemid, line).group(0))

# write the itemids and quantities to a file
with open('C:\\Program Files (x86)\\Steam\\steamapps\\common\\Skyrim\\removeitem.skybat', 'w') as file:
    for id in range(0, len(itemid)):
        file.write('removeitem ' + itemid[id] + ' ' + quantity[id] + '\n')
Now, pick half of the list, delete it from the removeitem.skybat file, and save the file, but do not close the file because you will be making use of the undo feature. If your text editor is being weird about it, get something like Notepad++. The theory here is that you use the script to remove half of the items in the chest each time, resulting in a smaller number of crashes (and subsequent restarts) until you figure out which item is being vexing. Let's say you have 16 items in the chest. You would edit the removeitem.skybat file and delete the second half of the file, with the result that when you run the skybat file, it will only remove the first half of the chest contents. If you open up the chest and still crash, you know that none of the 8 items you just removed via the skybat file is the culprit. At this point, you would undo the changes to the skybat file, and select 4 of the other 8 items to removed, and so on, until you find the item.

Now, when you go ingame, do the following:
  • prid 5c132
    to select the storage chest.
  • bat removeitem.skybat
    to run the skybat file and remove however many items are called for.
  • Open the chest to see if you crash.
  • If you crash, the item is still in the chest, so alter the removeitem.skybat file using the method above and try again.
  • If you don't crash, alter the removeitem.skybat to remove different items, load up the previous save, and try again.
It's a bit tedious, but it will ultimately lead you to the offending item.
I hope it's ok to post here when it's marked 'solved' but this is happening to me as well. Game playing fine right up until I installed 1.2.2.1, now it crashes every time I try to open my inventory. I've tried back several saves and it keeps happening. I only had one mod installed which was waitnoheal and I've disabled that which still doesn't help. I do keep things in the secure chest but mainly I keep things in my inventory. I can't see any way to roll back the upgrade so I don't know what to do now. I don't want to start over as I have many hours invested. I'm not familiar with the console so the 'solution' seems very complicated to me.
This is not really solved, at least it wasn't marked as solved by us. This particular issue was present in early development and disappeared at some point. Now here it is again. We work on a solution for the next patch.
@stuemper would you like me to unmark this as solved for now?

@Sharelf the same method that I used in my previous post should work for the player inventory as well, you would just need to target the commands at "player" instead and you wouldn't use the "prid ..." command at all. To target the other commands at the player's inventory you just need to prefix the commands with "player.", e.g. "player.showinventory".

Hope this helps.
Thanks, but not being familiar with console commands it seemed extremely complicated to me, and long. I'm hoping they will soon release a new patch which will fix the issue. In the meantime I can't play so having slight withdrawal pangs!
As someone with the same problem (CtD after updating to patch 1.2.2.1 when opening an inventory containing the Staff of the Burning Call), I have figured out how to fix it if you know the itemID of the conflicting item.

What you do is that you launch the save file and open console. Then you type the following,

"prid 5c132" (For targeting the secure chest inventory).

"removeitem 29b78 1" (For removing the conflicting item, Staff of the Burning Call)

Done.


If the item is in your player inventory, you simply do as before but in the console you type

"player.removeitem 29b78 1"

Done.

I hope this helps as much as it did for me, as the bat file solution didn't quite work for me.
(I probably did something wrong as I am new to such stuff).
The latest patch has fixed this issue for me - yay! Thanks
Nice, glad it works now. :)
Locked
19 posts • Page 1 of 1