Crash on all lock-pick attempts

Post by **ibanix** » Tue Jun 03, 2014 7:12 am

Hello!

I am a return user to TTW, been away for a while. I have v2.4 installed on fresh copies of FO3 and FNV. TTW installer worked w/o any problems.

Successfully played through the leaving Vault 101 quest. After exit from the Vault, *any* lockpick attempt - doors, safes, etc. - all cause a CTD right after the lockpick interface loads. I am able to see the lock and screwdriver, then it crashes. Tested against locks in Springvale and Megaton.

Details:

Windows 7, 4GB DDR2, Q8300

Load order:

[X] FalloutNV.esm

[X] DeadMoney.esm

[X] HonestHearts.esm

[X] OldWorldBlues.esm

[X] LonesomeRoad.esm

[X] GunRunnersArsenal.esm

[ ] TribalPack.esm

[ ] MercenaryPack.esm

[ ] CaravanPack.esm

[ ] ClassicPack.esm

[X] Fallout3.esm

[X] Anchorage.esm

[X] ThePitt.esm

[X] BrokenSteel.esm

[X] PointLookout.esm

[X] Zeta.esm

[X] TaleOfTwoWastelands.esm

My TTW InstallLog.txt:

[6/1/2014 10:47:42 PM] System Architecture: Intel64 Family 6 Model 23 Stepping 10

[6/1/2014 10:47:42 PM] 64-bit architecture found.

[6/1/2014 10:47:42 PM] Building checksum dictionary using E:\Fallout_TTW_INSTALLER\resources\\TTW Data\TTW Patches\TTW_Checksums.txt

[6/1/2014 10:47:42 PM] TaleOfTwoWastelands.bsa = BA4906CF3AB218545E76842D0A1BD3C1

[6/1/2014 10:47:42 PM] Anchorage.esm = 209639897C5AD1361E75485E8D444ECF

[6/1/2014 10:47:42 PM] BrokenSteel.esm = AFC9CA58AF0FB206157D888BAE324B9F

[6/1/2014 10:47:42 PM] Fallout3.esm = 37C5DA1ED64F003F88B3D9418344BCE7

[6/1/2014 10:47:42 PM] PointLookout.esm = A65A464169D6570AF606C270D6825C77

[6/1/2014 10:47:42 PM] ThePitt.esm = A3B7CE448DA21ED51AD665D44A326E75

[6/1/2014 10:47:42 PM] Zeta.esm = AA1C1917F75093A3348F0086C3AE57CA

[6/1/2014 10:47:42 PM] Done.

[6/1/2014 10:47:42 PM] Looking for Fallout3.exe

[6/1/2014 10:47:42 PM] Found.

[6/1/2014 10:47:42 PM] Looking for FalloutNV.exe

[6/1/2014 10:47:42 PM] Found.

[6/1/2014 10:47:42 PM] Looking for Tale of Two Wastelands

[6/1/2014 10:47:42 PM] Default path found.

Also using FNV4GB.exe. Problem occurs with or without use of FNV4GB.exe.

No other relevant mods or changes.

Thanks,

ibanix

Post by **Risewild** » Tue Jun 03, 2014 8:09 am

No other relevant mods or changes.

Do you mean it is totally vanilla TTW or you have other mods but you think they are not relevant to the problem?

Because that problem is definitely not a TTW problem, never happened to anyone I know, and it doesn't happen in my TTW 2.4 extensive play testing I did on it.

So my opinion is that it is a mod problem (which might just be some mod leftovers or something), or for some reason your game got corrupt somehow... I really have no idea why or how that could be happening at all with just TTW .

Post by **plumjuice** » Tue Jun 03, 2014 8:44 am

Attach your install log and load order as .txt files.

You have broken something. TTW did not break it. If you want people to help you actually need to give us what we want/need in order to help you.

Read the link in my sig.

Post by **ibanix** » Tue Jun 03, 2014 6:59 pm

Oy, way to be nit-picking about the word "relevant"; sorry I included it when I was attempting clarity. There were no other mods.

I re-ran the TTW installer and then manually moved all the files to my TTW install, and the problem resolved itself. I'm going to assume there was a problem with a bsa or esm somewhere.

Post by **plumjuice** » Wed Jun 04, 2014 1:21 am

FWIW your attempt at adding clarity did the exact opposite, and Rise was perfectly justified in asking if you had ANY mods, since you had left that possibility very much open.

If you have the spare time, you should hunt through the tech support forum and see exactly how many times people have posted "mai gaem no wurk!!1!one!! you broke it fuck you fix it plz" and then turn out to have been using mods that are either proper incompatibilities with ttw (mmue and nvec complete) or mods that conflict /with each other/. It gets old pretty quick.

Glad to hear everything is working now though, enjoy.