Georgiegril
-
Posts
4284 -
Joined
-
Last visited
Posts posted by Georgiegril
-
-
Just to step in--
skse can be found here. The installer version makes it very easy. I recommend the 1.7 build.
SkyUI adds a ton of features to the game; definitely why it is the most downloaded mod.
-
I agree that starting over is probably the fastest solution, if you take the time to set it up carefully.
The below may help you do that.
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, have you used BOSS for your load order? It does not look right to me.
If so, please replace your load order with your BOSS log text file and enclose in spoiler tags.
Please TES5Edit clean all the mods and DLCs the are flagged by BOSS, and take caere of the rest of the messages BOSS gives you as well, if you have not done so.
Also it looks like you have not run the reprocc .jar, which you need to do.
-
please post the entirety of your BOSS log in text file format, and enclose in spoiler tags.
Look on the top toolbar. The third icon to the left is a squarish thing. IF you click that it will bring up a pulldown menu where you sill find the spoilers tag. Highlight all of the BOSS log text, once you add it to the post. They select "spoilers"
BEfore doing that you need to finish cleaning your Dlcs and the mods that need it.
You also need to properly hand place the unrecognized mods.
You have a large number of inactive mods. Deactivating mods does not remove their effects, particularly if they have scripts. This could be your problem.
However, it could also be a memory issue, so keep working on that, and also post your skyrim.ini and prefs.ini.
-
Sorry, there are too many security issues going around the web for me to open random files.
Please go to the BOSS Gui, select to have the log generated in text format, then copy/paste that into your post, and enclose in spoiler tags. You can find those in the pull down menu of third icon to the left on the top toolbar.
Probably you will get more looks from more people who can help you in that way.
-
If you haven't used BOSS or cleaned your flagged mods/DLCs with TES5Edit, do that first.
Get BOSS. The installer version is the easiest to use. Here is a video tutorial by Gopher on how to use it; though the installation part is not needed if you choose the installer version.Use it. Read the log it generates. In the log, you will see messages about TES5Edit cleaning, and there will be a link that will take you to TES5Edit and tutorials on how to use it. You can also get Gopher's TESEdit video tutorial here.
-
The Unofficial patches are mods. They take care of a lot of bugs Bethesda never fixed. You can get the first one here. Read the whole mod page, it will help you.
If you click on the link to TES5Edit that you will find in your BOSS log, it will take you to a tutorial on how to use it.
I think you would also find Gopher's Beginning Mod video series useful.
-
The beginning sequence is notorious for not liking mods. The solution is to start the game unmodded and play through to the cave exit before making changes, or use an alternate start mod to avoid Helgen.
The below may help you: (especial the Gopher tutorial at the bottom)
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
-
Please post your BOSS log. skyrim.ini, skyrimprefs.ini, and the last forty or so lines of your papyrus, at the time you are trying to enter an interior..
Please add to that list any mods you recently removed and any supporting programs (like skse, etc. with versions.)
The 4GB memory patch is no longer needed. ENBoost might help, but it is difficult to make any recommendations, as velve55 points out, without more information.
-
Please copy/paste your BOSS log (open BOSS GUI, chose to have the log render in text format.) Enclose in spoiler tags, which you can find in the pull-down menu of the third icon to the left on the top toolbar.
List mods that BOSS doesn't sort (like texture mods without .esps) and utilities you use (like any texture optimizers, skse, etc.)
If you haven't used BOSS or cleaned your flagged mods/DLCs with TES5Edit, do that first.
The 4 GB patch is obsolete. However, since your problem could be related to resources, please get and use the Skyrim Performance Monitor, and post those results. (Like BOSS this is a separate program, not a mod.)
Finally, if you have made any changes to your skyrim.ini or skyrim prefs.ini, please post those as well (also enclosed in spoilers.)
-
Did you try removing the reprocc.esp from the plugins, then re-running the reprocc.jar?
-
Did this list ever work for you? Did you add mods one at a time, test them before adding the next? Did you start out with a pristine vanilla skyrim--ever you never used a mod before or you used the STEP Guide to return to vanilla (just a reinstall is not enough).
If the answer to any of the above questions is "no," you will save yourself days or weeks of trying to figure out the problem by simply starting over and using careful modding procedure.
To that end, the below might help youl.
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
If you gave been playing with this list, and it stopped workimg, then please replace your mods list with your BOSS log. Add information about what changed just before the crashes began (for example, did you update skse?), versions you are using of skse, etc, and what you have done so far to try to fix the problem.
-
No offense geogiegril but bloodbomb has asked for suggestions on good mods that suit his criteria. Now your response has left him no better off
Sorry I don't have to much time to write a list but I'll give you my quick rundown of face mods and mods that fit your criteria
For your gfx overhaul I recommend taking a look at the step guide which is a great start for making skyrim look loads better without sacrificing performance another one would be texture pack combiner which is more performance heavy and saves looking through literally thousands of textures both these are great starts and then go into categories and then models and textures and look for something you like personally I love amidians work landscape and book of silence are his best work in my opinion
Allow me to clarify. Mods are extremely personal.What one person loves, another does not, as is evidenced in the posts above. Also what works with one computer--particularly when dealing with graphics mods--may not work with another. So, the key to being able to mod your game heavily is not which mods, exactly, but how. Although my answer may appear tangential, my intention is to the core of the question--how can I have a awesome, heavily modded game that I will have a great time playing. Have fun!
-
Are you using the Unofficial Skyrim Patches?
Also have you used TES5Edit to clean your DLCs?
If not, taking care of those two things may solve your problem.
-
My advice to you is to read every word available on any mod you are considering, including the discussion page. Make any change one at a time and play through to test before adding the next. If you decide a mod is not what you are looking for, return to a save from before you first added it to avoid lasting problems.
Also, make sure to get and use BOSS, read the log it generates and take care of all the messages--including TES5Edit cleaning, which may not have been available when you first played.
-
Please replace your mod list with your BOSS log text file. Also, enclose in spoiler tags, which you can find in the pull-down menu of the third icon to the left on the top toolbar.
-
I use random alternate start.
It seems very odd that you would get at CTD if that is the only mod you have.
Are you starting a new game? Did your old game have mods? If so, you probably have leftovers from that game.
Go to the STEP guide to revert to vanilla skyrim-- this is faster than the traditional uninstal/reinstall, but it removes all traces of mods, which the traditional method can miss.
-
Did you open up the esp in the CK and re-export the texture (alt-f4, I think)?
-
I suspect that you have something set for followers to pick up items automatically. I'd suggest you open up the configuration menu and check your settings.
-
Are you sure they are ALWAYS stuck in the ground? Characters feet are sometimes stuck in the ground in the vanilla game; no way around it.
If it is constant (even indoors, etc.) then I would look not just at your body mods, but also any mods you have that affect terrain.
You may just have to try removing them one at a time to find which if any are involved.
-
Alternately, you could just make a regular follower, and then use the Amazing Follower Tweaks mod to manage your follower--it allows you to configure all sorts of things, including treating your follower like a pack mule. Also lets you summon them easily when they get lost, etc.
-
It could be that background services (like autoupdates, IM, autoscans, etc.) are taking up memory and causing the lag.
It could also be that you have simply pushed your gamer farther than it can go, given your low resources--you say that you have played before without this problem, but also that you have been adding more. It may just be too much.
I suggest you get Skyrim Performance Monitor and take a look at what is actually happening with your computer in-game.
-
You are welcome, good luck!
-
The guide that is posted just above yours is, in fact, step by step.
Clean Game ctd on start, Troubleshooting not working!
in Skyrim LE
Posted
I think your problems started with your method of reinstalling. Uninstall/reinstall will not remove all traces of mod content.
To do that you need to follow the Step Guide for reverting to vanilla. (the link is in the spoiler-tag section below.)
Then, to set up mods without having troubles, the below may help you.
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