Georgiegril
-
Posts
4284 -
Joined
-
Last visited
Posts posted by Georgiegril
-
-
Please replace that mod list with your BOSS log text file (open BOSS GUI select to have log generated in text format. Enclose in spoiler tags, which you can find in the pull-down menu of the third icon to the left in the top toolbar.
-
You appear to have remains from your last game in your current one.
You need to start over, but this time use the STEP Guide to Revert to vanilla skyrim.
Generally speaking, your papyrus log is not a crash log. It is only rarely useful in determining causes of crashes.
The below may be useful to you in starting a new game without the headaches you've been having.
1. Go to STEP and follow the directions to revert to vanilla skyrim.
2. Start a new game, do not attempt to apply an old save, it will not work and may reintroduce corruption back into your now clean game.
3. Do not make any changes at all until you exit Helgen (the other option is to start with an alternate start mod to avoid the Helgen sequence.)
4, Before making any changes, read everything available on the subject. If it is a mod, read every last word of the readme, description, discussion thread, everything. If it is an ini change, google it, visit a few reputable sources and determine if it is worth trying. Just because one guy puts up a list of his ini changes and swears buy it does not mean it will work for you, and it might even make things worse. When considering any change, mod, .ini file, setting, whatever, consider it in light of your own system hardware and software and the other mods/changes you intend to make. Investigate any possible conflicts before adding it.
5. When you are ready to make any changes (mods, ini settings, anything) attempt only 1 or two at a time. If it's a mod, run BOSS. BOSS is a regular program, not a mod. There is a useful vid for BOSS, here. Set it up to generate the log in .txt format, not html. Read the log and address any messages. In any case, play a bit to test for stability, performance, and compatibility. Make sure to properly place the unrecognized mods as instructed by the mod author, or use TES5Edit or WryeBAsh, or if all else fails, place it with similar mods that are recognized, though that is more trial and error. Also, a number of excellent mods require you use skse. You can find it here. It now has an automatic installer. on that page, you will see there is a link to a readme, which you should read for help understanding the program. There is also another gopher vid to help you set it up, here.
6. If you notice any negative effect of your change (not just crashes, but performance loss, glitches, anything), Stop. Do not attempt to keep playing and definitely do not add any new variables into your system. Investigate the possible causes. If it is a mod and you want to try to remove it, then remove it, but be sure to follow the author's removal instructions exactly. To be safe, go back to the save from just before you added it. (This is easy of you are slowly adding mods, but extremely painful if you add everything at once, play a bunch and have no idea where the problem lies. ) This will also help you avoid with script problems from removed mods that will continue and may get worse.
7. If you get stuck, post a detailed question before you get frustrated. Detailed means t include your BOSS log, noting how you placed unrecognized mods, other supporting programs you have used (like TES5Edit, skse, Any texture optimizers, enbs, etc.) Also provide your computer specs, any changes to your driver profile and/or skyrim ini files. Finally, provide details about the crash--how long you've had it, what changed before you first noticed it, any patterns like time playing, specific areas or activities like opening a menu or such. Explain what you have already tried to fix the problem and what the results were.
8. Once you get your mods and other changes the way you want them, your game is stable and performing well, then stop. Every time you add or change any variable, you are inviting instability. If a new mod shows up and you think you just have to have it, ask yourself if it is worth having to start all over for--because, you may have to. If the answer is yes, then go ahead and try it and if your game crashes, well, you were willing to take the risk.
Recommendations for maintaining a trouble free game:
1. I personally suggest avoiding the Steam workshop for mods, because it will automatically update and sometimes even remove mods in your list, which can cause your game to die. Also, playing with Steam in offline mode will prevent unexpected updates from causing havoc.
2. Disable auto updates and avoid using quicksave, as these increase the chance of savegame corruption. Also, if your save does become corrupt, you will need to go back to your last working full save, which can be extremely painful if you rarely make them. You can do this by going into your Prefs.ini text file and then making sure the following lines look like this:
[Main]
bSaveOnPause=0
bSaveOnTravel=0
bSaveOnWait=0
bSaveOnRest=0
[saveGame]
fAutosaveEveryXMins=0.0000
For people who want the convenience of auto save with the functionality of a full save, there are a few mods you might check out, such as Ishara's Normal Numbered AutoSaves
-
Well, I doubt that will solve your issue, and if it did, it would simply cause another script to have a latency problem instead.
There are a few things you might try to help clean up your scripts, like adding these lines to your skse.ini, if they aren't there already
[General]
ClearInvalidRegistrations=1
[Memory]
DefaultHeapInitialAllocMB=512
ScrapHeapSizeMB=256You could look at your papyrus log and see if you have leftover scripts from mods you have removed...and if so, you might try Save Game Script Cleaner. A caveat: Although this particular save cleaner seeems more effective with less collateral damage than other script cleaners, using a script cleaner is still inherently risky. Meaning you need to be willing to start a new game if this breaks the one you've got.
Other than that, the only other real option is to play with fewer script-heavy mods. However, since it is impossible to remove all traces of scripted mods from your game, again you are looking at maybe having to start all over.
Or make peace with the lazy birds.
-
It's not your computer, it's the game engine.
-
You have a lot of mods that are very script heavy. The Skyrim engine can only process these so fast, and one at a time. What you are probably looking at is the effect of that; the bird script can't run until everything before it does.
-
What exactly do you change to make that happen (you say it doesn't happen if you use the default .ini values...)
-
If this is not your first game with mods, and you did not use the STEP Guide revert to vanilla to start your new game, that could be your problem. You will want to do that first.
If you have never used mods before, or you did use the STEP Guide revert to vanilla, and still have the problem,
Post your BOSS log text file. Enclose in spoiler tags. Add a list od mods and programs you are using for skyrim that BOSS does not manage (like skse, enb, texture mods that don't have an .esp, etc.) Also list any mods you have removed from the game.
Also post your Skyrim.ini and Skyrimprefs.ini, enclosed in spoiler tags.
Capture about 40 lines of your papyrus log when you are trying to go into 1st person and it changes to 3rd. Post that, again enclose in spoiler tags.
The spoiler tags are in the pull-down menu of the third icon to the left on the top toolbar.
-
Are you using the skyrim performance monitor? It can help you figure out what you can increase, and where the problems are.
Off the bat, I'd say your biggest problem is
multisample=16
This controls your Antialiasing, which is very demanding. You can get better results visually with less demand on your system by disabling this in the game and forcing it on your card, using Nvidia Inspector instead. This guide may help you with that.
As to the crash on load, that is usually a missing master or load order issue. If you replace mods list with your BOSS text file, enclosed in spoiler tags, I will take a look at it.
-
1. When you reinstalled, did you follow the STEP Guide revert to vanilla? If not, then you may still be looking at a mod problem.
2. Are you using the Unofficial patches? Which version?
3. There is a lot of information on this in the Elder Scrolls wiki, Have you looked through that and tried the suggestions?
-
Please replace that with your BOSS log text file and enclose in spoiler tags.
Also add a list of any mods or supporting programs that BOSS doesn't manage, and another list of any mods you have removed since starting this character.
It may also help to have part of your papyrus log-- just 40 or so lines from when you are in the tavern and try to interact with a bard.
-
-
-
The changes you made would have decreased the load on your GPU quite a lot.
I strongly suggest you use the Skyrim Performance Monitor, or some other monitoring software to capture what is going on in your computer while playing. You may have been overheating, which can damage or kill your GPU. Especially if you are planning to try to push those settings back up.
-
This thread will probably help you.
-
It sounds like a GPU issue--maybe overheating, maybe a driver issue...hard to say without more information.
Please provide your computer information
(CPU, RAM, GPU, VRAM, driver version), graphics settings (in game and also anything you have altered in your graphics driver game profile or your skyrim.ini/prefs.ini).
Finally, get and use the Skyrim Performance Monitor to collect data in game, and post that.
-
When you reinstalled, did you follow the STEP Guide to revert to vanilla? If not, that is probably at least part of your problem. I recommend you do that, then add mods/other changes one at a time, so you can easily identify any other cause of the problem.
If the problem exists after having done that, please:
Post your BOSS log text file, enclosed in spoiler tags.
List any mods BOSS does not manage (like mods without .esps) and any mods you have removed from this play-through.
Also, get and use the Skyrim Performance Monitor and post the data it collects.
Finally, collect your papyrus log (this should be short if you are freezing immediately, if it is not, definitely put in spoiler tags.)
If you do not know what BOSS is, you probably need to watch Gopher's beginner's mod tutorial.
-
Also, please get Skyrim performance monitor, use it and paste the data it collects.
-
Please read the "how to ask for help" pinned thread on the top of this board.
-
-
Please replace that list with your BOSS log (open the BOSS GUI, select to have log generated in text instead of html.
Also, please get Skyrim performance monitor, use it and paste the data it collects.
-
copy/paste the text file of your BOSS log, enclose in spoiler tags.
Also make a list of any mods you removed and/or any mods/programs you are using for skyrim not organized by BOSS (mods without esp files, things like skse, etc.)
Also provide about 40 lines of your papyrus log, at the time when you are trying to talk to a non-responsive NPC.
The spoiler tag is in the pull-down menu of the third icon to the left on the top toolbar.
-
I do think the problem stems from your earlier mod install.
To completely remove all effects of mods (which the steam delete local content does not), follow the STEP guide to revert to vanilla. It is extremely effective, if followed to the letter.
-
No, that is correct. You'd have to get into the CK for that. The uncapper would just adjust all conjuration, or whatever.
-
You can manually configure the Skyrim Uncapper to adjust leveling, experience, perks, to whatever you prefer.
Skyrim CrashToDesktop how?
in Skyrim LE
Posted
1. You need to put a message in your other post that it is a duplicate.
2. You need to get and use TES5Edit to clean the DLCs and mods that are flagged. (follow the link in BOSS for the program and the tutorial on how to use it.)
3. You need to take care of the other messages (for example, do you have CBBE?
4. You need to properly placed the unrecognized mods. Many times you can find this info on the mod author's page, or you can use TES5Edit to do this as well.
That is all just based on your BOSS log.
However, if you started this game having previously ever played a modded Skyrim, and you did not use the STEP Guides's process to revert to vanilla before trying to build a new game, it is very likely that you have leftovers from your last game which are causing, or will cause, crashes. In that case I would strongly recommend starting over after properly reverting to a clean vanilla game.