gigaus Posted July 10, 2016 Share Posted July 10, 2016 Dumb question, but when the game crashes, is there some error code that you can look up? I've got a mod combo running that ends with my computer crashing at random times, most of the time not even at peak usage or when something new is loading in. I've never had to deal with mods crashing this much before, and every time I look around I can't find anything that lists off the events of what happened to narrow it down. Right now I'm chalking it up to my computer being bad with active windows and hiding it under the NV window, but I wanted to ask if there is something that spits out an error code or event log when the game crashes? Link to comment Share on other sites More sharing options...
dubiousintent Posted July 10, 2016 Share Posted July 10, 2016 Sometime there are error codes, and sometimes there aren't. Depends upon just what caused the error (not all are directly related to the game code), and if it was anticipated or not. FNV itself, doesn't. The various "script extenders" (NVSE, JIP NVSE, and Lutana NVSE) produce error logs which are found in the game root folder ("<steam install path>\SteamApps\Common\Fallout New Vegas"). Some few other mods do as well. (Just sort by file extension and all the ".log" files will be grouped together.) If you get a Windows "system" or "application" error message window, then you can use the Windows "EventViewer". Refer to the "Windows Error Messages" section of this wiki article about those. They won't tell the average player anything, but you can search on the Internet for the error code. Take a look in the wiki article "Fallout NV Mod Conflict Troubleshooting Guide" for the various issues with "CTD" in their title to see if any of those solutions can improve your situation. -Dubious- Link to comment Share on other sites More sharing options...
gigaus Posted July 11, 2016 Author Share Posted July 11, 2016 Alright good to know, though I have NVSE set up properly and it didn't produce a .log file. Even went as far as to search for it incase it was somewhere else. Is there some sort of option I need to enable for it to produce a log? Link to comment Share on other sites More sharing options...
dubiousintent Posted July 12, 2016 Share Posted July 12, 2016 (edited) Sorry to say but if there isn't an NVSE log, then you either didn't set it up properly or failed to start it correctly. It always creates one with initialization entries automatically. I've refined my earlier reply (the "Plugins" folder is NOT automatically created, for instance), and added it as a new section to the "FNV General Mod Use Advice" article. Now it covers not only NVSE but also JIP and Lutana script extenders as well. -Dubious- Edited July 12, 2016 by dubiousintent Link to comment Share on other sites More sharing options...
gigaus Posted July 13, 2016 Author Share Posted July 13, 2016 (edited) Thank you for that, though....I 'think' I installed it correctly. Three times now. I went back and made sure I did everything the guide said, checked that the version popped up when 'getNVSEversion' was cced, it did....and I still get no log. Wipe, try with no mods, follow it to the letter, check version, fine, still no log. I even went for a video just incase I'm being increadibly stupid and....No, no I'm installing it the same way, getting the working version, and there's still no log file. I've made sure to install it just is...I'm using the 5.0b2 [stable] version, and I'm at a loss for what I'm doing wrong here. I'm supposed to copy the .exe over and the 4 .dlls to the root folder with the NV .exe, run vanilla, then run the NVSE .exe, THEN use shortcuts to run the GECK with the NVSE, and that should get to work, right? What am I missing here? Edited July 13, 2016 by gigaus Link to comment Share on other sites More sharing options...
dubiousintent Posted July 13, 2016 Share Posted July 13, 2016 (edited) You are correct in the steps you say you are taking (as long as your GECK shortcut has "nvse_loader -editor" for a command line. ("The normal editor can open plugins with these extended scripts, but it cannot recompile them and will give errors if you try." - nvse readme) Which leads me to suspect ... Where do you have the game installed? The Steam default of "C:\Program Files" tree I'm guessing? If so, that is why you can't get a log file. Everything under that folder tree actively resists allowing any new files or changes to existing ones after the initial installation of a program/game. Even if you run as "admin" and set the folder to give everyone "full control" it resets the file and folder permissions back to "read only". The only real solution is to move at least FNV (but preferably all your Steam games) out of that tree. See the "Installing Games on Windows Vista+" article in my signature. It explains this in detail and has a link to the official Steam procedure for moving games. (Which has evolved to meet this particular problem.) -Dubious- Edited July 13, 2016 by dubiousintent Link to comment Share on other sites More sharing options...
gigaus Posted July 13, 2016 Author Share Posted July 13, 2016 I ran the NVSE loader with that -editor change, should I have ran the GECK with that? And yeah, it's in C: Program Files (x86). I only have one HD atm. As a result....Where could I put it other than C:? Link to comment Share on other sites More sharing options...
dubiousintent Posted July 13, 2016 Share Posted July 13, 2016 (edited) The " -editor" switch is only for running NVSE with GECK; not with the normal game. That is what the switch is saying: "running with GECK." You shouldn't need any command line switches when running "nvse_loader" before the game, unless you have an unusual setup covered in their documentation. All you need to do is get the game out from under "C: Program Files (x86)". You can simply create a "C:\Games" folder, set the permissions on it, and then follow the Steam procedure for moving the game. Creating the folder and setting it's permissions first is the key trick they failed to mention. But follow the procedure. Don't just move files around or you will break your registry. -Dubious- Edited July 13, 2016 by dubiousintent Link to comment Share on other sites More sharing options...
gigaus Posted July 13, 2016 Author Share Posted July 13, 2016 Okay, I did that without breaking my registery; There's still no .log file....I am looking for something with the extension .LOG right? And it's supposed to be in the same folder as the NV and NVSE .exe right? Really hoping I'm just looking in the wrong place, because right now it seems like something's really wrong despite doing everything right. Link to comment Share on other sites More sharing options...
dubiousintent Posted July 14, 2016 Share Posted July 14, 2016 Yes, extension ".log" in the game root folder (i.e. "C:\Games\SteamLibrary\steamapps\common\Fallout New Vegas") along with FNV.EXE and NVSE_Loader.exe. File "nvse_loader.log". I am assuming you have configured Windows Explorer to display extensions as you know about them. Did you use "nvse_loader.exe" to launch the game, after you launched the Steam Client (but not via the Steam Library game entry) and ran the vanilla launcher at least once? Are you using FNV4GB or anything else as your launcher? Have you tried to actually load a save game and then quit to desktop? -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts