z929669

I think that it is worth mentioning that the memory patch is intended for 64-bit OS. Many users do run 32-bit architecture still, and it makes sense that the memory patch is not for them. We welcome corrections or enhancements to any of our guides.

Happy holidays everyone! May all your new gadgets boot and configure flawlessly ;)

Unrelated, but I reduced your top image to a more realistic size ... revert if you want, but it was too big IMO. As far as underlines in links, that is the standard behavior ... [http://www.nexusmods.com/oblivion/mods/44069/ Alive Waters updated]will render on the wiki as: Alive Waters updated ... not sure what you are linking to in your post

OK, that's fine then. Just wanted to make sure you knew about history and even linking to pieces of interest like diffs and anything history related that can be loaded in the browser. Appreciate the diplomatic touch though ... you are thorough ;)

@alt3rn1ty Just FYI: No need to describe changes made to any wiki page here on the forums ... what a PITA it must have been to create that post! ... all pages on the wiki have PAGE TOOLS > HISTORY link to give you a page that allows a diff compare of each edit or a series of edits. All of your changes will be shown in detail in the History page so that you don't need to explain anything again (except maybe for 'why' you changed something).

As I said before, whenever anybody takes it upon themselves to alter wiki guides or other pages, it usually results in an improvement, because it forces others invested in the guide to critique those changes and the result is almost always positive change Edit away! Guide us with your perspectives in action! EDIT: info in mod pages that relate to larger guides (like ENBoost mod page and ENB guide) is supposed to be a condensation of the most important 'setup' info from the guide (i.e., mod page is a quickstart installation/setup guide) ... if that helps.

Yes, good call alt3rn1ty. You might consider adding this to testing under Mods forum. You can use the download link for your share and this forum for the 'mod link'. Alternatively, we can upload to the STEP mod on Nexus as a Misc file in Beta until further notice.

If you are familiar with our DDSopt Guide, then you know that 'standard' = base vanilla and 'hi-res' = HRDLC vanilla. I also follow the main points that are outlined in our guide, so that is basically the description of optimization. I do know what you mean, but I just don't have time to go into all that detail in the description and maintain it all. Just test if you want and post back if you see any errors or issues. Once I determine what Tony671 did and how it may differ from what I did, I will possibly ask him to use some of the techniques I employed in an updated version of his mod. I mainly want to verify that these versions work fine and look good first.

Mod pages on our wiki ;) just click on any of the categories at right on the main page (or the "Detailed Instructions Available" and "W" links in STEP Guide mod tables). Our mod pages serve as the info source for mods in guides and elsewhere.

Correct ... also, tony971's stuff has more options and likely does not use quite the same techniques for certain textures ... for example, I convert uncompressed terrain textures to 565 format, but most would convert to DXT ... not sure what exactly tony is doing, but there are many ways to skin a cat, and i have not examined his readme's or techniques to be able to say how much differs ... his files are smaller though, so that tells me that I have more files included in mine (or that he has reduced more than I have). It would probably be a good idea for me to take a close look at his mod to determine the differences. I will do that one of these days unless someone beats me to it. @ophansologo I included the DDSopt log in the download, which provides all details as to the conversion of each texture provided.

I resized/altered images to better suit the flow of text and other elements. What you see is what I thought was the best compromise for display of text and surrounding graphic elements. Feel free to devise a better result if you can find one (note use of {{clear}} and positions of [[file:/Image:]] wiki code/syntax). Also keep in mind that browser window size will vary by user, and that whatever you derive will need to look 'good' at various browser resolutions.

Ask s4n (he created it for use on mod pages) ... I think it defines the style of the tag elements on mod pages. The tags contain (among other things) the icons for the mod attributes (e.g., Core)

OK, I see now ... :P Fixing ...

We don't use that data, because it just adds to the noise, and the GPU overclock does not add anything really noteworthy to performance.

I think that this still applies though. Note the name of the plugin was changed from "Cleaned ..." to "unmanaged: ...".

I fixed the links on the mod pages. Any #tab= needs to be changed to # wherever they exist for links to guides that have been converted from HT to TOC. If the links and the "cleaned * ESM" language were what was causing confusion, they are fixed. I had already fixed the mod-page notes concerning cleaned plugins for the DLC ... admin see this post. The issue is that the new MO update places all DLC into an 'unmanaged' plugin, so altering the plugins by cleaning them no longer places them in overwrite (I think ... defer to DY, Tannin, and GDSfan on this and the new instructions) ... we need to make sure to update this in all locations (i.e., possibly the MO guide and elsewhere)

