SkyrimLE:ModList/Polish/2.2.1: Difference between revisions

From Step Mods | Change The Game
No edit summary
No edit summary
Line 75: Line 75:
# Wyjdź z menu opcji i kliknij "Play". Spowoduje to utworzenie niezbędnego pliku konfiguracyjnego i wpisów w rejestrze Windows, wymaganych przez niektóre z aplikacji opisanych w dalszej części poradnika. Wbrew powszechnemu mniemaniu uruchomienie gry nie jest wymagane do utworzenia plików INI.
# Wyjdź z menu opcji i kliknij "Play". Spowoduje to utworzenie niezbędnego pliku konfiguracyjnego i wpisów w rejestrze Windows, wymaganych przez niektóre z aplikacji opisanych w dalszej części poradnika. Wbrew powszechnemu mniemaniu uruchomienie gry nie jest wymagane do utworzenia plików INI.


== 1.C.  Ustawienia ekranu i karty graficznej.
== 1.C.  Ustawienia ekranu i karty graficznej. ==
=== 1.C.1.  Nvidia Users ===
=== 1.C.1.  Posiadacze kart Nvidia ===
# Download and install the [http://www.nvidia.it/Download/Find.aspx?lang=us latest Nvidia drivers] (beta if available).
# Pobierz i zainstaluj [http://www.nvidia.com/Download/Find.aspx?lang=us najnowsze sterowniki] (wersję beta, jeśli jest dostępna).
# Download [http://downloads.guru3d.com/NVIDIA-Inspector-1.9.6.6-download-2612.html Nvidia Inspector].
# Pobierz program [http://www.guru3d.com/files_details/nvidia_inspector_download.html Nvidia Inspector].
# Due to the variability of Nvidia configurations, Inspector settings are not recommended here, but see the [http://www.tomshardware.com/news/Elder-Scrolls-Skyrim-Nvidia-GeForce-Tweak-Guide,14211.html Tom's Hardware article] for helpful tips and links to relevant guides. Be certain to filter the potential options to accommodate the correct [[STEP:2.2.1#Performance.2C_Baseline_.26_Extreme_STEP|STEP configuration]].
# Przeczytaj [[Guide:NVIDIA_Inspector|Wiki Poradnik Nvidia Inspector Wiki]] (tylko w jęz. angielskim).


=== 1.C.2.  ATI Users ===
=== 1.C.2.  Posiadacze kart ATI ===
# Download and install the [http://support.amd.com/us/gpudownload/Pages/index.aspx latest AMD drivers] (beta if available).
# Pobierz i zainstaluj [http://support.amd.com/us/gpudownload/Pages/index.aspx najnowsze sterowniki] (wersję beta, jeśli jest dostępna).
# Open Catalyst Control Center, and click on the {{fc|#E6B69E|[Preferences]}} button in the upper rightSelect {{fc|#E6B69E|Advanced View}}.
# Uruchom Catalyst Control Center i kliknij przycisk {{fc|#E6B69E|[Preferences]}} w prawym górnym roguWybierz {{fc|#E6B69E|Advanced View}}.
# Under the {{fc|#E6B69E|Gaming}} section on the left select {{fc|#E6B69E|3D Application Settings}}.
# Po lewej stronie, w sekcji {{fc|#E6B69E|Gaming}} wybierz {{fc|#E6B69E|3D Application Settings}}.
#* Mirror the anti-aliasing and anisotropic filtering values set using the Skyrim Launcher above.
#* Ustaw anti-aliasing i anisotropic filtering tak samo jak w opcjach Skyrima powyżej.
#* Set [Tessellation] to {{fc|#E6B69E|AMD Optimized"
#* Ustaw [Tessellation] na {{fc|#E6B69E|AMD Optimized}}
#* Set [Catalyst A.I.] to highest texture quality and tick {{fc|#E6B69E|Enable Surface Format Optimization}}
#* Ustaw [Catalyst A.I.] na najwyższe ustawienia tekstur i zaznacz {{fc|#E6B69E|Enable Surface Format Optimization}}
#* Set [Wait for vertical refresh] to {{fc|#E6B69E|Quality}}  
#* Ustaw [Wait for vertical refresh] na {{fc|#E6B69E|Quality}}  
#* Set [Anti-Aliasing Mode] to {{fc|#E6B69E|Multi-sample AA}}
#* Ustaw [Anti-Aliasing Mode] na {{fc|#E6B69E|Multi-sample AA}}
#* Tick {{fc|#E6B69E|Triple buffering}} under [OpenGL Settings]
#* Zaznacz opcję {{fc|#E6B69E|Triple buffering}} w [OpenGL Settings]


=== 1.C.3.  Display ===
=== 1.C.3.  Ekran ===
Configure the monitor's display settings using Windows Display configuration utility (Control Panel > Display > Calibrate Color).  
Skonfiguruj ustawienia ekranu monitora używając narzędzia Windowsa.  
* First use the monitor's built-in configuration to attempt to complete the wizard. (ignore the ClearType tuner process)
* Najpierw użyj jednego z wbudpwanych ustaweń konfiguracyjnych
* Repeat the calibration wizard using the GPU's driver configuration settings.
* Następnie powtórz proces kalibracji przy użyciu narzędzi dostępnych z poziomu sterownika karty graficznej
* For each run, be certain to execute all calibrators with particular attention to gamma, brightness and contrast. Most users' monitor output will be significantly darker and slightly more color-saturated.
* Za każdem uruchom wszystkie opje kalibrowania monitora, zwracając szczególną uwagę na ustawienia gamma, jasności i kontrastu.


