Difference between revisions of "Category talk:Items"
no edit summary
imported>M1k3y360 |
imported>M1k3y360 |
||
| Line 62: | Line 62: | ||
---------------- | ---------------- | ||
Ok here is the solution everyone wants to know so no one ever gets an "invalid directory" error again. Editing the *.ini files (the "bInvalidateOlderFiles") only makes a File valid or not depending on how new they are when compared to the orginal. So solving the "invalid directory" problem has nothing to do with the *.ini files. The problem is, I believe we are all asuming that the .dds file loaded here is for the actual texture - it is not. This second file is for the "icon" of the item appearing in the ingame menu, that is a completely different .dds file from the ones used in actual texturing. So, all .dds files acquainted with this second spot are for the "icons" and not textures. The textures themselves are linked to the .nif files, and you can edit the directory in which they are linked using nifskope. Also be aware that nifskope will give you a "file not found" error when the directory path is actually correct to the game, nifscope just can't itself read files before the .nif file that is open's current directory. Anyway you can figure the rest out from here, if you have any questions or anything be glad to help. 7/9/06 | Ok here is the solution everyone wants to know so no one ever gets an "invalid directory" error again. Editing the *.ini files (the "bInvalidateOlderFiles") only makes a File valid or not depending on how new they are when compared to the orginal. So solving the "invalid directory" problem has nothing to do with the *.ini files. The problem is, I believe we are all asuming that the .dds file loaded here is for the actual texture - it is not. This second file is for the "icon" of the item appearing in the ingame menu, that is a completely different .dds file from the ones used in actual texturing. So, all .dds files acquainted with this second spot are for the "icons" and not textures. The textures themselves are linked to the .nif files, and you can edit the directory in which they are linked using nifskope. Also be aware that nifskope will give you a "file not found" error when the directory path is actually correct to the game, nifscope just can't itself read files before the .nif file that is open's current directory. Anyway you can figure the rest out from here, if you have any questions or anything be glad to help. 7/9/06 | ||
mikey ~ the ewok ~ | mikey ~ the ewok ~ [[User:mikey the ewok|m1k3y360]] | ||
mikey@ewokattack.com | mikey@ewokattack.com | ||