imported>Dev akm |
imported>Qazaaq |
| (10 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| = Troubleshooting Introduction = | | This is a collection of articles on troubleshooting TES IV problems -- gotchas, common mistakes, CS bugs, etc. The basic ideas and topics were originally discussed in [http://www.bethsoft.com/bgsforums/index.php?showtopic=628331 this ESF thread]. Continued reports and peer review has moved to a [http://www.bethsoft.com/bgsforums/index.php?showtopic=837706 new thread] now that the original is almost full. |
|
| |
|
| This is a collection of articles on troubleshooting TES IV problems -- gotchas, common mistakes, CS bugs, etc. The basic ideas and topics were originally discussed in [http://www.bethsoft.com/bgsforums/index.php?showtopic=628331 this ESF thread].
| | The original list started back in February 2007 has grown to the point that it needed to be split into separate articles. These articles list of some common mistakes and their effects on players and/or the CS. Please suggest more ideas if you can. |
|
| |
|
| These topics could be organized in a lot of different ways, but for now we can start with a simple list.
| |
|
| |
|
| I've created it as a category so we can add more specific topic articles in the category.
| | ---- |
|
| |
|
| What follows is essentially a long list of some common mistakes and their effects on players and/or the CS. Please suggest more ideas if you can.--[[User:Dev akm|Dev akm]] 17:56, 20 February 2007 (EST)
| |
|
| |
|
| | | *[[Common Bugs]] - These are annoying problems with the CS and game engine. |
| | | *[[Common Mistakes]] - These are things that all mod-creators should know not to do. |
| | | *[[Crashes]] - Common problems that may cause game crashes (CTDs). See also [[Crash Prevention]]. |
| | | *[[CS Crashes]] - Common actions that make the CS crash. |
| | | *[[Debugging]] - When something just isn't working right, look here for possible causes and ways to track down the bug. |
| | | *[[Performance Problems]] - This section is intended as a place to list performance problems and tips, especially those related to scripting. |
| | | *[[Fixing the AddTopic Bug]] - Critical dialog bug fix. |
| | | *[[Obscure Bugs]] - These issues don't occur very often, and we don't even really know what causes them, but they hurt nonetheless. |
| | | *[[Helpful Programs]] - These programs can help a lot when troubleshooting. |
| | | *[[Understanding Mod Conflict Reports]] - An explanation of different mod conflicts. |
| = Obscure Problems =
| |
| | |
| These issues don't occur very often, and we don't even really know what causes them, but they hurt nonetheless. | |
| | |
| == Pathgrid CTDs ==
| |
| | |
| Does anyone really know why the pathgrid CTDs happen? The last thread about it I remember didn't find a solution.
| |
| | |
| This is an older problem that plagued both UL and OOO for a while. Basically, [http://www.elderscrolls.com/forums/index.php?showtopic=495607 changing pathgrids is risky] and requires a lot of testing to avoid CTD issues. I didn't find any surefire solutions for this either. Does anyone know if this topic has been written about in any more detail than the introductory [[Path_Grid_Generation|Path Grid Generation]] article and [[A_beginner%27s_guide%2C_lesson_3_-_The_external_world#Path_Grids_.28simple.29 |Path Grids (simple)]]?
| |
| | |
| == Black Screen Bug ==
| |
| | |
| This is the [http://www.elderscrolls.com/forums/index.php?showtopic=517690 Infamous Nvidia + HDR Black Screen Bug].
| |
| | |
| This bug can usually be fixed by the mod-creator. It is usually caused by problems in a custom mesh. This can happen if the mesh creator forgot to assign a valid material to part of the mesh. It can also happen if you have an opaque texture assigned to a transparent portion of your mesh. It can even sometimes be caused by a standard shader like the GhostEffect.
| |
| | |
| It can also usually be solved by updating the tangent space of certain mesh nodes in a .nif file. NifSkope has a spell to do this.
| |
| | |
| Once you've narrowed down which .nif is causing the problem, simply open it in NifSkope, right-click each NiTriStrips/NiTriShape node and select ''Mesh -> Update Tangent Space''. This works most of the time.
| |
| | |
| = Related Articles =
| |
| | |
| = Helpful Programs =
| |
| [[TES4Edit]]<br> | |
| [[Wrye Bash]]<br> | |
| [[TES4Gecko]]<br> | |