Looks fine to me ... one thing I would like to change about this guide is to offload any info that does or could exist elsewhere: enblocal.ini settings - move into its own guide under cat INI Guide (like ENBSeries INI Guide) and reevaluate the need for the Quickstart section, because all relevant "quick" settings are already included on the mod page.enbseries.ini - Trim down substantially to only the most relevant settings to be included under the quickstart sectionEventually, all "quickstart" guide sections should be housed on the mod page and the actual guides should go into more detail, encompassing all info contained within the corresponding mod pages. When we create an ENBSeries 'mod' page, it could house all of the setings for particular packs to which they apply. For info on Packs and our Semantic Wiki implementation and goals, see the DD talk page.

That is a fair representation though, so looks good. thanks.

My head is not acclimated to this subject at the moment, and I never had much of a hand in creating the ENB Guide anyway, but I think it is perfectly reasonable to rearrange information flow in the guide like so: ENB Guide ENBoost Quickstart In-depth ENB Lighting Quickstart In-depth Please have at it! IMO, the Quickstart for ENBoost is really on the Mod Page and should stay there and should be linked from the ENB Guide > ENBoost > Quickstart section. Otherwise, we could switch that the other way (mod page notes link to ENBoost quickstart).

TOC layout is much beter for guides, but I do see what you mean with regard to linking to specific info ... tabbed layout parses things out nicely when provided a direct link; nevertheless, linking to a chapter or sub-chapter heading is very simple and apropos. See this rationale for the change and this Category for some compares. You should be able to fix all of your links by simply changing the portion of the link that looks like (as long as the tab-->chapter: #tab=to simply ... # Use case example: Linking a user to info about ENBSeries.ini setting "GradientIntensity" With HeaderTabs, unless each setting is under its own tab (which would be preposterous), there is no way to do this, so one sends the user to the tab itself and instructs taht user to "scroll down". http://wiki.step-project.com/ENBSeries_INI_HeaderTabs_Functionality#tab=_5BSKY_5DWith TOC, a precise link is possible: http://wiki.step-project.com/Guide:ENBseries_INI/Sky#GradientIntensity... the ENBSeries INI Guide is a bit different though since it uses subpages, so here is an example using the DDSopt Guide and pointing the user to info about supported texture 'base' types. IIn the first case, info cannot be linked directly, but in the second, it can: http://wiki.step-project.com/DDSopt_INI_HeaderTabs_Functionality#tab=DDSopt_Initialization_File http://wiki.step-project.com/Guide:DDSopt#Supported_.27Base.27_Types... furthermore, choosing the link is simpler in TOC format, because one only needs to load the page and ... (right click the chapter of interest) > "Copy Link Location" > paste > done. You should be able to easily update all of your links to point correctly, but another unfortunate aspect of Headertabs is that we cannot enforce standard wiki redirects, so once a former 'heading' (that has been linked in a forum thread) is removed or its name changed to suit the TOC layout, there is not way to redirect. Thus, updating links is a manual process. They at least should point to the guide though. Also, if you want to alter any of the guide wiki content or add to it, please do so! The suggested change seems rational, as it simplifies a common real-world use case. We could use more help on our wiki, so go for it. Changes are all reversible, and that is the beauty of the wiki ;) ALL USERS ARE WELCOME TO EDIT OUR WIKI WITHOUT WORRY OR CONCERN! If we don't like what you did, we can easily change it or revert it ... almost all edits result in an improvement, even if the edit kinda sucks

All fixed ... left to do: Look for instances of the word "tab" in the context of a chapter 'tab' (and not a MO GUI tab, which is correct). These should be replaced with the word 'chapter' or 'section' as appropriate. Feel free to take care of this piece, as that takes a bit more time than I have ATM.

All functionality is there, and the links should look like: Guide:Mod_Organizer#Chapter_NameThe longer name is a relic from the mock-up version. Since I moved the page leaving a redirect (see the top of the page when you follow that third link you posted), all links should work correctly; however, it is best to change all ... Guide:Mod_Organizer_TOC_Functionalityto ... Guide:Mod_OrganizerFeel free to do so if you want, but I will take care of it tomorrow if you don't. Actually, I will take care of the internal links, as I have some time now and can use a global replacement tool Thanks for pointing this out ... and feel free to check for any "#tab=" without the quotes. The old tab names may or may not be applicable, so you can deduce the correct chapter in the new guide and replace ... #tab=Chapterwith ... #ChapterJust be careful if you change anything so that all internal links remain functional ;) (changes can be reverted, but it could be confusing in the interim if anything gets mucked up)

Thanks! ... it is amazing what I just do not know! Sigs DO contain relevant info :D OK, sorry to digress.

At the risk of digressing, what is Modwat.ch? (just so I and everyone else knows, then back on topic :P )

NP ;) The Nexus is (again) having issues with these large files, so my updates are not available yet (Nexus virus scanner seems to be mucking up file size for large files and endlessly 'scanning' these without releasing them for download). I have updated the OP with links to my Copy share for download of the full versions.