Nearox

Yes. There is no individual belt texture.

That mod is pretty outdated though... If you are looking for some city and towns, I can (shamelessly self-promoting I know) point you to A Real Explorer's Guide to Skyrim, which works right on top of STEP Core. You can pick out any mod you like, follow its instructions and grab a patch at the end when needed. TAVE is not in REGS though.

I think title should be centred imho. And given a different color, bigger size and maybe also different font. After title, everything aligned to left.

Looks like a good start DY!

I always manually remove a mod and completely reinstall. Using merge is imho not really a good idea if you are unpacking the bsa files.

Can you determine the latest esp to affect the lantern by using MFG Console mod?

I don't have that in my own game, I think. I can't test right now. But it's best to forward that question to gandaganza, author of Realistic Boat Travel. He's casually active here and active at the Nexus as well. He can probably tell you what exactly most be the conflict, because he made a REGS compatible version :)

Also, are all the esps enabled in MO? I made that error more than once :)

Hmm sounds like something wrong with load order. Are you using BOSS or LOOT? If using BOSS, be sure to grab the userlist.txt from the download.

Alright, the PaMa patcher unfortunately gets stuck at SIC - DLC2.esp. Disabling it gets it all the way down to SR Conflict Resolution.esp. Seems like every esp that has a master dependency on Skyrim Immersive Creatures.esp gets the patcher to spit out an error. T3endo says is nothing he can do and is on the side of the author. I'll contact lifestorock and see if he is willing to look into it.

Cool. Btw check the PaMaxml.zip, it has the documentation for the patcher (as in the new version of the reproccer). A quick look says this is gonna be promising for compatibility with other mods! Hmm just checking but did you install the RRR - ELFX patch?

Just got in the PM beta, will check it out for a couple of days.

Mod Anthology is for accepted (or dropepd) mods. SPERG is not in the Anthology, instead it is in 'Mod' section. You can use SPERG without any of the packs, no problem. Might have to do some minor conflict resolution here and there. Might be good to ask the question in the New Gameplay Overhaul thread in the packs section, those guys can help you best.

I'm on tablet now so can't type in detail but you can fin it in one of the MO subdirectories. Profiles iirc.

Please post your modlist. Do you happen to have Helgen Reborn installed? Also that memory blocks log would still help to at least rule out a potential issue...

Your CPU won't die, a non-OC CPU will go 15-30 years or something. Generally hardware components dont usually break a lot, except from HDDs and other components with moving parts which have a slightly higher chance. Why'd you want a new case though? As long as the GPU fits and your overall temps are good and you dont need extra expansion slots, there's little reason to get a new one.

Totally awesome once again! Now DoF might even be an option for us performance users :)

phazer12?

For that reason I would first like to read the beta documentation before testing it in game :) I have no doubt that he can create what he wants, as long as the plan is good. SkyRe worked as advertised, barring a few things that were later fixed in the unofficial skyre patch.

Didn't realize it was in beta, signed up just now to test it out, hope I can still get in :)

Sounds good. One big installation section is allright too. However if we are talking about consistency though, I would prefer to see TES5Edit Mod Cleaning Required, BOSS Masterlist/LOOT updating required, Bash Tagging required all in the same style/colors in every pack. If that is possible by means of a template, great :) But why then not make these fields that the pack author can fill in, and which accordingly are shown in their respective style/color at the pack page? Keep in mind I am not a programmer and have little knowledge about html, so I don't really have an idea if what I suggest is possible or viable to make.

Doesn't matter if it is 3 years old. CPUs are no longer being improved in accordance with Moore's Law, so their effective speed hasn't gone up very much since sandy bridge. The 2500k is still a powerhouse and upgrading will net you maybe 10% more fps, under the best conditions. If on the other hand you upgrade your GPU, you can see like a 500% increase in FPS as well as overall improved image quality due to being able to run at higher settings. Look at this chart: https://www.tomshardware.co.uk/charts/2014-vga-charts/04-Metro-Last-Light-1080p,3596.html Your GPU is almost at the bottom with 8.70 FPS. However if you buy, let's say, an R9 280x for 220 euro (300 dollars I guess) then you can increase your FPS in that game according to that chart to apprxoimately 55-60! Upgrading your CPU to a better one would costs more and would only gain you 2-3fps, at most. Your specs say it is a 600w PSU but it doesnt say if it is 80+ quality. It is important to know this as the actual output of your GPU may be much lower than the theoretical.

If you explain it like that, then yes that is what I meant with my previous posts. If the author can fill in a kind of 'mod table form' which, when viewed at the pack page by the user, ends up looking a bit like SRLE, that would be great! Obviosuly doesn't have to look exactly like SRLE, but I personally find the vertical order of information to be very useful. Best thing even would be if the form to fill in the table for the author has fields for not the basics but also more advanced instructions. That way every pack could look more consistent. There should, imho, be form fields + tickable boxes (so that author can enable/disable a field at discretion) per mod for: Description: Author: Version: Files to download: (e.g. main + update + miscalleneous, to be filled in manually by author) TES5Edit cleaning required: (if possible, make it so that automatically a link is generate to one of the cleaning guides at the wiki) Bash tagging required: DDSopt required: Mod merging required: Special install instructions: (e.g. do not install etc.) Optionally a field for BOSS/LOOT rules but they could also be provided in a handy overview at the end of a pack. Again, just some ideas, happy to contribute and happy to see you guys are taking pack author's opinion into account!

2500k seriously not worth upgrading right now. the new cpu's are only like 10-20% faster, and dont overclock so well. Moreover a 2500k does not even bottleneck a 780ti, last I read it. Instead of buying a new system, which will be expensive, put that money in a shiny GPU like a r9 280x or, preferrably, 290 or 780:) Maybve overclock the 2500k to between 4.0 and 4.2ghz, which basically any 2500k can do easily. You could also consider buying an SSD, as a modded skyrim will often load 20-30gb of data, so it will increase your load speed and potentially reduce stutter (which could occur from regular HDD)

I don't know... In my experience it is very tedious and, from a pack author's point of way, unnecessary to add a seperate wiki entry for every mod added to the pack. Moreover mod tables also really limit your options with regards to layout. S4N I understand the need for consistency, but that is easily achieved by making packs in SRLE format... Unless you are speaking of a different kind of consistency. I don't think it benefits the packs if they are limited to mod tables for sake of having a similar look to STEP Core. We tried pretty hard with REGS, it was in mod table format for a month or so, but it just became unworkable after a while. After switching to SRLE formatting everything became a lot easier, and the feedback of REGS users at the time was exclusively positive about that change. As for intercoonectedness of data, what are you referring to? Even if 2 packs use the same mod, or if a pack uses the same mod as STEP but in different ways, having them all refer to the same mod wiki entry, while technically being interconnected, what is the benefit of that? Instructions are made on the pack page anyways, and I don't think it would be a good idea to have every pack author write the instructions on the mod wiki page as that would clutter them up real fast.