D-pad Freezes Game

General help and technical troubleshooting. Ask for help here if you can't find an answer in the FAQ.
Post Reply
BDDG
Posts: 5
Joined: Fri Jul 10, 2015 6:20 pm

D-pad Freezes Game

Post by BDDG » Tue Nov 28, 2017 11:45 pm

Please Help. I've done something wrong, and I've done it twice.



Computer:

i7-4720HQ @ 2.60Ghz

16 GB Mem

Windows 8.1 64bit



Mod Manager:

Fallout Mod Manager 0.14.13



Fallout 3:

Games for Windows Live, Game of the year edition.  2xDVD's



A problem:

It will occasionally freeze(crash) at random points. I've played Fallout before, no big deal.



The Problem:

Later in the game when I change a gun or armor with the D-pad the game freezes(crashes).  It makes no difference if I go back and load a different save game, or whether I'm in FO3 or NV.  When this starts the game is unplayable from then on.



What I've already tried:

The first time I ran into this problem I loaded a couple of different save games. Then I went to different palaces on the map. No good. Turned off each mod one at a time. No good.  Uninstalled all the mods. No good.  I then uninstalled or deleted everything.  Reinstalled everything and then followed the performance guide to the letter "I hope".  Loaded old saves, went to different places on the map, turned off all of the mods, and a new one I found online.  Open the Pipboy drop everything that is hotkeyed to the D-pad. Close the Pipboy. Open it again. All no good.



If anyone has any idea as to what I should try next, I would greatly appreciate your input. Also, I've never posted anything to a forum before in my life, so if I mess up...Sorry.



Thanks,

B


You do not have the required permissions to view the files attached to this post.

User avatar
jlf65
Posts: 849
Joined: Wed Aug 10, 2016 9:10 pm

If you run a mod that changes

Post by jlf65 » Wed Nov 29, 2017 12:20 am

If you run a mod that changes the key inputs (sometimes on the fly, like flying/driving mods), the changes are in the INI file. If you get a crash when the key settings in the ini file are set one way, it stays forever... or until you restore the ini file settings for the key mapping.


 



BDDG
Posts: 5
Joined: Fri Jul 10, 2015 6:20 pm

jlf65

Post by BDDG » Wed Nov 29, 2017 4:40 pm

jlf65



Thank you for replying to my call for help.  



I have checked The values in the Controls section of FalloutPerfs.ini against the backup I made before making the changes called for in the Performance Guide.  All of the values seem to be the same, except for the values and lines changed or added in the Performance Guide.  I also checked Fallout.ini, and Fallout_default.ini against backups I made.  There seems to be no changes except those called for in the guide.  It is always posable that I made an error of course.



Could you please tell me if I have checked the right files in the correct way? I'm not certain that I've done the right thing.



Thanks again for your help.



B


You do not have the required permissions to view the files attached to this post.

User avatar
jlf65
Posts: 849
Joined: Wed Aug 10, 2016 9:10 pm

That seems okay. About the

Post by jlf65 » Wed Nov 29, 2017 9:48 pm

That seems okay. About the only other thing I can think of is maybe JIP - I've noticed many mods that say you need JIP to use a pad with the mod, so clearly it has some kind of influence over that. Try reseting the JIP ini file and see what happens. Other than that, no clue. You'll have to start disabling mods to see which is the actual source of the problem.


From the jip page... you might check this file:


Extra features:




  • FalloutCustom.ini may now be created in the game's user folder (%USERPROFILE%\Documents\My Games\FalloutNV). Setting entries included in this file will overwrite the values defined in either Fallout.ini or FalloutPrefs.ini. This allows modifying the game's configuration files without actually editing them. This also ensures any INI tweaks will persist and will not be reset/discarded by a mod organizer or the default launcher.



Mystical Panda
Posts: 750
Joined: Wed Mar 30, 2016 2:02 pm

One thing you might want to

Post by Mystical Panda » Thu Nov 30, 2017 6:32 am

One thing you might want to consider if you haven't already is to install NVAC (NVSE is also required). When you freeze or crash check the nvac.log and see if your getting a bunch of 'hits'- enough of these and the game eventually crashes. These could be indicative of 'bad assets', load order problems, or bad data somewhere in the chain of things; the authors page on the Nexus shows the 'hit' codes and what they represent.



BDDG
Posts: 5
Joined: Fri Jul 10, 2015 6:20 pm

Thanks to both of you for

Post by BDDG » Fri Dec 01, 2017 5:01 pm

Thanks to both of you for trying to help me with this problem.  I apologize for my delay in getting back to both of you.  I had a tough day yesterday.


I tried to troubleshoot last night with the advice offered.  I had no idea that the NVAC log gave you information on the crash.  I ran three tests from different save points to compare the log files of each crash.  At first I didn’t think they were related, but after looking closer, I think now that there is a relationship.  I just have to figure out what the addresses point to.  I’ve only found one, so far, and that points to a Microsoft “C” exception (only one occurrence).  I will look for the rest of the address this weekend.  Is it true that you can put these addresses in to FNVEdit and it will tell you where the problem is?


I had been thinking of uninstalling everything and starting over again, but since I’ve done that twice I feel like I should really try to figure out what the problem is first.  It’s confusing.  The first time through I only had about 6 mods, this time I have twelve.  I’m wondering if I haven’t made a mistake in the Performance Guide part of the equation, or maybe the load order (just guessing).  Oh, it’s not just the D-pad.  It crashed with the back button too.


Again, thanks to both of you for your help.


B



User avatar
jlf65
Posts: 849
Joined: Wed Aug 10, 2016 9:10 pm

I've managed 137 plugins in

Post by jlf65 » Fri Dec 01, 2017 5:41 pm

I've managed 137 plugins in TTW before having problems. :)


You can't enter the address into FNVEdit - that takes IDs, not addresses. You really ought to disable all mods but the base game, then work back to what's causing the issue. Even disable those extra TTW mods.



BDDG
Posts: 5
Joined: Fri Jul 10, 2015 6:20 pm

jlf65

Post by BDDG » Fri Dec 01, 2017 7:28 pm

jlf65


I will do exactly that.  The last time I didn't disable the extra TTW mods.  I should have, thanks.



BDDG
Posts: 5
Joined: Fri Jul 10, 2015 6:20 pm

Jlf65

Post by BDDG » Tue Dec 05, 2017 7:37 pm

Jlf65


I turned off all my mod’s, went back 15 saves, and went a different way to Vault 34.  That seems to have undone the problem I was having.  I turned my mod’s back on one at a time, not doing what I had before, and I didn’t get the crash on any of the plays this time.  I still haven’t figured out exactly what caused the crash. If I get time I’m going to try and get closer to the problem. I’ll bet it will come back at some point if I don’t get it fixed.  I just have to stop playing first.  Thanks for all your help.



User avatar
jlf65
Posts: 849
Joined: Wed Aug 10, 2016 9:10 pm

Sometimes the mods just

Post by jlf65 » Tue Dec 05, 2017 9:57 pm

Sometimes the mods just combine in a certain way with what you do in game to create a 'perfect storm' of bugs. Some of these things, there's nothing you can do but NOT do whatever it was that caused the issue. Modern games are pretty complex, and Beth games are REALLY complicated with the way the game engine was cobbled together from various pieces of code.


 



Post Reply