**For those who absolutley can't stand the occasional graphical glitches seen when using TexMod and have some time on their hands :)**
Read and try this:
I have found that when I am working on textures in the game I am in logging mode and all of the textures are in a folder in my Masseffect directory and my TexMod.log points to them, they are not in a .tpf so they are not compressed and I NEVER see glitches in this mode. If you want to try this and have the HDD space follow the steps below:
Step 1) Download TpfExtract The link is below.
Step 2) Open Tpf Extract GUI and find and select the full pack. Click "Extract" Choose the place you want to keep the files and continue. Now all of the Textures are uncompressed and in .bmp form and a Texmod.def (opened by notepad) file in your desired location.
Step 3) Now comes the tedious part, you need to create a TexMod.log file that tells TexMod where to find these files. Use the definition file (that was created with your opentpf extraction as a base). It contains all of the file names but is missing the directory of the textures.
TexMod.def says: "0xA412EC15|MASSEFFECT.EXE_0xA412EC15.bmp"
TexMod.log needs to say:" 0xA412EC15|C:\Program Files (x86)\Mass Effect\Binaries\ME1 Tex rep\ME 1 Package\MASSEFFECT.EXE_0xA412EC15.bmp"
The middle piece is the directory where you store the files. You need to add that piece for all 303 textures and then name the newly created file to TexMod.log.
You can use "ctrl H" find and replace function in note pad to do this. Find "|MASSEFFECT.EXE" and replace with your directory for example "|C:\Program Files (x86)\Mass Effect\Binaries\ME1 Tex rep\ME 1 Package\MASSEFFECT.EXE"
Step 4) Finally in the logging section of TexMod where it asks to specify "Def File" point it to your newly created TexMod.log and run the game in logging mode.
The benefits are: zero glitches and much faster getting into the game because no decompression is required.
**Update Major flaw** (for now)
Running in logging mode though visually flawless, currently causes TexMod to crash due to a memory leak that I'm not sure how to fix. The crash comes within 20-40 minutes and so far has been unavoidable. I have discussed with fellow members trying to find a solution over at SBN. So far we have had no luck :/.