z929669

I will see about creating a "sidebar" template. Template complete. Try using according to the examples.

You can do it either way. When moving to the Bash Installers, you will either get a confirmation to overwrite, or you won't. If the file name is unchanged (for me, it usually is not, since I add the version ID to the file name), then you will overwrite. The result will be that the background color for the mod turns orange, and the box may also change to red. Just right click on the mod and select "Anneal" to fix. If the file name has changed, there will be no prompt to overwrite, and when you go back to WB Installers tab, it will refresh, and you will see the new version at the bottom of the install order list (I always sort by [Order]). In this case, I recommend that you always move the new version to the Order slot just before the old version ... then INSTALL THE NEW VERSION BEFORE UNINSTALLING THE OLD. THEN, uninstall the old. In this case, Anneal will not be required. Why place the new above the old and install first? Because whenever a mod is uninstalled, WB looks for source from other mods that were overridden by that of the current mod being uninstalled. If any of the overridden source is from a particularly large package, then it will take awhile to unpack the source files from that beast ... only to be again overwritten by the new version. If you first install the new above and beforehand, then the source will be pulled from the new version once the old is uninstalled. You just saved yourself a big wait if you use either method above. WB keeps track of all CRCs and the entire source file assemblage (and the override info) of all mods in the Installers, so moving things around can always be easily repaired using Anneal or Anneal All.

you be illin' you mean? Yep, very 80s

Still have not tested with DB at any length yet, so I will see about my logs when I get to that point @ fizzer thanks for the input can you confirm if the guide led you astray or was it user error?

Did you try with the mouse lag INI fix?

Thanks for your edits mishmash. I like the idea of simplifying and consolidating wherever possible. I am in favor of keeping the main guide topics centralized and side-barring ancillary material. There are many ways to do this, but I prefer creating margins. This takes a bit more coding know-how, so if someone wants to go into the SIG and other guides and begin demarking segments that are tangential to the main points, others can take care of formatting. Streamlining content is important right now. @Kelmych & WilliamImm You have made some edits out there too, so I suggest that you three team up if you want. The more the better. (and please try to keep all text in the third person (i.e., avoid using 'I', 'we', 'you')

Glad it is implemented (more) correctly now. Much can be done with those ENB settings, too, and every ENB is a bit different.

All compression is lossy, so DDSopt will not increase quality of the native texture. At most, it will reduce size without loss of quality of already improperly-compressed formats. However, the mip treatment actually improves many textures' mip-map levels so that distant detail is actually enhanced noticeably. Especially rocks and foliage.

We don't delete anything around here :P Feel free to make any edits you think apply.

... OK and some of the older wannabe Americans too :P

I had ran across the same thing awhile back, and it was determined there was a missing mip level after optimization. Looks like the same thing at play here.Those are my first DDSopt results, before Ethatron added the special foliage treatments, since these have an atypical alpha. Using the latest release with the settings on the wiki will give you better trees and foliage LODs ... improvement actually.

Funny, but completely understandable. "Sick" is relatively new lingo used by young Americans these days :P

This looks promising. Anyone care to post some screens in the working changelog? Let's compare the lot again.

Lots of good info in here and linked, thanks!

Yes, I know, but that only covers up the problem. I think Metro is likely responsible for your current problem and perhaps more to come ...?

This happens for a time after recent updates. BOSS has not yet caught up with the latest release schedule, which is very fast since DB was released.

One more confirmation that I will not be moving to Win 8 until they eliminate all traces of Metro and assoc. apps, and Linux may have some real competition by then.

Very strange. Do you have anything running that prevents apps from writing to the reg? Aniti v/m? I turn of UAC personally. I think it is the stupidest feature that can inhibit the power user.

Are you using Lush Trees? I am pretty sure that those are Vurt's meshes with no textures assigned. You are missing one of the texture options

I added the updated BATs and instructions to the wiki and set up a link from the Guide. This will be nice for collaborative editing and updating as necessary. Once completely stable, we cn serve up an archive of the pre-configured fix.

Nice work on the Guide Kelmych!

That's a lot more textures with increased resolution than the DIFF that was published yesterday showed. However, they didn't check the files against any of the 3 DLC bsa files. I did notice better resolution versions of the Dragonborn textures in the HRDLC, but that wouldn't affect the comparison you did against the old HRDLC. Do you have a list of the improved textures that weren't in the DIFF list and/or some of the errors that were fixed? I found a few errors fixed in addition to the directory assignment fixes (e.g., a spelling error was fixed to change woodenladel01 to woodenladle01) but in my spot check I didn't find any of the duplicates with STD vanilla or across the 3 HRDLCs fixed and none of the link files had been removed. I checked a few of the files in Tweaks to see if there had been any changes in the HRDLC files they replace but I didn't find any. Did you?I have yet to do a thorough check, but the best thing would be to check the compilation of all of the old texture BSAs combined (with fixed HRDLCs, non-hi-res vanilla, HF and DG) against the new combined result. This would give the comprehensive net change (with DB additions). I am hopeful that we no longer even need a fix ....

Cool, thanks. may be after the weekend, as we are on a sprint to release 2.2.1