STEP:Mod Testing: Difference between revisions
From Step Mods | Change The Game
MadWizard25 (talk | contribs) No edit summary |
MadWizard25 (talk | contribs) No edit summary |
||
Line 13: | Line 13: | ||
''' | ''' | ||
= Computer Stability = | = Computer Stability & Settings = | ||
''' | ''' | ||
Line 50: | Line 50: | ||
[[File:Recommended Settings.png|250px|thumb:'''Figure 1.''' TESV.exe Properties Settings]] | [[File:Recommended Settings.png|250px|thumb:'''Figure 1.''' TESV.exe Properties Settings]] | ||
= Skyrim = | = Skyrim Stability & Settings = | ||
This section will describe best practices to ensure a stable Skyrim platform to work from. It will also detail various tips for debugging, error tracking, etc. | This section will describe best practices to ensure a stable Skyrim platform to work from. It will also detail various tips for debugging, error tracking, etc. | ||
Line 65: | Line 65: | ||
This will allow you to easily switch between mod testing ini's and your normal ini settings. To apply the ini settings, right click on the ini file in Wrye Bash and chose apply. Be warned that if you would like to remove the applied ini settings, you cannot do so from Wrye Bash. For example, if you apply your normal ini settings to your mod testing ini setting, you will overwrite many ini settings. However, if you mod testing ini settings contain entries that do not exist in your normal inis, then these entries will remain. Only enteries that exist in both will be overwritten. It is easier just to copy your settings from your normal ini files, delete the text inside your Skyrim.ini and SkyrimPrefs.ini, and paste the copied text inside if you wish to revert back to your personal settings. This can also be done from your backups. | This will allow you to easily switch between mod testing ini's and your normal ini settings. To apply the ini settings, right click on the ini file in Wrye Bash and chose apply. Be warned that if you would like to remove the applied ini settings, you cannot do so from Wrye Bash. For example, if you apply your normal ini settings to your mod testing ini setting, you will overwrite many ini settings. However, if you mod testing ini settings contain entries that do not exist in your normal inis, then these entries will remain. Only enteries that exist in both will be overwritten. It is easier just to copy your settings from your normal ini files, delete the text inside your Skyrim.ini and SkyrimPrefs.ini, and paste the copied text inside if you wish to revert back to your personal settings. This can also be done from your backups. | ||
'''uGrids''' | '''uGrids''' | ||
Line 73: | Line 70: | ||
This ini setting MUST be set to the default value of 5. For those of you who use a value of 7 and above, be warned that these higher values are 100% inherently unstable. It may be stable as a rock for you, but please don't test a mod with anything but the default value of 5. The chance that a new mod may cause stability issues with higher uGrids values is quite high, and again, most Skyrim players will be using the default value. To easily switch between uGrids values, create the relevant ini files in the INI Tweaks folder for WB as mentioned in the section above. | This ini setting MUST be set to the default value of 5. For those of you who use a value of 7 and above, be warned that these higher values are 100% inherently unstable. It may be stable as a rock for you, but please don't test a mod with anything but the default value of 5. The chance that a new mod may cause stability issues with higher uGrids values is quite high, and again, most Skyrim players will be using the default value. To easily switch between uGrids values, create the relevant ini files in the INI Tweaks folder for WB as mentioned in the section above. | ||
Should you attempt to test a mod on a save game that used to have a higher uGrids value, you will be unable to load it. There are three solutions. The first is to start a new game, which is highly preferred. The second is to use a Bat file to revert to the default value. These can be obtained from the DNA INI Generator site. The third option is to use a selection of vanilla saves and STEP complete saves that can be downloaded under the save game section. | Should you attempt to test a mod on a save game that used to have a higher uGrids value, you will be unable to load it. There are three solutions. The first is to start a new game, which is highly preferred. The second is to use a Bat file to revert to the default value. These can be obtained from the [http://donotargue.com/cfg-makers/skyrim/ DNA INI Generator] site. Once there, navigate to the green panel called Downloads, and follow the instructions there. The third option is to use a selection of vanilla saves and STEP complete saves that can be downloaded under the save game section. | ||
Default uGrids Settings (Skyrim.ini) | |||
[General] | |||
uGrids=5 | |||
uExterior Cell Buffer=32 | |||
'''Papyrus Logging''' | '''Papyrus Logging''' | ||
Line 92: | Line 92: | ||
'''Mod Tracing''' | '''Mod Tracing''' | ||
At the moment, in game mod tracing is very basic. Currently for textures, you can open the command console by pressing the ~ key, and click on the texture that you are interested in. In the console command screen you will see its name and reference ID (eight hexadecimal characters, ie "001C8F02"). If the texture starts with 00 then its a vanilla texture. If it is anything else, then it is a texture from a mod, or an object from a mod. | |||
= In Game Mod Testing Procedure = | |||
'''Testing Locations''' | '''Testing Locations''' | ||
Line 121: | Line 119: | ||
tfc 1 | tfc 1 | ||
= Save Game Archive = | |||
= In Game Tools = | = In Game Tools = |
Revision as of 11:27, July 19, 2012
Template:Warning Template:Notice Mod Testing for S.T.E.P. -- by MadWizard25, the S.T.E.P. Team and Wiki Editors
- Updated: 11:27:16 19 July 2012 (UTC)