Skyrim Revisited Pre-Release Feedback

[Nozzer66]

The only real guide I know about it is on the web page for it at Nexus. As for SR:LE and Perma, if you follow the suggested load order with it that raulfin suggests in the PCaPP forums you shouldn't have an issue.

[xxx78]

Thanks for responseNozzer66 and for the explanations

Just a few things...

 5) No, it's telling you to install the two files from the Mod's Optional Files section. The files called Dawnguard Patch and Dragonborn Patch.

 

So what you are saying that all places it say "Optionals:" in the guide, actually mean that I shall install them all and that it is not meant as optional installations?

 

6) No. Expand the mod using the + and then follow the directions.

 

OK, but I still dont get what to do. In the guide it say to "Delete the light emitter changes" and "remove" later down but not what to remove. Also when I open up the mod with + there is nothing named "light emitter", so I need a more detailed instruction

[Nozzer66]

With the first one, yes that's what it's saying; find the optional files that are named and install them.

 

With the second one READ the instruction. It says: Right Click ELE_Legendary_Fs_Wt_Lite.esp>"Light" and select "Remove". Doesn't say anything about Light Emitters.

 

You select the plugin in TES5Edit, when it's done you expand it. Right Click on 'Light', a menu will pop up. Select Remove.

[Pretendeavor]

So what you are saying that all places it say "Optionals:" in the guide, actually mean that I shall install them all and that it is not meant as optional installations?

In general they are called "optionals" because they are separate downloads mostly found under the Optional and Misc sections on the Nexus page of the mod in question. If they are listed in the guide that means they are needed!

 

About the EFF replacement file, you should indeed select 'merge' when prompted by MO. If you select 'replace' it will delete all previously installed EFF files. You just want the replacement file to .. well.. replace only the files it is supposed to replace, and the 'merge' option will do that.

You could also install it as a new mod (and call it like 'EFF Replacement File') and place it below the main EFF mod if that is what you prefer. That way it will still overrule the main EFF files that it is supposed to replace (as seen in the 'Conflicts' tab if you right-click the mod and select 'Information'), but the overruled files will still exist in the main EFF folder. I actually do this a lot, it helps me organize my mod list. But to each their own.

 

An example of a situation where this can be useful is Race Menu. The main file has been updated several times in the past few months, but its optional file stays at v2-5-0. Instead of 'merging' the optional file with the main file every time it gets updated, I put the optional file in its own folder. This prevents me from being stupid and forgetting to reinstall it. (plus that way I don't have to un-hide and find the optional file in the MO downloads tab every time.. -lazy- )

Edited May 20, 2015 by Pretendeavor

[xxx78]

 

With the second one READ the instruction. It says: Right Click ELE_Legendary_Fs_Wt_Lite.esp>"Light" and select "Remove". Doesn't say anything about Light Emitters.

 

You select the plugin in TES5Edit, when it's done you expand it. Right Click on 'Light', a menu will pop up. Select Remove.

aha...hehe...I saw that when I read it earlier but did not connect the dots, thanks m8 for teaspoon feeding me

Its just how this guide have a tendency to confuse noobs like...think I need a serious talk with Neovalen at some point

[xxx78]

In general they are called "optionals" because they are separate downloads mostly found under the Optional and Misc sections on the Nexus page of the mod in question. If they are listed in the guide that means they are needed!

 

About the EFF replacement file, you should indeed select 'merge' when prompted by MO. If you select 'replace' it will delete all previously installed EFF files. You just want the replacement file to .. well.. replace only the files it is supposed to replace, and the 'merge' option will do that.

You could also install it as a new mod (and call it like 'EFF Replacement File') and place it below the main EFF mod if that is what you prefer. That way it will still overrule the main EFF files that it is supposed to replace (as seen in the 'Conflicts' tab if you right-click the mod and select 'Information'), but the overruled files will still exist in the main EFF folder. I actually do this a lot, it helps me organize my mod list. But to each their own.

 

An example of a situation where this can be useful is Race Menu. The main file has been updated several times in the past few months, but its optional file stays at v2-5-0. Instead of 'merging' the optional file with the main file every time it gets updated, I put the optional file in its own folder. This prevents me from being stupid and forgetting to reinstall it. (plus that way I don't have to un-hide and find the optional file in the MO downloads tab every time.. -lazy- )

Thanks for response Pretendeavor.

 

Yeah, I have read up on how MO work, but to go from there to choosing merge or to install files as separate mods from same mod is a tricky area. I like to reduce number of mods on install list to minimum for better overview, but it is safer to just install files from same mod after each other, but damn it look messy.

 

Also if I install all files from same mods as optional mods and have hundreds of mods installed, I can imagine that all the files that get processed just to be overwritten will at some point take resources and time and maybe create issues. This is the same reason I try to avoid using hide, but it can be practical sometimes.

 

About optionals, maybe Im slow but I did not grasp its function in the guide, optionals sounds like very much like optional

Edited May 20, 2015 by xxx78

[Pretendeavor]

Ah, I was under the impression you were confused about the MO merge option, my bad. Yeah you're right about it getting messy if you do that with all optionals. I only do it with a couple of mods, so I can revert back to the original files more easily. It also depends on the size of the files.. Like I delete a lot of texture files that get overwritten (sometimes multiple times) to save up some precious SSD space.

[Nozzer66]

The only one I don't merge all into one is aMidianBorn. I leave them all separate.

[xxx78]

The only one I don't merge all into one is aMidianBorn. I leave them all separate.

aha that's great to know, thanks :)

[xxx78]

Another "quick" question.

 

I just wonder if it will be any problems if I install optional files with less resolution than the one in the guide, as long as I do it with all mods?

Im afraid to run into memory issues or other issues, so I try not to go higher than 1024. Most important for me is a smooth gameplay and I can sacrifice graphical improvement for fps.

Personally I don't think there will be any issues with installing mods with less resolution, but since I dont know much about this I rather ask then to run my whole installation into the ground.

 

Cheers :)

Edited May 20, 2015 by xxx78

[Neovalen]

Shouldn't be a problem, assuming there are no added bugs with the lower resolution archive (been a few examples of late with downscaled textures being corrupted).

[xxx78]

Ok I was not aware of that being a problem. What kind of problems can corrupted textures do? is it just that they will look strange?

 

I can't imagine how you have managed to test all this and combine things together, some files here and some files here, its truly amazing the work you have done.

 

Edited May 20, 2015 by xxx78

[Nozzer66]

More likely that they just wont load and you'll get lovely pink purple areas where they should be.

[Neovalen]

Alright - SR:LE converted to the newly released LOOT stable version. Growing pains incoming, if you find anything missing / wrong please let me know and I will fix it.

[cybexgames]

@Neo,

 

I have Oblivion installed as well, so I added --game=Skyrim to the Arguments text box in MO.

 

This may be needed to the documentation.