Difference between revisions of "Bethsoft Tutorial GECK Setup"
Jump to navigation
Jump to search
m
Bethsoft Tutorial GECK Setup (edit)
Revision as of 14:35, 13 December 2008
, 14:35, 13 December 2008→Loading and testing your plugin
imported>Khomotso |
imported>Khomotso |
||
Line 31: | Line 31: | ||
==Loading and testing your plugin== | ==Loading and testing your plugin== | ||
[[image:launcherDatafile.jpg|thumb|right|Loading your Plugin]] | [[image:launcherDatafile.jpg|thumb|right|Loading your Plugin]] | ||
* Load the Fallout 3 Launcher, don't hit | * Load the Fallout 3 Launcher, but don't hit '''PLAY'''. | ||
* Choose "Data Files" from the launcher | * Choose "Data Files" from the launcher | ||
* The new plugin you created should be | * The new plugin you created should be available on the next screen, with an empty checkbox. Check it and click '''OK'''. | ||
<blockquote> | <blockquote> | ||
Don't see your .esp file? Verify that you installed the GECK to the same directory as your retail installation of Fallout 3. The file should have been created in a ''\Data'' sub-directory in that directory. This is where the launcher looks for data files. <br>Under Vista, if you are not running as Administrator, the data file may have been created in a shadow directory (with a name like "\Users\Me\AppData\Local\VirtualStore\Program Files\Bethesda Softworks\Fallout3\Data"), where it is visible to the GECK but not to the Fallout3 launcher. You can avoid this by always running the GECK as Administrator. | Don't see your .esp file? Verify that you installed the GECK to the same directory as your retail installation of Fallout 3. The file should have been created in a ''\Data'' sub-directory in that directory. This is where the launcher looks for data files. <br>Under Vista, if you are not running as Administrator, the data file may have been created in a shadow directory (with a name like "\Users\Me\AppData\Local\VirtualStore\Program Files\Bethesda Softworks\Fallout3\Data"), where it is visible to the GECK but not to the Fallout3 launcher. You can avoid this by always running the GECK as Administrator. |