Crash After Hitting New Game

Post by **Harrug** » Sat Sep 17, 2016 1:48 am

This is my first time in dealing with TTW and this forum, so I want to make sure I do things right.

System Specs: Windows 10, Intel i7-4790k processor, 16GB RAM

I have attached the TTW Install Log and my current load order (I am using FOMM, version 0.14.11.12). Also, I have the Steam versions of Fallout 3 GOTY and Fallout NV GOTY. I believe that was all of the 'technical' information asked of in the stickied post.

Now, as the subject says, every time I hit new game after launching FNV through FOMM (with the 4GB launcher), it plays the main Fallout 3 intro, and then crashes. I have re-downloaded both my Fallout 3 and Fallout NV three times (to insure fresh installs) and proceeded with the TTW installer, of which I had zero trouble with any time. I received this error the first time, so I set up my Fallout 3 to work on Windows 10, thinking that might possibly be what was casing the error. Fallout 3 now runs fine, but I was still getting a crash after new game, so that was when I re-downloaded everything the second time. Still got an error. I then checked my drivers through NVIDIA and found there was an update, so I downloaded the update and reinstalled both games a third time. I am still recieving the error.

I have scoured the forums and the internet, watching multiple YouTube tutorials and reading online guides to see if I was missing anything. I have all of the appropriate .ini's corrected to work with TTW, and have tried a multitude of other things (I admit I don't remember everything I did). I just want to get the mod working before I download any other mods, but I am starting to run out of ideas. I don't want to re-download everything a fourth time, as that will use a lot of my internet's data, and I've used enough as it is.

Does anyone have any suggestions or advice? I greatly appreciate any and all advice/help. If you have any questions, please ask away, and I will do my best to answer them in a timely matter. I've seen a couple of playthrough videos and the mod looks like tremendous fun (as if the concept alone wasn't enough to sell me already, which it was), and I really want to try it. I appreciate any and all help. I did not want to bother people with this, but I really am at my wits end with this one. And as I mentioned, if I forgot to include any necessary helpful information, please let me know!

Post by **RoyBatty** » Sat Sep 17, 2016 2:50 am

Next nvidia driver should have a fix for this. In the meantime you can install NVAC and it will temporarily fix the problem. However none of the NPC's will have hair.

Post by **Harrug** » Sat Sep 17, 2016 4:23 am

I have updated my drivers and installed NVAC (into the Data\NVSE\Plugins folder, and not the main directory); however, I still crash. Was this the only known solution to the issue, or is it time for another reinstall...thank you for your response regardless.

Post by **jlf65** » Sat Sep 17, 2016 4:56 am

When you altered the ini files, did you look to see if the entries already exist and modify them, or did you just add them? If you just add them and the lines already exist, the last lines run will be the ones that count.

The reason I ask is where you crash sounds like the crash I got when I had the main quest id set in one ini file but not the other. It already exists in the other ini file, so I had to alter it rather than add it like in the first file.

Post by **Harrug** » Sat Sep 17, 2016 1:26 pm

I altered the pre-existing lines in the .ini files. Was I supposed to add lines, of are you asking if I added these lines instead of editing the ones in there (I just edited them). With each re-download of the games I made sure to go back and make the necessary changes to each .ini file as well.

Post by **jlf65** » Sat Sep 17, 2016 3:47 pm

You edit the existing lines if they exist, add them only if they don't. So that doesn't sound like the issue here. Just checking because crashing when you start a new game is what happened to me when I didn't have the ini files set right. I'd double check the quest id against the install instructions just to make sure you don't have a number wrong.

Post by **RoyBatty** » Sat Sep 17, 2016 4:24 pm

The new driver is *broken* as I said. Downgrade to 365.19 and your game will work again for now. The *next* driver update from nvidia will have this issue fixed according to them. It is a known issue.

Post by **Harrug** » Sat Sep 17, 2016 4:26 pm

Oh ok, I understand now. Sorry for the misunderstanding. Thank you both RoyBatty and jlf65 for the replies, I appreciate it.