== 1.D. Performance Benchmarking ==
== 1.D. Benchmark Wydajności ==
{{Fc|#E6B69E|The following procedure is very important in determining baseline performance and ultimately helps the STEP team to assess performance variation across a wide range of computer configurations. This ultimately allows the accurate prediction of performance requirements for the various versions of STEP to come. User contributions in this regard are highly valued and much appreciated!}} {{Fc|#DDD|Even more importantly, this routine should be used to assess the performance of the strict STEP versions as described [[STEP:2.2.1#Performance.2C_Baseline_.26_Extreme_STEP|above]].}} {{Fc|#FFF|Database-comparison benchmarks will be available as sufficient numbers of user-submitted data accumulate.}}
{{Fc|#E6B69E|Poniższa procedura jest bardzo ważna, jeśli chodzi o ustalenie podstawowej wydajności systemu, jak również bardzo pomocna dla ekipy projektu STEP w ustaleniu rozrzutu wydajności wśród użytkowników. Dane te pozwalają nam na dokładniejsze ustalenie wymagań dla przyszłych wersji STEP. Wkład użytkowników w benchmarki jest bardzo ceniony i ma dużą wagę dla jakości projektu!}}  


At this point ...
Następujące kroki powinny być jak dotąd zakończone:
* There should be a clean install of both Steam and Skyrim as recommended by the SIG ([[STEP:2.2.1#1.A_Install_Steam_.26_Skyrim|see above]]),  
* "Czysta"  instalacja aplikacji STEAM oraz Skyrima,  
* the baseline INI settings should be configured (via the Skyrim Launcher), and
* Podstawowa konfiguracja opcji gry, wygerenowane pliki INI,
* the monitor and video-driver configurations should be optimized.  
* Konfiguracja karty graficznej oraz kalibracja monitora.  
This is a perfect point to collect some baseline performance data, as all tweaks after this section are manual and could have significant performance impact on some systems. A baseline benchmark provides valuable information about the setup and the gaming environment. Detecting driver issues, software incompatibilities, hardware problems or other issues is essential while the build is simple, as these kinds of problems are much more difficult to diagnose and solve as the build becomes more complex. It is recommended that users execute the following process again after the INI edits following are applied and after each sequence of potentially-impactful changes is introduced.<br />  
 
Jest to idealny wręcz moment na zebranie podstawowych danych dotyczących wydajności, jeśli chodzi o Skyrima. Wszelkie kolejne zmiany konfiguracyjne będą wprowadzane ręcznie. Zmiany te mogą mieć znaczący wpływ na wydajność naszego systemu. Ten pierwszy, podstawowy benchmark pozwoli zebrać cenne informacje na temat ustawień i środowiska gry. Najlepszy czas na wykrycie wszelkich problemów ze sterownikami, niekompatybilnych aplikacji, problemów ze sprzętem oraz innych defektów jest teraz, kiedy gra jest jeszcze niezmodowana, ponieważ tego typu problemy będą znacznie trudniejsze do zidentyfikowania w późniejszej fazie, kiedy zaczniemy instalować nasze modyfikacje. Zaleca się, aby użytkownik wykonał poniższe kroki za każdym razem, kiedy zmieniane są pliki konfiguracyjne INI oraz po ukończeniu instalacji modów z każdej sekcji poradnika STEP. <br />  


{{Fc|White|Points during setup that benchmarking is suggested will be indicated by:}}<br />
{{Fc|White|Points during setup that benchmarking is suggested will be indicated by:}}<br />
Line 112: Line 113:


# Identify any unnecessary background programs that may be running. Most importantly, determine if it is possible to set any anti-virus/spyware to low priority or "game mode". Any running background processes will consume some proportion of resources that Skyrim could otherwise use and increase the chances for instability. It is fine to have processes running in the background, but it is a good idea to be aware of what they are for troubleshooting in case there are problems.
# Identify any unnecessary background programs that may be running. Most importantly, determine if it is possible to set any anti-virus/spyware to low priority or "game mode". Any running background processes will consume some proportion of resources that Skyrim could otherwise use and increase the chances for instability. It is fine to have processes running in the background, but it is a good idea to be aware of what they are for troubleshooting in case there are problems.
# If mods were recently installed and IF NOT USING a SSD, defragment the game HDD. This will prevent game stutter caused by i/o inefficiencies (the effects are real!).
# Launch [http://www.fraps.com/download.php Fraps] in order to measure FPS. Set to output FPS to a log file.
# Launch [http://www.fraps.com/download.php Fraps] in order to measure FPS. Set to output FPS to a log file.
# Launch [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-z] in order to measure GPU and system memory-usage statistics. Set GPU-z to output the following to the log file (Sensors > Log to File; each variable log can be toggled by selecting the corresponding drop-downs):
# Launch [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-z] in order to measure GPU and system memory-usage statistics. Set GPU-z to output the following to the log file (Sensors > Log to File; each variable log can be toggled by selecting the corresponding drop-downs):
Line 121: Line 123:
# Launch Skyrim, and start a new game. Once loaded and the sound starts and the FPS counter appears, hit the FRAPS benchmark hotkey (F11 by default).
# Launch Skyrim, and start a new game. Once loaded and the sound starts and the FPS counter appears, hit the FRAPS benchmark hotkey (F11 by default).
# Let the game progress up to the first autosave just after jumping down off the cart, and press the FRAPS benchmark hotkey again to stop benchmarking. Total time since first depressing the benchmark hotkey will be approximately 240 seconds.
# Let the game progress up to the first autosave just after jumping down off the cart, and press the FRAPS benchmark hotkey again to stop benchmarking. Total time since first depressing the benchmark hotkey will be approximately 240 seconds.
# Quit the game and go to the GPU-z log. Identify the point in the log where the GPU Core Clock first maxes out and find the point beyond which the GPU Load values and the Dedicated Memory max and become fairly consistent (it should be around 10-40 rows from the top of the file). Delete all preceding rows (keep the header row!).
# Quit the game as quickly as possible and immediately exit the GPU-z app to stop logging.
# Move down to the end of the file and locate the point at which the GPU Load and Dedicated Memory begin to recede again (signifying loading the menue and quitting the game). Delete all rows after this point. The GPU-z log file is now trimmed of noisy data.
# Go to the GPU-z log. Identify the point in the log where the GPU Core Clock first maxes out and find the point beyond which the GPU Load values and the Dedicated Memory max and become fairly consistent (it should be between 50-90 rows from the top of the file). Delete all preceding rows (keep the header row!).
# Move down to the end of the file and locate the point at which the GPU Load and Dedicated Memory begin to recede again (signifying loading the menue and quitting the game, usually 20-40 rows of data, depending on how much time is spent in the menu and actually shutting down the game and quitting GPU-z). Delete all rows after this point. The GPU-z log file is now trimmed of "noisy" data.
# There are many ways to do this, but get GPU-z log data into a spreadsheet program and calculate the mean and standard deviation for:
# There are many ways to do this, but get GPU-z log data into a spreadsheet program and calculate the mean and standard deviation for:
#* GPU Load
#* GPU Load
Line 130: Line 133:
# Open the Fraps FPS log, and copy that column into the GPU-z spreadsheet.  
# Open the Fraps FPS log, and copy that column into the GPU-z spreadsheet.  
# Download [https://dl.dropbox.com/u/45644759/STEP/STEP_Bench1_z929669.xlsx '''this example spreadsheet'''] as an actual working example.
# Download [https://dl.dropbox.com/u/45644759/STEP/STEP_Bench1_z929669.xlsx '''this example spreadsheet'''] as an actual working example.
 
# As can be seen in the example spreadsheet, there are several columns and 200+ rows of data. The relevant summary statistics are the mean (i.e., average) and the standard deviation (i.e., a measure of the variation about the mean). These can be calculated for each column of data by using the following formulas in Excel or most other spreadheets (cell ranges are in parentheses):
<pre>
=AVERAGE(A2:A240)
=STDEV(A2:A240)
</pre>
:: [[Image:Bench.JPG|thumb|150px|left|Example benchmarks]]
{{clear}}
'''Example benchmark results:'''<br>
: [[User:Kelmych/Benchmark_Testing|Kelmych]]<br>
: [[User:Techangel85/Benchmarks|techangel85]]<br>
: [[User:Z929669/Benchmarks|z929669]]
{{Notice Small|{{Fc|#E6B69E|The STEP team would very much like to collect this data in addition to the related system specs system specs of each system used to obtain it (See [[STEP:2.2.1#Baseline_System|format above]]).}}}}
{{Notice Small|{{Fc|#E6B69E|The STEP team would very much like to collect this data in addition to the related system specs system specs of each system used to obtain it (See [[STEP:2.2.1#Baseline_System|format above]]).}}}}


== 1.E.  Install Utilities ==
== 1.E.  Install Utilities ==
=== 1.E.2.  Better Oblivion Sorting Software ===
=== 1.E.2.  Better Oblivion Sorting Software ===
[http://code.google.com/p/better-oblivion-sorting-software/ Better Oblivion Sorting Software] (BOSS) is the recommended utility for managing mod plugins for Skyrim and is compatible with most mod managers. Download BOSS and install according to the instructions provided by the author.
[http://code.google.com/p/better-oblivion-sorting-software/ Better Oblivion Sorting Software] (BOSS) is an essential utility for managing mod plugins for Skyrim.  Specifically, BOSS ensures proper mod order and Bash Tags, and it also identifies plugins (ESPs/ESMs) that need cleaning or other special treatment (more on this below). Download BOSS and install according to the instructions provided by the author.


=== 1.E.3.  BOSS Userlist Manager ===
=== 1.E.3.  BOSS Userlist Manager ===
Line 153: Line 166:
{{Warning Small|The Nexus Mod Manager (NMM) is no longer supported by STEP. The reason is that NMM does not allow the necessary level of control required by the STEP installation process. More importantly, NMM can *break* the STEP installation due to its lack of several controls related to mod overwrites and incomplete install/uninstall in some cases. }}
{{Warning Small|The Nexus Mod Manager (NMM) is no longer supported by STEP. The reason is that NMM does not allow the necessary level of control required by the STEP installation process. More importantly, NMM can *break* the STEP installation due to its lack of several controls related to mod overwrites and incomplete install/uninstall in some cases. }}


:: Nexus Mod Manager (NMM) is a mod-management utility from Blacktree Gaming, the owners of the Nexus sites, and provides a convenient download manager, and mod tracker.  The [http://justpaste.it/ms0 Nexus Mod Manager (NMM) Guide] By TheStigma provides good instructions for using this tool.
=== 1.E.5.  TES5Edit ===
[http://skyrim.nexusmods.com/mods/25859 TES5Edit] is a utility that can be used to 'fix' plugins in order to prevent problems during gameplay. The potential for incompatibilities, CTDs and other issues increases as the mod load increases. Thus, it is inevitably necessary to do some basic cleaning of a few mod plugins that BOSS identifies.  The process for cleaning mods can be found [[TES5Edit#Mod Cleaning|here]].


== 1.F.  INI Tweaks ==
== 1.F.  INI Tweaks ==
INI files can be used to managed many aspects of the game and also ancillary mods to Skyrim. Following are relevant tweaks that apply to Baseline STEP.  Performance STEP may require that some of the following settings be relaxed, and Extreme STEP settings can be further enhanced in some cases. Potential performance impact is indicated for each tweak.  
INI files can be used to managed many aspects of the game and also ancillary mods to Skyrim. Following are relevant tweaks that apply to Baseline STEP.  Performance STEP may require that some of the following settings be relaxed, and Extreme STEP settings can be further enhanced in some cases. Potential performance impact is indicated for each tweak.  


Go to "''Documents/My Games/Skyrim''" or "''My Documents/My Games/Skyrim''" (depending on Operating System) and find {{fc|#E6B69E|Skyrim.ini}} and {{fc|#E6B69E|SkyrimPref.ini}}. Make a backup of the files.  If using Mod Organizer, editing INI files is done by clicking {{fc|#E6B69E|'''[Edit Ini]'''}}. Wrye Bash users can edit and manage all INI files via the INI Tweaks tab.
The Skyrim INI files are located in "''Documents/My Games/Skyrim''" or "''My Documents/My Games/Skyrim''," depending on Operating System. At this point, the default INI files should have been established due to actions completed in [[STEP:2.2.1#1.B._Skyrim_Launcher_Options| step 1.B]], and {{Fc|white|the following tweaks assume that the Skyrim INI files are not already customized in any way}}. If using Mod Organizer, editing INI files is done by clicking {{fc|#E6B69E|'''[Edit Ini]'''}}. Wrye Bash users can edit and manage all INI files via the INI Tweaks tab.


{{Notice Small|Changing settings in the Skyrim Launcher can undo some of the below INI tweaks.  To avoid this, make sure to [http://windows.microsoft.com/en-US/windows7/Prevent-changes-to-a-file-by-setting-it-to-read-only set the INI files as "read only"] when all the tweaks are in place.  }}
{{Notice Small|Changing settings in the Skyrim Launcher can undo some of the below INI tweaks.  To avoid this, make sure to [http://windows.microsoft.com/en-US/windows7/Prevent-changes-to-a-file-by-setting-it-to-read-only set the INI files as "read only"] when all the tweaks are in place.  }}
Line 234: Line 248:
: ''Disables the annoying intro sequence.''
: ''Disables the annoying intro sequence.''
<pre>
<pre>
sIntroSequence=DISABLED.BIK
sIntroSequence=
</pre>
</pre>


Line 264: Line 278:
'''{{Fs|1.3em|Modify the following values under {{fc|white|[Display]}}:}}'''
'''{{Fs|1.3em|Modify the following values under {{fc|white|[Display]}}:}}'''


: ''Valid values range from 0 - 7. Lower values will sharpen shadows (not the resolution), making vegetation more "vibrant."  It gives a subtle increase in performance, but also gives more pixelated and striping effects to shadows.  Higher values will make shadows softer and more blurred. Consider a value of zero if using ENB.''
: ''Valid values range from 0 - 7. Lower values will sharpen shadows (not the resolution), making vegetation more "vibrant."  It gives a subtle increase in performance, but also gives more pixelated and striping effects to shadows.  Higher values will make shadows softer and more blurred. Consider a value of two if using ENB.''
<pre>
<pre>
iBlurDeferredShadowMask=2
iBlurDeferredShadowMask=3
</pre>
</pre>


Line 313: Line 327:
# [[Guide:Skyrim_Installation|Skyrim Installation Guide]] (SIG) – Comprehensive installation and configuration guide to Skyrim and its DLCs, mods, extensions, and utilities.
# [[Guide:Skyrim_Installation|Skyrim Installation Guide]] (SIG) – Comprehensive installation and configuration guide to Skyrim and its DLCs, mods, extensions, and utilities.
# [[Guide:Wrye_Bash|Wrye Bash Guide]] (WBG) – A practical, hands-on introduction to Wrye Bash using STEP as a working example.
# [[Guide:Wrye_Bash|Wrye Bash Guide]] (WBG) – A practical, hands-on introduction to Wrye Bash using STEP as a working example.
# [[Guide:Troubleshooting|Mod Organizer Guide]] (MOG) – A WIP with some advice and troubleshooting suggestions.
# [[Guide:Mod Organizer|Mod Organizer Guide]] (MOG) – A WIP with some advice and troubleshooting suggestions.
<br />
<br />


= Final Notes =
= Final Notes =
<div style="color:rgb(225,225,245); text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">A Final Consideration</div>
<div style="color:#ccc; text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">A Final Consideration</div>
Install mods in the order that they are presented in the following tables in order to achieve an aesthetically and mechanically well-vetted result. More experienced or adventurous modders may want to use STEP as a loose guide.
Install mods in the order that they are presented in the following tables in order to achieve an aesthetically and mechanically well-vetted result. More experienced or adventurous modders may want to use STEP as a loose guide.


Line 333: Line 347:


= STEP 2 =
= STEP 2 =
<div style="color:rgb(225,225,245); text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Mod Installation</div>
<div style="color:#ccc; text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Mod Installation</div>
<br />
<br />


Line 340: Line 354:
! '''Mod Name'''
! '''Mod Name'''
! '''Baseline'''
! '''Baseline'''
! '''Performance Options'''
! '''Quality Options'''
! '''DLC Required'''
! '''DLC Required'''
! '''Notes'''
! '''Notes'''
|-
|-
! class="core" |
! class="core" |
| style="width: 20%" | {{fc|#709ECA|<u>Mod Name</u>}}<sup>[[File:Wikilink.png|20px]]</sup>
| style="width: 20%" | [[Main Page|Mod Name]]<sup>[[File:Wikilink.png|20px]]</sup>
| style="width: 10%; text-align:center;" | Baseline
| style="width: 10%; text-align:center;" | Baseline
| style="width: 5%; text-align:center;" | [[File:Both Version.png]]
| style="width:72px; padding:4px 6px 0px;" | <span style="float:left;">[[File:LowQuality.png|32px]]</span> <span style="float:right;">[[File:HighQuality.png|32px]]</span>
| class="dlc" style="width: 8%; text-align:center;" | {{Fc|#99DD66|DG}}
| class="dlc" style="width: 8%; text-align:center;" | [[File:Dawnguard.png|22px]]
| Notes
| Notes
|}
|}


{| valign="middle" style="width: 70%; background-color: transparent; float:center; position:relative; margin:auto;"
{| valign="middle" style="width: 70%; background-color: transparent; float:center; position:relative; margin:auto;"
! style="background-color:#6B7E40; border-bottom: 1px solid #666C71; border-top: 1px solid #666C71; width: 7px; padding: 0;" |  
! style="background-color:#6B7E40; border-bottom: 1px solid #666C71; border-top: 1px solid #666C71; width: 4px; padding: 0;" |  
| style="border-bottom: 1px solid #666C71; border-top: 1px solid #666C71;;" | Core Mod
| style="border-bottom: 1px solid #666C71; border-top: 1px solid #666C71;" | Core Mod
| style="border-bottom: 1px solid #666C71; border-top: 1px solid #666C71;" | Core mods are indicated by the presence of a green vertical bar in the row at the immediate left-hand column of the table.
| style="border-bottom: 1px solid #666C71; border-top: 1px solid #666C71;" | Core mods are indicated by the presence of a green vertical bar in the row at the immediate left-hand column of the table.
|-
|-
Line 367: Line 381:
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" | Baseline
| style="border-bottom: 1px solid #666C71;" | Baseline
| style="border-bottom: 1px solid #666C71;" | This notes the STEP Baseline version or option of the corresponding mod.
| style="border-bottom: 1px solid #666C71;" | This notes the STEP Baseline version or option of the corresponding mod, and usually only refers to graphical quality choices.  Stylistic or mechanical suggestions are located in the "''Notes''" section.
|-
|-
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" | Performance Options
| style="border-bottom: 1px solid #666C71;" | Quality Options
| style="border-bottom: 1px solid #666C71;" | Indicates if there are performance-friendly or performance-unfriendly versions of the mod ''relative to the Baseline recommendation'':
| style="border-bottom: 1px solid #666C71;" | Indicates if there are performance-friendly or performance-unfriendly versions of the mod ''relative to the Baseline recommendation'':
|-
|-
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" | &nbsp;&nbsp;[[File:Performance Version.png|16px]] &nbsp;&nbsp;'''''Relative to Baseline''''', a lower quality, less demanding version of the mod is also available.
| style="border-bottom: 1px solid #666C71;" | &nbsp;[[File:LowQuality.png|18px]] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''''Relative to Baseline''''', a lower quality, less demanding version of the mod is also available.
|-
|-
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" | &nbsp;&nbsp;[[File:Quality Version.png|16px]] &nbsp;&nbsp;'''''Relative to Baseline''''', a higher quality, more demanding version of the mod is also available.
| style="border-bottom: 1px solid #666C71;" | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[File:HighQuality.png|18px]] &nbsp;'''''Relative to Baseline''''', a higher quality, more demanding version of the mod is also available.
|-
|-
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" | &nbsp;&nbsp;[[File:Both Version.png]] &nbsp;&nbsp;'''''Relative to Baseline''''', both lower and higher quality versions of the mod are available.
| style="border-bottom: 1px solid #666C71;" | &nbsp;[[File:LowQuality.png|18px]] [[File:HighQuality.png|18px]] &nbsp;'''''Relative to Baseline''''', both lower and higher quality versions of the mod are available.
|-
|-
| style="border-bottom: 1px solid #666C71;" |  
| style="border-bottom: 1px solid #666C71;" |  
Line 394: Line 408:
|}
|}
<br />
<br />
{{Notice|size=80|Mods should be installed in the order that they are listed to ensure that mods further down the list overwrite those occurring before them. This is necessary to ensure the desired in-game effect. Mods are otherwise listed in alphabetical order within each section, and any deviations from this are purposeful to achieve the desired outcome. {{Fc|White|Those new to modding should install mods explicitly according to the list order.}}
{{Notice|size=80|Consider the following while installing mods:
* {{Fc|#e6b69e|If there are not any notes associated with a particular mod, then all options fit the STEP mandate. The notes only provide instructions where necessary; otherwise, STEP encourages user customization.}}
* {{Fc|#e6b69e|Mods should be installed in the order that they are listed to ensure that mods further down the list overwrite those occurring before them. This is necessary to ensure the desired in-game effect. Mods are otherwise listed in alphabetical order within each section, and any deviations from this are purposeful to achieve the desired outcome.}}
* For experienced modders wishing to maximize their control over a customized outcome that deviates from STEP, “Loose files” (non-BSA) versions of mods should be used.  If a "loose files" version is not available, extract the BSA as described [[Guide:BSA Extraction|here]].}}
* {{Fc|#96b6ce|To achieve the best results, “Loose files” (non-BSA) versions of mods should be used.  If a "loose files" version is not available, extract the BSA as described [[Guide:BSA Extraction and Optimization|here]].}}
* {{Fc|#e6b69e|Always install plugins (ESPs/ESMs) unless otherwise noted. If there are not any notes associated with a particular mod, then all options fit the STEP mandate. The notes only provide instructions where necessary; otherwise, STEP encourages user customization.}}
* {{Fc|#96b6ce|Unless otherwise stated, follow BOSS's advice with regards to mod cleaning.}}
}}


== 2.A  {{#show:Category:ModSection_A|?SectionLabel}} ==
== 2.A. {{#show:Category:ModSection_A|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_A|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_A|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 413: Line 430:
}}
}}


== 2.B  {{#show:Category:ModSection_B|?SectionLabel}} ==
== 2.B. {{#show:Category:ModSection_B|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_B|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_B|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 428: Line 445:
}}
}}


== 2.C  {{#show:Category:ModSection_C|?SectionLabel}} ==
== 2.C. {{#show:Category:ModSection_C|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_C|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_C|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 443: Line 460:
}}
}}


== 2.D  {{#show:Category:ModSection_D|?SectionLabel}} ==
== 2.D. {{#show:Category:ModSection_D|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_D|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_D|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 457: Line 474:
}}
}}
}}
}}
{{Benchmark}}


== 2.E  {{#show:Category:ModSection_E|?SectionLabel}} ==
== 2.E. {{#show:Category:ModSection_E|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_E|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_E|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 472: Line 490:
}}
}}
}}
}}
{{Benchmark}}


== 2.F  {{#show:Category:ModSection_F|?SectionLabel}} ==
== 2.F. {{#show:Category:ModSection_F|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_F|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_F|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 489: Line 508:
{{Benchmark}}
{{Benchmark}}


== 2.G  {{#show:Category:ModSection_G|?SectionLabel}} ==
== 2.G. {{#show:Category:ModSection_G|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_G|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_G|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 503: Line 522:
}}
}}
}}
}}
{{Benchmark}}


== 2.H  {{#show:Category:ModSection_H|?SectionLabel}} ==
== 2.H. {{#show:Category:ModSection_H|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_H|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_H|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 518: Line 538:
}}
}}
}}
}}
{{Benchmark}}


== 2.I  {{#show:Category:ModSection_I|?SectionLabel}} ==
== 2.I. {{#show:Category:ModSection_I|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_I|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_I|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 533: Line 554:
}}
}}
}}
}}
{{Benchmark}}


== 2.J  {{#show:Category:ModSection_J|?SectionLabel}} ==
== 2.J. {{#show:Category:ModSection_J|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_J|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_J|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 548: Line 570:
}}
}}
}}
}}
{{Benchmark}}


== 2.K  {{#show:Category:ModSection_K|?SectionLabel}} ==
== 2.K. {{#show:Category:ModSection_K|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_K|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_K|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 563: Line 586:
}}
}}
}}
}}
{{Benchmark}}


== 2.L  {{#show:Category:ModSection_L|?SectionLabel}} ==
== 2.L. {{#show:Category:ModSection_L|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_L|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_L|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 578: Line 602:
}}
}}
}}
}}
{{Benchmark}}


== 2.M  {{#show:Category:ModSection_M|?SectionLabel}} ==
== 2.M. {{#show:Category:ModSection_M|?SectionLabel}} ==
:{{Fc|#E6B69E|{{#show:Category:ModSection_M|?SectionDescription}} }}
:{{Fc|#E6B69E|{{#show:Category:ModSection_M|?SectionDescription}} }}
{{ModTable|ModTableRow=
{{ModTable|ModTableRow=
Line 603: Line 628:


= STEP 3 =
= STEP 3 =
<div style="color:rgb(225,225,245); text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Tips & Troubleshooting Common Issues</div>
<div style="color:#ccc; text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Tips & Troubleshooting Common Issues</div>


== 3.A.  Technical Tips ==
== 3.A.  Technical Tips ==
Line 628: Line 653:


=== 3.A.3.  Defrag the Hard Drive ===
=== 3.A.3.  Defrag the Hard Drive ===
For hard drives (<u>not SSDs</u>), this is a very important task once most/all mods are installed.  The Windows defrag utility may be used, but it is sub-standard.  A couple of the best free utilities are [http://www.auslogics.com/en/software/disk-defrag/ Auslogics Disk Defrag] and [http://www.puransoftware.com/Puran-Defrag-Download.html Puran Defrag Free Edition].  <u>'''Do NOT defrag an SSD as it will detrimentally affect its lifetime'''</u>.
For hard drives (<u>not SSDs</u>), this is a very important task once most/all mods are installed.  The Windows defrag utility may be used, but it is sub-standard.  A couple of the best free utilities are [http://www.piriform.com/defraggler Defraggler] and [http://www.auslogics.com/en/software/disk-defrag/ Auslogics Disk Defrag].  <u>'''Do NOT defrag an SSD as it will detrimentally affect its lifetime'''</u>.


=== 3.A.4.  Semi-Invisible People & Misbehaving Walls ===
=== 3.A.4.  Semi-Invisible People & Misbehaving Walls ===
Line 662: Line 687:


= User Contributions =
= User Contributions =
<div style="color:rgb(225,225,245); text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">How YOU Can Help</div>
<div style="color:#ccc; text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">How YOU Can Help</div>


STEP can only get bigger and better with help from the user community.  Even simply maintaining the current STEP is too much work for the core STEP team to ensure that the highest quality is maintained.  We need people to help us identify mods that are thought to improve Skyrim while adhering to the [[#STEP Mandate|STEP Mandate]].  We also need ongoing reviews and updates on mods that may be causing problems or that stray from the STEP philosophy.  Finally, we need help from the community in terms of testing, benchmarking and analysis. More detail is presented in the [[Guide:Mod Testing|Mod Testing Guide]].   
STEP can only get bigger and better with help from the user community.  Even simply maintaining the current STEP is too much work for the core STEP team to ensure that the highest quality is maintained.  We need people to help us identify mods that are thought to improve Skyrim while adhering to the [[#STEP Mandate|STEP Mandate]].  We also need ongoing reviews and updates on mods that may be causing problems or that stray from the STEP philosophy.  Finally, we need help from the community in terms of testing, benchmarking and analysis. More detail is presented in the [[Guide:Mod Testing|Mod Testing Guide]].   
Line 680: Line 705:
* The STEP beta testers ... for their good humor and rigorous analyses
* The STEP beta testers ... for their good humor and rigorous analyses
* The Nexus community  
* The Nexus community  
* Bealdwine, EisDrache & MontyMM - site founders on indefinite leave (we hope you guys are well!)
* Bealdwine, EisDrache & MontyMM - site founders on indefinite leave (we hope you guys are well!) --UPDATE: MontyMM is back ... welcome back!
* Outstanding v2.2.1 contributors - Techangel85, Neovalen, rpsgc, Besidilo, JudgementJay, torminater, Kelmych, Korentin & Mothergoose729
* Outstanding v2.2.1 contributors - Techangel85, Neovalen, rpsgc, Besidilo, JudgementJay, torminater, Kelmych, Korentin & Mothergoose729
* Bethesda Softworks for Skyrim (and TES in general)
* Bethesda Softworks for Skyrim (and TES in general)
<br />
 
==== Site Donors ====
We have had a handful of generous user donations to keep this site alive anviable. Most of these donors have not left their user names, so they shall remain anonymous; however, the following are site contributors that have generously given a bit of their livelihood in support of STEP. For that, we thank them immensely!
* '''solist''' (our most generous contributor)
* geeee785
* 16 additional generous contributors that shall remain anonymous until their user names are made known to us.
 
 
====== The core STEP team is: ======
====== The core STEP team is: ======
* Farlo - Mediawiki developer & extraordinaire, Mod-list co-compiler, forums admin, site founder
* Farlo - Mediawiki developer & extraordinaire, Mod-list co-compiler, forums admin, site founder

Revision as of 14:04, March 22, 2013

Warning-Logo.png

WARNING

This guide is out of date and is NOT supported! It may contain information that is incorrect or not in line with the current state of the game.
Go to the latest supported SkyrimLE Guide.

O projekcie STEP[edit | edit source]

Tytułem wstępu

STEP jest wyczerpującym i szeroko zakrojonym poradnikiem, który ma na celu uzupełnienie gry TES V: Skyrim o najlepsze modyfikacje (zwane potocznie modami) oraz optymalizację ustawień. Głównym założeniem projektu jest zachowanie wierności oryginalnej zawartości Skyrima, przy jednoczesnym wzbogaceniu wrażeń wizualnych i dźwiękowych oraz poprawieniu błędów w mechanice gry.

Autorem projektu jest TheCompiler, całość jest jednak pracą zbiorową, powstałą przy udziale społeczności modderskiej, ochotników posiadających wiedzę techniczną oraz administratorów projektu. Celem STEP-a jest zapewnienie sprawdzonych i przetestowanych metod, które pozwolą na instalację i utrzymanie wzbogaconego o modyfikacje Skyrima. W poradniku przedstawiamy w sposób szczegółowy, jak zrobić z oryginalnej instalacji wzbogacony „szablon” czy też „podstawkę” gry, którą później można wykorzystać do instalacji kolejnych modów. Niedoświadczonym użytkownikom zalecamy dokładne stosowanie się do instrukcji "krok-po-kroku" zawartych w poradniku, natomiast bardziej zaawansowani gracze mogą użyć STEP-a jako ogólnych wytycznych do modowania swojej gry.

W celu zebrania informacji odpowiedniej jakości (czyli takich, które jak najlepiej spełnią oczekiwania użytkowników), zespół projektu STEP współpracuje ze społecznością modderów poprzez szczegółowe recenzje, opinie i sugestie wymieniane i omawiane wspólnie na Forum Społeczności STEP. Na forum obowiązuje regulamin, z którym należy się zapoznać (cała strona funkcjonuje wyłącznie w języku angielskim). Po rejestracji można się już cieszyć pełnym dostępem do wszelkich udostępnianych informacji, a w razie problemów - liczyć na chętną do pomocy ekipę. W celu porównania jak wygląda Skyrim przed i po instalacji STEP-a, możecie sprawdzić zrzuty ekranu na stronie Nexus, ale tak naprawdę jedyny sprawdzony sposób na doświadczenie, czym naprawdę jest STEP, to wypróbowanie go!

Ucieszymy się z każdego wsparcia finansowego Projektu STEP - datki przeznaczane są na utrzymanie serwera, domeny i zarządzanie projektem.


Wytyczne projektu STEP[edit | edit source]

Zobowiązania

Podstawą projektu jest wzbogacenie oryginalnej wersji gry Skyrim na komputery PC poprzez...

  • zamianę tekstur na lepsze, przy minimalnej utracie wydajności gry
  • konsekwentny i logiczny dobór modyfikacji graficznych i dźwiękowych w celu poprawienia klimatu rozgrywki
  • poprawienie komfortu UI i systemu menu
  • wybór modyfikacji naprawiających błędnie funkcjonujące aspekty mechaniki gry

Projekt NIE dotyczy modyfikacji, które...

  • wprowadzają zmiany sprzeczne z założeniami oryginalnej wersji gry oraz uniwersum The Elder Scrolls
  • wprowadzają do gry erotykę oraz podmieniają modele kobiecych postaci
  • podmieniają muzykę z oryginalnego produktu
  • diametralnie inegrują w sposób rozgrywki

STEP w wersjach Wydajnościowej, Podstawowej i Ekstremalnej[edit | edit source]

Projekt STEP oferuje 3 różne wersje. Instalacja modów oznaczonych jako "Core" (zielony pasek przy nazwie moda) jest niezbędne i wymagana do poprawnego funkcjonowania wszystkich trzech wersji STEP. Pozostałe mody nie są niezbędne, aczkolwiek Ekipa projektu STEP gorąco poleca ich instalację. Poszczególne wersje STEP zostały stworzone z myślą o wydajności, w zależności od możliwości komputera gracza:

Wersja Wydajnościowa: Jedynie mody oznaczone jako "Core". Wybór opcji wydajnościowej dla wszystkich modów.
Czyli: "Z litości nie będę katował procesora i karty graficznej, ale muszę mieć STEP!"
Wersja Podstawowa: Mody oznaczone jako "Core" oraz dowolne mody dodatkowe. Wybór opcji wydajnościowej lub średniej jakości, jeśli to tylko możliwe.
Czyli: "Mój komputer daje radę, ale nie zniosę, jeśli gra będzie się choć trochę zacinać!"
Wersja Ekstremalna: Wszystkie mody oznaczone jako "Core" oraz wszystkie mody dodatkowe. Wybór opcji oferujących najwyższą jakość, jeśli to możliwe.
Czyli: "Posiadam superkomputer!"


KROK 1[edit | edit source]

Konfiguracja przed instalacją

Wymagania[edit | edit source]

  • Oficjalny Patch v1.8
  • Cierpliwość i szczegółowe wykonywanie instrukcji krok-po-kroku

Template:Notice Small

System[edit | edit source]

Poradnik STEP został napisany z myślą o komputerach posiadającyh poniższe (lub porównywalne) parametry:

  • Windows 7
  • Intel i5/i7 quad core
  • 4+ GB pamięci RAM
  • Karta graficzne 1+ GB VRAM (DDR5)
  • Rozdzielczość ekranu: 1680x1050

Template:Notice Small

1.A. Instalacja platformy Steam oraz Skyrima[edit | edit source]

Niniejszy poradnik zakłada, że użytkownik zainstalował aplikację Steam zgodnie z Poradnikiem Instalacji Skyrima (chwilowo dostępny jedynie w wersji angielskiej). Zalecamy poświęcić trochę czasu na poprawną instalację i konfigurację zarówno platfortmy Steam jak i samego Skyrima, według instrukcji zawartych w poradniku.

UWAGA! Ważnym jest, żeby dalszą instalację STEP przeprowadzać na ŚWIEŻYM, NOWO ZAINSTALOWANYM SKYRIMIE! Ewentualnie można spróbować przywrócić Skyrima do podstawowej, świeżej wersji według tego poradnika (w jęz. angielskim).

UWAGA! Poradnik STEP przeznaczony jest do gry w wersji angielskiej. Autor tego tłumaczenia posiada grę właśnie w takiej wersji i nie gwarantuje, że Projekt STEP będzie w pełni funkcjonalny w polskiej wersji gry. Wiele z modów zawartych w poradniku podmienia opisy przedmiotów, ras itp. Autor tłumaczenia nie wie, jaki wpływ na polską wersję gry będą miały mody tego typu i nie bierze odpowiedzialności za wszelkie ewentualne problemy, które wynikną z tego tytułu.

1.B. Opcje Menu Startowego Skyrima[edit | edit source]

1.B.1. Ustawienia Menu Startowego[edit | edit source]

  1. Uruchom Skyrima przez aplikację Steam i kliknij na [Options (Opcje)]. Spowoduje to utworzenie plików konfiguracyjnych (tzw. pliki INI) i automatyczne ustawienie opcji gry zgodnie z wykrytym sprzętem. Powstaną również wpisy w Rejestrze Windowsa, które będą niezbędne do działania pomocniczych programów, niezbędnych w dalszej części poradnika.
  2. Kliknij przycik [Ultra].
  3. Antialiasing ustaw na 4. Różnica między 4 a 8 próbkami jest na bardzo subtelna i niewarta utraty wydajności, którą powoduje (zgodnie z Poradnikiem Tweakguides). W celu ostatecznej poprawy wydajności obniż wartość z 4 do 2. UWAGA: Jeśli używasz SMAA, ustaw Antialiasing na ZERO.
  4. Anisotropic Filtering (Filtrowanie Anizotropowe) ustaw na 16 (ustawienie na 8 nieznacznie poprawi wydajność gry).
  5. Kliknij przycisk[Advanced (Zaawansowane)] i upewnij się, że opcja FXAA jest ODZNACZONA. FXAA pogarsza efekt Filtrowania Anizotropowego, jak również ogólną jakość tekstur. Oferuje co prawda znaczący wzrost wydajność w stosunku to Antyaliasingu, ale widocznie zmniejsza jakość. UWAGA: SMAA jest nieco lepszą alternatywą dla FXAA.
    • Rozważ ustawienie jakości cieniowania na 'High' (Wysokie) zamiast na 'Ultra', jeśli masz kartę graficzną z mniej niż 1 GB VRAM (STEP w wersji Wydajnościowej) lub pozostaw ustawienie 'Ultra' dla wersji Ekstremanlen STEP.
    • Under [View Distance], make sure Object Detail Fade is UN-checked and adjust grass to 100% with all other settings around 50%.NOTE: High-end systems can handle max view distances just fine.
  6. Wyjdź z menu opcji i kliknij "Play". Spowoduje to utworzenie niezbędnego pliku konfiguracyjnego i wpisów w rejestrze Windows, wymaganych przez niektóre z aplikacji opisanych w dalszej części poradnika. Wbrew powszechnemu mniemaniu uruchomienie gry nie jest wymagane do utworzenia plików INI.

1.C. Ustawienia ekranu i karty graficznej.[edit | edit source]

1.C.1. Posiadacze kart Nvidia[edit | edit source]

  1. Pobierz i zainstaluj najnowsze sterowniki (wersję beta, jeśli jest dostępna).
  2. Pobierz program Nvidia Inspector.
  3. Przeczytaj Wiki Poradnik Nvidia Inspector Wiki (tylko w jęz. angielskim).

1.C.2. Posiadacze kart ATI[edit | edit source]

  1. Pobierz i zainstaluj najnowsze sterowniki (wersję beta, jeśli jest dostępna).
  2. Uruchom Catalyst Control Center i kliknij przycisk [Preferences] w prawym górnym rogu. Wybierz Advanced View.
  3. Po lewej stronie, w sekcji Gaming wybierz 3D Application Settings.
    • Ustaw anti-aliasing i anisotropic filtering tak samo jak w opcjach Skyrima powyżej.
    • Ustaw [Tessellation] na AMD Optimized
    • Ustaw [Catalyst A.I.] na najwyższe ustawienia tekstur i zaznacz Enable Surface Format Optimization
    • Ustaw [Wait for vertical refresh] na Quality
    • Ustaw [Anti-Aliasing Mode] na Multi-sample AA
    • Zaznacz opcję Triple buffering w [OpenGL Settings]

1.C.3. Ekran[edit | edit source]

Skonfiguruj ustawienia ekranu monitora używając narzędzia Windowsa.

  • Najpierw użyj jednego z wbudpwanych ustaweń konfiguracyjnych
  • Następnie powtórz proces kalibracji przy użyciu narzędzi dostępnych z poziomu sterownika karty graficznej
  • Za każdem uruchom wszystkie opje kalibrowania monitora, zwracając szczególną uwagę na ustawienia gamma, jasności i kontrastu.

1.D. Benchmark Wydajności[edit | edit source]

Poniższa procedura jest bardzo ważna, jeśli chodzi o ustalenie podstawowej wydajności systemu, jak również bardzo pomocna dla ekipy projektu STEP w ustaleniu rozrzutu wydajności wśród użytkowników. Dane te pozwalają nam na dokładniejsze ustalenie wymagań dla przyszłych wersji STEP. Wkład użytkowników w benchmarki jest bardzo ceniony i ma dużą wagę dla jakości projektu!

Następujące kroki powinny być jak dotąd zakończone:

  • "Czysta" instalacja aplikacji STEAM oraz Skyrima,
  • Podstawowa konfiguracja opcji gry, wygerenowane pliki INI,
  • Konfiguracja karty graficznej oraz kalibracja monitora.

Jest to idealny wręcz moment na zebranie podstawowych danych dotyczących wydajności, jeśli chodzi o Skyrima. Wszelkie kolejne zmiany konfiguracyjne będą wprowadzane ręcznie. Zmiany te mogą mieć znaczący wpływ na wydajność naszego systemu. Ten pierwszy, podstawowy benchmark pozwoli zebrać cenne informacje na temat ustawień i środowiska gry. Najlepszy czas na wykrycie wszelkich problemów ze sterownikami, niekompatybilnych aplikacji, problemów ze sprzętem oraz innych defektów jest teraz, kiedy gra jest jeszcze niezmodowana, ponieważ tego typu problemy będą znacznie trudniejsze do zidentyfikowania w późniejszej fazie, kiedy zaczniemy instalować nasze modyfikacje. Zaleca się, aby użytkownik wykonał poniższe kroki za każdym razem, kiedy zmieniane są pliki konfiguracyjne INI oraz po ukończeniu instalacji modów z każdej sekcji poradnika STEP.

Points during setup that benchmarking is suggested will be indicated by:

Benchmark32.png
Benchmark
Benchmark32.png


Use the following checklist to calculate the standard STEP benchmark:

  1. Identify any unnecessary background programs that may be running. Most importantly, determine if it is possible to set any anti-virus/spyware to low priority or "game mode". Any running background processes will consume some proportion of resources that Skyrim could otherwise use and increase the chances for instability. It is fine to have processes running in the background, but it is a good idea to be aware of what they are for troubleshooting in case there are problems.
  2. If mods were recently installed and IF NOT USING a SSD, defragment the game HDD. This will prevent game stutter caused by i/o inefficiencies (the effects are real!).
  3. Launch Fraps in order to measure FPS. Set to output FPS to a log file.
  4. Launch GPU-z in order to measure GPU and system memory-usage statistics. Set GPU-z to output the following to the log file (Sensors > Log to File; each variable log can be toggled by selecting the corresponding drop-downs):
    • GPU Core Clock (MHz)
    • GPU Temperature (°C)
    • GPU Load (%)
    • Memory Usage (Dedicated) - This is on-card-VRAM
    • Memory Usage (Dynamic) - This is the amount of VRAM transferred to much-slower system RAM
  5. Launch Skyrim, and start a new game. Once loaded and the sound starts and the FPS counter appears, hit the FRAPS benchmark hotkey (F11 by default).
  6. Let the game progress up to the first autosave just after jumping down off the cart, and press the FRAPS benchmark hotkey again to stop benchmarking. Total time since first depressing the benchmark hotkey will be approximately 240 seconds.
  7. Quit the game as quickly as possible and immediately exit the GPU-z app to stop logging.
  8. Go to the GPU-z log. Identify the point in the log where the GPU Core Clock first maxes out and find the point beyond which the GPU Load values and the Dedicated Memory max and become fairly consistent (it should be between 50-90 rows from the top of the file). Delete all preceding rows (keep the header row!).
  9. Move down to the end of the file and locate the point at which the GPU Load and Dedicated Memory begin to recede again (signifying loading the menue and quitting the game, usually 20-40 rows of data, depending on how much time is spent in the menu and actually shutting down the game and quitting GPU-z). Delete all rows after this point. The GPU-z log file is now trimmed of "noisy" data.
  10. There are many ways to do this, but get GPU-z log data into a spreadsheet program and calculate the mean and standard deviation for:
    • GPU Load
    • GPU Temperature
    • Memory Usage (Dedicated)
    • Memory Usage (Dynamic)
  11. Open the Fraps FPS log, and copy that column into the GPU-z spreadsheet.
  12. Download this example spreadsheet as an actual working example.
  13. As can be seen in the example spreadsheet, there are several columns and 200+ rows of data. The relevant summary statistics are the mean (i.e., average) and the standard deviation (i.e., a measure of the variation about the mean). These can be calculated for each column of data by using the following formulas in Excel or most other spreadheets (cell ranges are in parentheses):
 =AVERAGE(A2:A240)
 =STDEV(A2:A240)
Example benchmarks

Example benchmark results:

Kelmych
techangel85
z929669

Template:Notice Small

1.E. Install Utilities[edit | edit source]

1.E.2. Better Oblivion Sorting Software[edit | edit source]

Better Oblivion Sorting Software (BOSS) is an essential utility for managing mod plugins for Skyrim. Specifically, BOSS ensures proper mod order and Bash Tags, and it also identifies plugins (ESPs/ESMs) that need cleaning or other special treatment (more on this below). Download BOSS and install according to the instructions provided by the author.

1.E.3. BOSS Userlist Manager[edit | edit source]

Boss Userlist Manager (BUM) helps to make BOSS even easier by providing a GUI to edit the BOSS masterlist, which is used to define load order. Includes automated BOSS masterlist management and more.

1.E.4. Mod Manager(s)[edit | edit source]

There are several utilities that may be used to manage the STEP setup. Truth be told, mods can even be installed manually (not recommended). A mod-management utility is HIGHLY RECOMMENDED in order to keep track of a comlpex setup like STEP. These utilities also make it exponentially simpler to deconstruct a STEP install in order to update between versions. This is impossible to do simply or efficiently (or even correctly) otherwise.

  • Wrye Bash
Wrye Bash (WB) is perhaps the most powerful mod-management utility, and is full of features for both modders and advanced mod authors alike. A fairly comprehensive mod-maintenance process is presented in the Wrye Bash Guide and presented in a context that applies to STEP. Presently, Wrye Bash lacks a Nexus-compatible-mod-update management system, so this will need to be managed by the user. Mod updates are not necessary for STEP though, and it is HIGHLY RECOMMENDED that regular STEP users avoid updating single mods piecemeal. This is the kind of thing that the STEP mod testing team works on for upcoming releases, and troubleshooting issues related to mod updates takes resources away from supporting others that are using supported versions of mods. (The mod testers are specifically encouraged to use Wrye Bash as the preferred management utility to simplify information exchange, although MO is another option).
  • Mod Organizer
Mod Organizer (MO) is a feature-rich management utility that utilizes data virtualization to keep your Skyrim folder pristine. See the Mod Organizer Guide to learn more. MO does keep track of mod updates on the Nexus, and is as accurate as long as the Nexus metadata is current.
  • Nexus Mod Manager

Template:Warning Small

1.E.5. TES5Edit[edit | edit source]

TES5Edit is a utility that can be used to 'fix' plugins in order to prevent problems during gameplay. The potential for incompatibilities, CTDs and other issues increases as the mod load increases. Thus, it is inevitably necessary to do some basic cleaning of a few mod plugins that BOSS identifies. The process for cleaning mods can be found here.

1.F. INI Tweaks[edit | edit source]

INI files can be used to managed many aspects of the game and also ancillary mods to Skyrim. Following are relevant tweaks that apply to Baseline STEP. Performance STEP may require that some of the following settings be relaxed, and Extreme STEP settings can be further enhanced in some cases. Potential performance impact is indicated for each tweak.

The Skyrim INI files are located in "Documents/My Games/Skyrim" or "My Documents/My Games/Skyrim," depending on Operating System. At this point, the default INI files should have been established due to actions completed in step 1.B, and the following tweaks assume that the Skyrim INI files are not already customized in any way. If using Mod Organizer, editing INI files is done by clicking [Edit Ini]. Wrye Bash users can edit and manage all INI files via the INI Tweaks tab.

Template:Notice Small

1.F.1. Skyrim INI[edit | edit source]

Go to the bottom of the Skyrim.ini and create the following:

Increases the distance arrows fly. (From "Arrows and Bolts Tweaks").
[Actor]
fVisibleNavmeshMoveDist=12288.0000
Places the camera just above your character's head in third-person view, and correct the camera angle in third-person view while on horseback. (From "Third Person Horse Camera"). Provides instant camera-angle switching when switching view types or when mounting/dismounting your horse. (from "Instant Camera POV Switching").
[Camera]
fOverShoulderAddY=0.0
fOverShoulderPosZ=18.0
fOverShoulderPosX=0.0
fOverShoulderCombatAddY=0.0
fOverShoulderCombatPosZ=24.0
fOverShoulderCombatPosX=0.0

fOverShoulderHorseAddY=-72.0
fOverShoulderHorsePosZ=50.0
fOverShoulderHorsePosX=35.0
fActorFadeOutLimit=-100

fMouseWheelZoomSpeed=60.0
f1st3rdSwitchDelay=0.95
iHorseTransitionMillis=001
Speeds up the book opening animation, and move the HUD elements closer to the borders of the screen.:
[Interface]
fBookOpenTime=200.0

fSafeZoneX=10
fSafeZoneY=10
fSafeZoneXWide=10
fSafeZoneYWide=10

Add the following under [Combat]:

Shifts the point of aim to the center of the aiming reticule for arrows and crossbows (with this setting targets will be hit where the cursor is placed at approximately 100 feet from the target).
f1PArrowTiltUpAngle=0.7
f3PArrowTiltUpAngle=0.7
f1PBoltTiltUpAngle=0.7
f3PBoltTiltUpAngle=0.7

Add the following under [Display]:

Fixes the shadow flickering issue. Shadow flickering is caused by updating sun shadows.
fSunShadowUpdateTime=0
fSunUpdateThreshold=2.0
Increases the time that blood decals remain visible (tweak from “Enhanced Blood Textures” mod).
fDecalLifetime=512.0
Helps reduce Z-fighting, but may increase clipping, especially with a higher field of view. See Gopher's More Z-fighting video for more information and examples.
fNearDistance=18.0000

Add the following under [General]:

Disables the annoying intro sequence.
sIntroSequence=
Prevents crashes when loading into a large interior area.
iLargeIntRefCount=262144
Helps prevent lighting “pop-in” by pushing back the distance at which the flicker/pulse animation loops begin.
fFlickeringLightDistance=8192

1.F.2. SkyrimPrefs INI[edit | edit source]

Modify the following under [Controls]:

Disable mouse acceleration.
bMouseAcceleration=0

Add the following under [Decals]:

Enables higher resolution blood decals on NPCs.
bDecalsOnSkinnedGeometry=1

Modify the following values under [Display]:

Valid values range from 0 - 7. Lower values will sharpen shadows (not the resolution), making vegetation more "vibrant." It gives a subtle increase in performance, but also gives more pixelated and striping effects to shadows. Higher values will make shadows softer and more blurred. Consider a value of two if using ENB.
iBlurDeferredShadowMask=3
Enables shadows rendering on trees.
bTreesReceiveShadows=1
If running Extreme STEP using 'Ultra' setting for shadow shadow quality to in 1.B.1, this tweak will further improve shadow resolution at a performance cost. Consider also raising 'iShadowMapResolutionSecondary' to 4096 on high-end machines. For Performance or Baseline STEP, do not change the default values for either of these settings.
iShadowMapResolutionPrimary=4096
iShadowMapResolutionSecondary=2048
Improves the blood decals number per scene (from “Enhanced Blood Textures”).
iMaxDecalsPerFrame=256
ENB users ONLY! Enabling these without an ENB will decrease performance with no visual impact and possibly introduce excessive shadow striping.
bDrawLandShadows=1
bFloatPointRenderTarget=1

Modify the following under [TerrainManager]:

Helps reduce Z-fighting, but may increase clipping, especially with a higher field of view. See Gopher's More Z-fighting video for more information and examples.
fBlockMaximumDistance=500000
fBlockLevel1Distance=140000
fBlockLevel0Distance=75000
fSplitDistanceMult=4.0

Modify the following under [MAIN]:

Also helps reduce Z-fighting. See Gopher's More Z-fighting video for more information and examples.
fSkyCellRefFadeDistance=500000.0000
Benchmark32.png
Benchmark
Benchmark32.png


Reminder - Essential Guides[edit | edit source]

The following guides form the base from which STEP builds and provide details on many of the topics mentioned in this Guide.

  1. Skyrim Installation Guide (SIG) – Comprehensive installation and configuration guide to Skyrim and its DLCs, mods, extensions, and utilities.
  2. Wrye Bash Guide (WBG) – A practical, hands-on introduction to Wrye Bash using STEP as a working example.
  3. Mod Organizer Guide (MOG) – A WIP with some advice and troubleshooting suggestions.


Final Notes[edit | edit source]

A Final Consideration

Install mods in the order that they are presented in the following tables in order to achieve an aesthetically and mechanically well-vetted result. More experienced or adventurous modders may want to use STEP as a loose guide.

Information from certain mods used can write additional information into save games. Thus, some mods can continue to affect the game even after the mods are removed or updated.

From the Bethesda document, Skyrim Mod Troubleshooting: Best Practices:

"When you play Skyrim with a mod, in most cases, the new data for the mod will be written into any new saved games you create. For example, if you play Skyrim with Mod X and create a save, the next time you load that save, the game will expect Mod X to also be loaded. If you no longer want to play Skyrim with Mod X, it is best to unload Mod X (by unchecking the plugin under Data Files in your Skyrim launcher) and loading a save that does not require Mod X, usually an older save or a backed up save."

The short version is “Never continue with a save once a mod it relies upon has been removed.” Although this is good advice, there may be occasions when it is inconvenient to revert to an older save. The Troubleshooting Guide provides a "best-practice procedure" for attempting to ‘clean’ the effects of a removed mod from a save game.

FINALLY... ALWAYS read the ReadMe and other mod-related documentation that comes packaged with most mods. This includes the mod description on the Nexus. If the mod author has seen fit and taken time to create these reference materials, then they are relevant and important in the eyes of the mod author. This means that they are relevant and important to you!

STEP 2[edit | edit source]

Mod Installation


Mod Name Baseline Quality Options DLC Required Notes
Mod NameWikilink.png Baseline LowQuality.png HighQuality.png Dawnguard.png Notes
Core Mod Core mods are indicated by the presence of a green vertical bar in the row at the immediate left-hand column of the table.
Mod Name Nexus mod name (where applicable) presented as a link links to Nexus for download.
Wikilink.png Link to the mod's Wiki page.
Baseline This notes the STEP Baseline version or option of the corresponding mod, and usually only refers to graphical quality choices. Stylistic or mechanical suggestions are located in the "Notes" section.
Quality Options Indicates if there are performance-friendly or performance-unfriendly versions of the mod relative to the Baseline recommendation:
 LowQuality.png       Relative to Baseline, a lower quality, less demanding version of the mod is also available.
      HighQuality.png  Relative to Baseline, a higher quality, more demanding version of the mod is also available.
 LowQuality.png HighQuality.png  Relative to Baseline, both lower and higher quality versions of the mod are available.
DLC Required Any DLCs listed here are required for the mod to function. If all DLCs listed are not present do not use this mod.
Notes Brief notes that apply to the mod or installation. In some cases, mods with many alternative options will include a suggested option. These suggestions will take the form of: "STEP recommends 'Option A'." In other cases, there may only be one appropriate alternative option that fits the STEP Mandate. These instructions will take the form of: "Use 'Option A'."


Template:Notice

2.A.[edit | edit source]

No mods defined.

2.B.[edit | edit source]

No mods defined.

2.C.[edit | edit source]

No mods defined.

2.D.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.E.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.F.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.G.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.H.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.I.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.J.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.K.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.L.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.M.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


Post-Installation Housekeeping[edit | edit source]

Once all mods have been installed and are ready to play, be certain to either:

  • Start a brand new character, or
  • load the save game generated just after character creation if it exists, or
  • load an existing character after clean saving the relevant save game.


STEP 3[edit | edit source]

Tips & Troubleshooting Common Issues

3.A. Technical Tips[edit | edit source]

The following is a good place to begin, but be certain to also check the Troubleshooting Guide. Also, search the support & Troubleshooting forum on the STEP Boards,

3.A.1. Maximizing STEP[edit | edit source]

A heavily modded Skyrim can bring even a very powerful system to its knees. Maximum visual quality is highly dependent upon total on-card graphics-dedicated video memory (VRAM), the number of GPUs, and monitor resolution. The goal should be to maintain 32 or more FPS on average without any noticeable stuttering. Following are some enhancements that users with rather powerful systems might be able to take advantage of:

  • Try using SSAO (using video driver settings) for better quality graphics and note the performance hit.
  • Use one of the STEP-recommended ENB configurations.
  • Make sure Skyrim.ini and SkyrimPrefs.ini are writable and, using the Skyrim Launcher, max out ...
    • anti-aliasing
    • anisotropic filtering
    • view distances
    • shadow quality
    • texture quality

Template:Notice Small

3.A.2. Fix game launch crash after installing STEP[edit | edit source]

For crashes to desktop (CTDs),

  • Set the Skyrim executable "TESV.exe" to run as administrator (right click TESV.exe > Properties > Compatibility > Check Run this program as administrator).
  • If using RCRN or any other FXAA-Injector/ENB mod, turn off any on-screen display programs and monitoring tools such as Fraps, ATI Tray Tools, MSI Afterburner, GPU-Z, etc.
  • Get the latest DirectX runtime installed.

3.A.3. Defrag the Hard Drive[edit | edit source]

For hard drives (not SSDs), this is a very important task once most/all mods are installed. The Windows defrag utility may be used, but it is sub-standard. A couple of the best free utilities are Defraggler and Auslogics Disk Defrag. Do NOT defrag an SSD as it will detrimentally affect its lifetime.

3.A.4. Semi-Invisible People & Misbehaving Walls[edit | edit source]

Be certain that ATI Antialiasing is set to Multi-Sample and NOT Adaptive. Also, remember to download the latest ATI drivers. Also be certain that bFloatPointRenderTarget=1 in the SkyrimPrefs.ini if using ENB.

3.A.5. Using Windowed Mode (ATI)[edit | edit source]

If having stuttering problems or CTDs in full screen mode, try "full screen" windowed mode by downloading Simple Borderless Window. The "Simple Borderless Window" launcher SBW.exe launches SKSE, so start the game through SBW.exe.

3.A.6. Increase Overall Performance[edit | edit source]

If after following the whole guide and installing the enhanced graphics, the game is unplayable due to low performance, try one or more of the following:

  • Disable SSAO or Supersampling AA (or both) if enabled.
  • Reduce shadow quality from the Skyrim Launcher.
  • Install the performance-friendly versions of textures where applicable.
  • Consider texture optimization.
  • Reduce The [View Distance] settings in the game launcher (see 1.B.1).

3.A.7. Texture Shimmering, Etc.[edit | edit source]

Refer to the Z-Fighting Guide.

3.B. In-Game Tips[edit | edit source]

The console can be activated by pressing the tilde ([~]) key, often located just below [Escape], while in-game.

3.B.1. Optimize Field of View (FOV)[edit | edit source]

In the console enter the following using a number from 66-100, depending on resolution and screen ratio. Default is 65 (4:3 screens), but 70-75 works nicely for 16:10 screens and 75-80 works nicely for 16:9 screens:

FOV ##

This change will be permanent in the saved game. Other INI FOV tweaks don't require opening the console, but they don’t 'stick' and can corrupt the game. Also note that high FOV can cause a performance drop for some configurations.

3.B.2. BIG Frame Drops During Cell Loading[edit | edit source]

This is a likely indicator that VRAM is too often operating at or beyond capacity (see 3.A.6).

User Contributions[edit | edit source]

How YOU Can Help

STEP can only get bigger and better with help from the user community. Even simply maintaining the current STEP is too much work for the core STEP team to ensure that the highest quality is maintained. We need people to help us identify mods that are thought to improve Skyrim while adhering to the STEP Mandate. We also need ongoing reviews and updates on mods that may be causing problems or that stray from the STEP philosophy. Finally, we need help from the community in terms of testing, benchmarking and analysis. More detail is presented in the Mod Testing Guide.

In order to suggest a mod, visit the Mod Suggestions section of the STEP Forums.

Template:Notice

Thank you for reading and enjoy the game!


Special Credits[edit | edit source]

The STEP administrators would sincerely like to thank (from the bottoms of our fuzzy little hearts):

  • The authors of mods recommended in STEP
  • The core STEP Community for feedback, suggestions and input
  • The STEP beta testers ... for their good humor and rigorous analyses
  • The Nexus community
  • Bealdwine, EisDrache & MontyMM - site founders on indefinite leave (we hope you guys are well!) --UPDATE: MontyMM is back ... welcome back!
  • Outstanding v2.2.1 contributors - Techangel85, Neovalen, rpsgc, Besidilo, JudgementJay, torminater, Kelmych, Korentin & Mothergoose729
  • Bethesda Softworks for Skyrim (and TES in general)

Site Donors[edit | edit source]

We have had a handful of generous user donations to keep this site alive anviable. Most of these donors have not left their user names, so they shall remain anonymous; however, the following are site contributors that have generously given a bit of their livelihood in support of STEP. For that, we thank them immensely!

  • solist (our most generous contributor)
  • geeee785
  • 16 additional generous contributors that shall remain anonymous until their user names are made known to us.


The core STEP team is:[edit | edit source]
  • Farlo - Mediawiki developer & extraordinaire, Mod-list co-compiler, forums admin, site founder
  • frihyland - Solutions developer (Thunderbolt), mod extraordinaire, site founder
  • stoppingby4now - Main site developer, Semantic Mediawiki developer & extraordinaire, site founder
  • TheCompiler - STEP creator, mod-list extraordinaire
  • z929669 - Wiki & forums content editor, main site administrator, hosting maintenance, site founder
  • EMPTY SLOTS WAITING TO BE FILLED BY ESTABLISHED & DEDICATED COMMUNITY MEMBERS!

{{#css:MediaWiki:StepGuide.css}}