Difference between revisions of "Helpful Programs"
imported>Dev akm (→In-Game Troubleshooting: added PrintC) |
imported>Dev akm (→In-Game Troubleshooting: added RefScope) |
||
| Line 14: | Line 14: | ||
If you want to create a serious debug environment for tracking down things you see in the game, you can use a dual-monitor setup with [[TES4Edit|TES4View]], [[OBSE]] and [[Pluggy]] to run TES4View on one screen while playing the game on the other. This setup will track what you're looking at in the game and automatically show you details in TES4View about whatever you currently have in your crosshair. Details [http://www.bethsoft.com/bgsforums/index.php?s=&showtopic=818024&view=findpost&p=11891509 here]. | If you want to create a serious debug environment for tracking down things you see in the game, you can use a dual-monitor setup with [[TES4Edit|TES4View]], [[OBSE]] and [[Pluggy]] to run TES4View on one screen while playing the game on the other. This setup will track what you're looking at in the game and automatically show you details in TES4View about whatever you currently have in your crosshair. Details [http://www.bethsoft.com/bgsforums/index.php?s=&showtopic=818024&view=findpost&p=11891509 here]. | ||
You can find some of the same information about things you see in the game using [http://tesnexus.com/downloads/file.php?id=16704 FormID Finder]. | You can find some of the same information about things you see in the game using [http://tesnexus.com/downloads/file.php?id=16704 FormID Finder] and/or [http://planetelderscrolls.gamespy.com/View.php?view=OblivionMods.Detail&id=5204 RefScope]. | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||
Revision as of 17:38, 6 January 2009
Helpful Programs
These programs can help a lot when troubleshooting.
TES4Edit
Wrye Bash
TES4Gecko
OBSE
In-Game Troubleshooting
The standard method of tracking down problem mod objects in-game is to use Beta Comments.
For debugging scripts, the OBSE command PrintToConsole is very helpful for giving you a way to see in-game debug messages from your scripts.
If you want to create a serious debug environment for tracking down things you see in the game, you can use a dual-monitor setup with TES4View, OBSE and Pluggy to run TES4View on one screen while playing the game on the other. This setup will track what you're looking at in the game and automatically show you details in TES4View about whatever you currently have in your crosshair. Details here.
You can find some of the same information about things you see in the game using FormID Finder and/or RefScope.