z929669

Yeah but the recommendation said to install the SRO texture pack if SRO was installed... and that is what I think is wrong. Note should be corrected. Tech, can you confirm taht EDT2 is compatible with these meshes? If not (i.e., "seams are back"), then we need to notify Sparrow, because EDT2 are much better.

You do install the textures though, don't you? You install the SRO 512 textures. No. that note needs to be changed ... it would be good to have confirmation that EDT2 textures conflict, since I am not in a position to verify at the moment.

Keep in mind that Enhanced Distant Terrain 2 conflicts with these LOD textures and EDT2 is better. that is why we don't install these textures (including normals IIRC)

Actually, there are two other SRO torrents that combine all v1.6 1k and 2k textures into a simplified structure ... same thing effectively. Either way, it is always good to have multiple private sources.

Actually, I think we need to be parsing STEP:Extended out of the current Guide and placing it into a Pack. I advocate that we get to that point for 2.3.0 and that the core guide be an exhaustive approach to establishing the "Core Skyrim Base". Also, we need to keep mod-specific instructions and notes very general for now, as mods can be invoked by any Pack, and STEP instructions will not apply. We will need to determine how best to tie Pack-specific instructions to mods ... I am thinking that we can do this using subpages: wiki/Mod/ModVersion/Pack/PackVersion or something like that. For now, we should keep the instructions generally applicable and focus more on the guide instructions and text outside of the mod tables.

Pack interface has been significantly updated in terms of the buggy popup and the aesthetic presentation. Much more to do, but it should be significantly easier to get the job done now.

Calling all Editors! We need help (particularly from our more knowledgeable forum staff and member) editing the STEP Guide. There are many sections regarding ENB settings, graphics settings, tweaks, troubleshooting, etc that could use an update. Many of these sections are superseded by wiki Guides of their own, and we could simply be linking users to portions of those guides (or presenting brief instructions consistent with those guides). I have my hands full right now with lots of server and site-wide general maintenance, so help would be much appreciated. Let's give this thing another makeover, taking some instruction from Neo's Skyrim Revisited as well as Nearox's work on compatibility patches. Also, don't forget to address any of the useful info being collected in the official bug reports thread.

Regarding Extended: There are likely to be some significant changes to Extended down the road. Just FYI.

Wow. Lots going on on this thread ... thanks for fielding the questions, tech. We are still configuring the site and the server, so I have had little time but to skim and provide quick advice here and there. BTW, we did switch servers, and they were up very early Monday morning. Thins should be running smoothly by now.

Perhaps he has sped up the frame rate of the film?

Neo is already linking to these from his guide I think.

I am still working on a solution to aid in changing the modlist name. It breaks because the feferences to the original name don't get updated and nither does the page that the modlist sits on.

Looks good! thanks for doing that!

First, you create the pack page using the Form. At this time, you will define one or more mod list tables defined by the Pack. Each table can contain one or more mods; however, you cannot edit the mods within each table until the tables have been created, and this in turn depends on the Pack itself being created. Once this is done, the Pack page will have one or more buttons corresponding to each mod table defined during pack creation. these will say "Add Modlist" or "Edit Modlist" if it is new or being edited, respectively. Mods cannot be added in this way unless the corresponding mod pages have been created on the wiki (see Form:Mod to do that). you know if a mod page exists already if you see the mod available in the dropdown as you begin typing the mod name. If a mod does not seem to exist, it still may exist under a slight name variation, so do a search of the wiki (lower right) to be certain before creating the mod page. HTH

Sounds like a good process, but it takes time to do all the conversions and manage the resulting files ... at least when doing a lot of screens. My view is that if the original resolution is good (I assume that a screen at 1920x1200 res is about 1080p) and all compare shots are taken using identical conditions, then a simple Fraps JPG format is fine (almost all of my compares use this approach ... or PNG same way). This leaves only file move and renaming to be done if necessary. Using another app for conversion is a PITA, and I avoid it unless there is a good reason to do so.

NEVER edit templates... that affects every single Pack page. Use only the Forms to make your edits (Page Tools > Edit With form). I will take a look. EDIT: Please tell me how you arrived at the template page ... I want to prevent users from easily arriving at these pages.

Sounds like a good idea, but not for mod testing. I'll probably just have the testers capture in JPG. I have photoshop which will work excellent for conversion of my PNGs (imo, PNG captures the most factual image without any color/quality loss or changes), but I can't expect for all MTs to be able to do the same.And the size diff is huge. There is a tiny fraction of a noticeable diff between the two formats, color-wize, but not enough for the human eye to notice easily. JPEG does just fine in capturing the contrasts we need here ... we are not doing digital image analysis :P

Thanks Searcher. You are welcome to make edits to the wiki if you want, or simply post suggestions on the discussion page of the guide. Remember to add four tildes to the end of any comments you make in the guide itself if you have any, as this provides your username and timestamp ( ~~~~ )

Yeah, that is probably because this option uses a different kind of parallax that likely causes strange rendering with ENB parallax. The details may be posted earlier in this thread.

How does it compare to RWT?https://forum.step-project.com/showthread.php?tid=2239

Has anyone taken a look at the new gem holder in game?

Moving this thread to release development. (thanks for your interest in the area, Nearox ... if you stick to this with regard to STEP:Extended, we may just make you part of the dev staff ;) )

Why are you creating this here? You should be doing this by creating a Pack by the name of "VEGA" Please port this into that Pack page (I'll give you access to create packs), so please do that and truncate this post ;) EDIT: Looks like you have not ever logged onto the wiki. Time to do so if you want this work to survive!

Good solution for those wishing to install our recommendation

Yes, if you rename a mod list, then the existing reference no longer points to the valid mod list page. That page also needs to be moved. Mod list pages reside at: PackName/ModListName I will need to create a link to that in the SMW structure. For now, you can either avoid renaming then, rename then and try to figure ti all out (which is good too, as it helps you guys/gals understand the mechanism ;) ), or I will go in and tend to this stuff a bit later. FYI, These use cases will go along way to helping us work out the kinks later, so we really appreciate you guys pushing through this stuff and sticking with it!